Order Integration with External Systems (Misc) (UXPROD-1580)

[UXPROD-2361] Simplify implementation of order API integrations for vendors Created: 24/Mar/20  Updated: 16/Sep/21  Resolved: 13/Jul/20

Status: Closed
Project: UX Product
Components: None
Affects versions: None
Fix versions: Q2 2020
Parent: Order Integration with External Systems (Misc)

Type: New Feature Priority: P3
Reporter: Dennis Bridges Assignee: Dennis Bridges
Resolution: Done Votes: 0
Labels: acquisitions, orders
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original estimate: Not Specified

Issue links:
Gantt End to End
has to be finished together with UXPROD-190 Create/Renew orders in FOLIO from EBS... Closed
Relates
relates to EDGORDERS-22 Configuration based request routing Closed
relates to EDGORDERS-27 Honor Accept header Closed
Epic Link: Order Integration with External Systems (Misc)
Back End Estimate: Medium < 5 days
Development Team: Thunderjet
PO Rank: 89.2
Rank: Chicago (MVP Sum 2020): R4
Rank: Cornell (Full Sum 2021): R2
Rank: Duke (Full Sum 2021): R2
Rank: 5Colleges (Full Jul 2021): R4
Rank: GBV (MVP Sum 2020): R2
Rank: TAMU (MVP Jan 2021): R2

 Description   

Overview: Update existing architecture to allow for additional third parties to easily add routing for their data through edge-orders. Sending it into a FOLIO module they have contributed for the use of mod-orders APIs for creating and possibly updating order records in FOLIO based on work done in their separate system.

Background:
Writing a vendor-specific module (see wiki Configuration based logic) this is where mapping and translation happens between the vendor and FOLIO (mod-orders). Lookups of things like locations, material-types, organizations, etc. will also happen here.
Minor changes in edge-orders to handle proper routing of requests to the proper vendor-specific module (e.g. mod-gobi, mod-ebsconet, etc.). There's essentially a decision tree that looks at the "type" query argument in the request and uses that to proxy the request to the appropriate API, e.g. POST /orders?type=GOBI proxies the request to POST /gobi/orders.

Approach:
Allow for these type → API mappings to be defined via configuration.


Generated at Fri Feb 09 00:23:19 UTC 2024 using Jira 1001.0.0-SNAPSHOT#100246-sha1:7a5c50119eb0633d306e14180817ddef5e80c75d.