Details
-
Story
-
Status: Closed (View Workflow)
-
P3
-
Resolution: Done
-
None
-
-
ACQ Sprint 120, ACQ Sprint 121, ACQ Sprint 122
-
2
-
Thunderjet
Description
Overview: Given a FOLIO tenant is using expense classes in their Fund structure. Third party systems must be able to indicate which Fund and Expense classes should be associated with the order line.
Acceptance criteria:
External systems (eg GOBI) can apply fund and expense class when creating orders
Approach:
Between fund code and expense class code splitter must be ":"
Example : "fundCode1234:electronicPrn"
Information:
External systems generally only support Fund codes and the sending of a fund code. For this reason it might make sense to use expense class codes as extensions and maintain a list of all fund code+extentions that can be used to Map Fund codes and expense classes when creating orders.
External systems (eg GOBI) may have customizable fields that could be used to send the additional expense class information separately from Fund code.
TestRail: Results
Attachments
Issue Links
- has to be done after
-
MODFISTO-243
Define DTO schema for combination of fund code and expense class
-
- Closed
-
- is blocked by
-
MODFIN-199
Create API for retrieving combination of fund code and expense classes
-
- Closed
-
- is defined by
-
UXPROD-3096 Allow external systems to apply Fund AND Expense classes when creating or updating POLs
-
- Closed
-
- relates to
-
MODEBSNET-13
Update logic for supporting fund expense classes
-
- Closed
-
-
MODEBSNET-22
Support canceling POL(s) through EBSCONET integration
-
- Closed
-
-
MODEBSNET-27
Update logic for supporting "customer note" from EBSCONET
-
- Closed
-
-
MODEBSNET-30
Update logic for supporting "Renewal note" from EBSCONET
-
- Closed
-
-
MODEBSNET-33
Update logic for supporting "customer note" from EBSCONET
-
- Closed
-
-
UIOR-965
Display "Renewal note" field on POL
-
- Closed
-