Uploaded image for project: 'mod-orders'
  1. mod-orders
  2. MODORDERS-406

Prevent the creation of an encumbrance for an inactive expense class

    XMLWordPrintable

Details

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

    Description

      Purpose:
      Requirement from the UX ticket: Each expense class has a status within the fund of Active or inactive. Inactive types can not be used

      Requirements/Scope:

      1. Update transaction(Encumbrance) creation and update logic
      2. Update unit tests
      3. Update API tests

      Approach:
      If expenseClassId specified in fundDistribution

      • if expenseClass has active status
        • populate transaction.expenseClassId. Create or update transaction
      • else
        • return error with inactiveExpenseClass error code

      Acceptance criteria:

      • logic updated
      • unit tests updated
      • API tests updated

      TestRail: Results

        Attachments

          1. karate.7z
            36 kB
          2. karate-1.png
            karate-1.png
            33 kB

          Issue Links

            Activity

              People

                Andrei_Makaranka Andrei Makaranka
                aliaksandr_pautau Aliaksandr Pautau
                Votes:
                0 Vote for this issue
                Watchers:
                2 Start watching this issue

                Dates

                  Created:
                  Updated:
                  Resolved:

                  TestRail: Runs

                    TestRail: Cases