Details
-
Story
-
Status: Closed (View Workflow)
-
P2
-
Resolution: Done
-
None
-
None
-
-
ACQ Sprint 82
-
1
-
Thunderjet
Description
Overview
Upon opening an order, we need to create encumbrances - either all the encumbrances for that order are created, or none of them are. Her we create an order_transaction_summary and accumulate the new encumbrances in temporary_order_transactions.
This behavior is correct, but needs to be expanded upon to accommodate MODINVOICE-113. More specifically:
Upon approving an invoice, we need to update encumbrances via the awaitingPayment API - another all-or-nothing operation. Here we create an invoice_transaction_summary and accumulate the updated encumbrances in temporary_invoice_transactions.
See the wiki for full details.
Acceptance Criteria
- Fix implementation of PUT /finance-storage/transactions/{id} according to the wiki
- Unit tests are updated
TestRail: Results
Attachments
Issue Links
- blocks
-
MODINVOICE-113 Call awaiting-payment API upon invoice approval
-
- Closed
-
- defines
-
UXPROD-2167 Value management through transactions Part 2 - Payments, Credits and limits
-
- Closed
-
- relates to
-
MODFISTO-91 Budgets aren't updated correctly upon updating/releasing encumbrance
-
- Closed
-