Details
-
Type:
Story
-
Status: Closed (View Workflow)
-
Priority:
P3
-
Resolution: Done
-
Affects Version/s: None
-
Fix Version/s: 1.3.0
-
Labels:
-
Template:
-
Sprint:ACQ Sprint 137, ACQ Sprint 138, ACQ Sprint 139
-
Story Points:3
-
Development Team:Thunderjet
-
Release:Morning Glory R2 2022
Description
Purpose:
Support applying expense classes together with fund codes in order details.
Requirements:
Approach:
Handle fund code and expense class being sent together using separator ":"
If "fundCode" doesn't contain the separator, everything should work as before. If "fundCode" contains the separator, new logic should treat everything before the separator as fund code, and everything after the separator as expense class.
Example:
{
...
"fundCode": "HIST:electronic",
...
}
Similar issue: MODGOBI-123
Acceptance criteria:
- When updating order line through EBSCONET user can apply expense class
TestRail: Results
Attachments
Issue Links
- defines
-
UXPROD-3257 Update FOLIO<>EBSCONET order renewal logic
-
- In progress
-
- has to be done after
-
MODFISTO-243
Define DTO schema for combination of fund code and expense class
-
- Closed
-
- is cloned by
-
MODEBSNET-22
Support canceling POL(s) through EBSCONET integration
-
- In Code Review
-
-
MODEBSNET-27
Update logic for supporting "customer note" from EBSCONET
-
- Closed
-
- relates to
-
MODGOBI-123
Allow mapping for expense classes through GOBI
-
- Closed
-
- mentioned in
-
Page Loading...