Done
Details
Reporter
Dennis BridgesDennis BridgesFront End Estimate
Small < 3 daysBack End Estimate
Medium < 5 daysRank: 5Colleges (Full Jul 2021)
R1Rank: Chalmers (Impl Aut 2019)
R4Rank: Chicago (MVP Sum 2020)
R1Rank: U of AL (MVP Oct 2020)
R1Rank: Lehigh (MVP Summer 2020)
R1TestRail: Cases
Open TestRail: CasesTestRail: Runs
Open TestRail: Runs
Details
Details
Reporter
Dennis Bridges
Dennis BridgesFront End Estimate
Small < 3 days
Back End Estimate
Medium < 5 days
Rank: 5Colleges (Full Jul 2021)
R1
Rank: Chalmers (Impl Aut 2019)
R4
Rank: Chicago (MVP Sum 2020)
R1
Rank: U of AL (MVP Oct 2020)
R1
Rank: Lehigh (MVP Summer 2020)
R1
TestRail: Cases
Open TestRail: Cases
TestRail: Runs
Open TestRail: Runs
Created January 18, 2019 at 3:16 PM
Updated September 16, 2020 at 9:12 PM
Resolved April 3, 2019 at 5:16 PM
Note This feature was created as a result of splitting https://folio-org.atlassian.net/browse/UXPROD-678#icft=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.