Details
-
Type:
Story
-
Status: Closed (View Workflow)
-
Priority:
P3
-
Resolution: Done
-
Affects Version/s: None
-
Fix Version/s: 6.0.0
-
Labels:None
-
Template:
-
Sprint:ACQ Sprint 98
-
Story Points:2
-
Development Team:Thunderjet
-
Epic Link:
Description
Purpose/Overview:
In order to support UIF-253 we need to support multiple expense classes for one fund in POL and invoice lines
Requirements/Scope:
- Support expense classes
Approach:
Update schema.json for temporary_order_transactions, temporary_invoice_transactions, transaction tables by adding "expenseClassId"
"uniqueIndex": [
{
"fieldName": "encumbrance",
"multiFieldNames": "amount, fromFundId, encumbrance.sourcePurchaseOrderId, encumbrance.sourcePoLineId, encumbrance.initialAmountEncumbered, encumbrance.status, expenseClassId",
"tOps": "ADD",
"whereClause": "WHERE (jsonb->>'transactionType')::text = 'Encumbrance'"
}
Acceptance criteria:
- Schema updated
- API tests created
TestRail: Results
Attachments
Issue Links
- blocks
-
MODFISTO-130
MODFISTO (mod-finance-storage) release
-
- Closed
-
- defines
-
UXPROD-2362 Shared allocation for budgets
-
- Closed
-
- has to be done before
-
UIF-253
Allow user to use multiple expense class from same fund on one invoice line or POL
-
- Closed
-