Uploaded image for project: 'mod-ebsconet'
  1. mod-ebsconet
  2. MODEBSNET-13

Update logic for supporting fund expense classes

    XMLWordPrintable

Details

    Description

      Purpose:

      Support applying expense classes together with fund codes in order details.

      Requirements:

      https://wiki.folio.org/display/DD/Apply+expense+classes+to+orders+and+invoices+through+API+integrations

      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

            New Feature - New feature requests UXPROD-3257 Update FOLIO<>EBSCONET order renewal logic

            • P3 - low priority level, item will be considered for inclusion in the next dev cycle
            • Closed
            has to be done after

            Story - Created by Jira Software - do not edit or delete. Issue type for a user story. MODFISTO-243 Define DTO schema for combination of fund code and expense class

            • P3 - low priority level, item will be considered for inclusion in the next dev cycle
            • Closed
            is cloned by

            Story - Created by Jira Software - do not edit or delete. Issue type for a user story. MODEBSNET-22 Support canceling POL(s) through EBSCONET integration

            • P3 - low priority level, item will be considered for inclusion in the next dev cycle
            • Closed

            Story - Created by Jira Software - do not edit or delete. Issue type for a user story. MODEBSNET-27 Update logic for supporting "customer note" from EBSCONET

            • P2 - normal priority level, must be included in the current development cycle
            • Closed
            relates to

            Story - Created by Jira Software - do not edit or delete. Issue type for a user story. MODGOBI-123 Allow mapping for expense classes through GOBI

            • P3 - low priority level, item will be considered for inclusion in the next dev cycle
            • Closed
            mentioned in

            Page Loading...

            Activity

              People

                dennisbridges Dennis Bridges
                Andrei_Makaranka Andrei Makaranka
                Votes:
                0 Vote for this issue
                Watchers:
                4 Start watching this issue

                Dates

                  Created:
                  Updated:
                  Resolved:

                  TestRail: Runs

                    TestRail: Cases