Details
-
Story
-
Status: Closed (View Workflow)
-
P2
-
Resolution: Done
-
None
-
-
Firebird Sprint 88
-
3
-
Thunderjet
Description
Overview
Allocations and transfers to/from budgets from another budget should be restricted by the fund.allocatedToIds and fund.allocatedFromIds fields in the funds associated with the budgets involved.
Example
Given the following funds:
- HIST allocatedTo: [CANHIST, LATHIST], allocatedFrom: []
- CANHIST allocatedFrom: [HIST], allocatedTo: []
- LATHIST allocatedFrom: [], allocatedTo: []
Transfers/Allocations to/from budgets associated with these funds should be restricted as follows:
- HIST -> CANHIST should be allowed
- HIST -> LATHIST should not be allowed since LATHIST doesn't have HIST in allocatedFrom.
- CANHIST -> (any budgets) should not be allowed
- LATHIST <-> (any budgets) should not be allowed
- LATHIST <- (no fromFundId specified) should be allowed - allocation only.
If an allocation or transfer is disallowed, an appropriate error response should be returned.
It's possible to allocated to or from a budget from "nowhere" so to speak... i.e. not to/from another budget but from outside the system. Transfers are always between budgets so this statement doesn't apply to transfers.
Acceptance Criteria
- Transfers/allocations between budgets should be restricted as described above
- unit tests are updated
- api tests are updated
TestRail: Results
Attachments
Issue Links
- has to be done before
-
UIF-153 Display appropriate error message when transaction is blocked by Allow to or from Fund setting
-
- Closed
-
- relates to
-
UXPROD-2295 Value management through transactions Part 3 - Fixes and committing/encumbering money for approved invoices
-
- Closed
-