GOBI API integration for creating Purchase Orders, Basic (UXPROD-989)

[UXPROD-1444] Update GOBI API integration for creating Purchase Orders Created: 18/Jan/19  Updated: 16/Sep/20  Resolved: 03/Apr/19

Status: Closed
Project: UX Product
Components: None
Affects versions: None
Fix versions: Q1 2019
Parent: GOBI API integration for creating Purchase Orders, Basic

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

Issue links:
Cloners
clones UXPROD-678 GOBI API integration for creating Pur... Closed
Relates
relates to MODGOBI-49 Fix SonarQube security issue(s) Closed
relates to MODGOBI-40 Update to RAML 1.0 and RMB 23 Closed
relates to MODGOBI-42 Mapping Remaining fields for default ... Closed
relates to MODGOBI-44 Use new Orders endpoint Closed
relates to MODGOBI-45 Create MODGOBI release Closed
relates to MODGOBI-47 Update required to support new interf... Closed
relates to UXPROD-961 Allow Inventory Instances to generate... Closed
Epic Link: GOBI API integration for creating Purchase Orders, Basic
Front End Estimate: Small < 3 days
Back End Estimate: Medium < 5 days
Development Team: EBSCO - FSE
Rank: Chalmers (Impl Aut 2019): R4
Rank: Chicago (MVP Sum 2020): R1
Rank: 5Colleges (Full Jul 2021): R1
Rank: Lehigh (MVP Summer 2020): R1
Rank: U of AL (MVP Oct 2020): R1

 Description   

Note This feature was created as a result of splitting UXPROD-678 Closed for the Q4 release. Some of the field mapping work has not yet been finished.

Purpose: Allow for the ordering of materials from GOBI via API integration. Map fields for incoming data in order to create orders with the details sent from GOBI

*Note: when I say customer delay, I am talking about fulfilling their order, there is no actual customer at a UI waiting for this response, otherwise we would be asking for sub-second responses.

*Also Note: At 100 seconds, our call fails (Timeouts), and the order is placed back into the queue for a retry (Up to 10 times) before it gives up.  So if your application does not process the order within 100 seconds, you can expect to see it again.  This can cause problems with duplicate orders unless you fail your own thread and rollback the order if you cannot respond within 100 seconds.  This is what OLE does.



 Comments   
Comment by Dennis Bridges [ 03/Apr/19 ]

All related user stories have been closed. Testing and demo successful in purpose built environments.

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