Details
-
Story
-
Status: Closed (View Workflow)
-
P3
-
Resolution: Done
-
None
-
customfield_11100 30575
-
ACQ Sprint 77, ACQ Sprint 78
-
3
-
Thunderjet
Description
Overview
In order to ensure consistency we need to update several running totals upon transaction (allocation, transfer, payment, credit, encumbrance) within a database transaction. This ensures that either all of the records are updated, or none of them are.
See the following wiki pages for details:
Calculations
- The story is about implementing recalculation upon update of encumbrance. The part of recalculations upon creating was implemented in story MODFISTO-29
- when money moves from encumbered -> awaiting-payment
- when encumbrances are released
- Take into account that updating operation overlaps with migration scripts
NOTE: Stay away from triggers if possible
Acceptance Criteria
- Running totals in budget and ledger are updated as described above upon transaction UPDATE
- All tables involved are updated within a database transaction
- Unit tests are updated
- JavaMoney API is used for all calculations
TestRail: Results
Attachments
Issue Links
- has to be done after
-
MODFISTO-20 Update Transaction schemas
-
- Closed
-
-
MODFISTO-21 Create/Update Ledger schemas
-
- Closed
-
-
MODFISTO-24 Update Budget Schema
-
- Closed
-
- has to be done before
-
MODINVOICE-113 Call awaiting-payment API upon invoice approval
-
- Closed
-
- relates to
-
MODFIN-70 Create transaction APIs - Allocations, Transfers, Encumbrances
-
- Closed
-
-
MODFISTO-29 Transaction Calculations - Encumbrance
-
- Closed
-
-
MODFISTO-68 Fix Transaction Calculations - Encumbrance upon update
-
- Closed
-
-
MODFISTO-91 Budgets aren't updated correctly upon updating/releasing encumbrance
-
- Closed
-
-
MODFISTO-61 budget/ledger unavailable shouldn't include overEncumbered amounts
-
- Closed
-
-
UXPROD-196 Value management through transactions.
-
- Closed
-