Details
-
New Feature
-
Status: Closed (View Workflow)
-
P3
-
Resolution: Done
-
None
-
None
-
-
Small < 3 days
-
Medium < 5 days
-
EBSCO - FSE
-
-
R4
-
R1
-
R1
-
R1
-
R1
Description
Note This feature was created as a result of splitting UXPROD-678 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.
TestRail: Results
Attachments
Issue Links
- clones
-
UXPROD-678 GOBI API integration for creating Purchase Orders
-
- Closed
-
- relates to
-
MODGOBI-40 Update to RAML 1.0 and RMB 23
-
- Closed
-
-
MODGOBI-42 Mapping Remaining fields for default mapping
-
- Closed
-
-
MODGOBI-44 Use new Orders endpoint
-
- Closed
-
-
MODGOBI-45 Create MODGOBI release
-
- Closed
-
-
MODGOBI-47 Update required to support new interfaces provided by mod-vendors
-
- Closed
-
-
MODGOBI-49 Fix SonarQube security issue(s)
-
- Closed
-
-
UXPROD-961 Allow Inventory Instances to generate purchase order and purchase order lines
-
- Closed
-