Uploaded image for project: 'mod-finance-storage'
  1. mod-finance-storage
  2. MODFISTO-165

Field "expenseClassId" must be a part of unique-constraint

    XMLWordPrintable

Details

    • Story
    • Status: Closed (View Workflow)
    • P3
    • Resolution: Done
    • None
    • 6.0.0
    • None

    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:

      1. 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

            Activity

              People

                Andrei_Makaranka Andrei Makaranka
                Andrei_Makaranka Andrei Makaranka
                Votes:
                0 Vote for this issue
                Watchers:
                1 Start watching this issue

                Dates

                  Created:
                  Updated:
                  Resolved:

                  TestRail: Runs

                    TestRail: Cases