Details
-
Story
-
Status: Closed (View Workflow)
-
P3
-
Resolution: Done
-
None
-
None
-
-
ACQ Sprint 66, ACQ Sprint 67
-
3
-
Thunderjet
Description
Overview:
Since piece and poLine records are stored separate from one another, and are managed via their own APIs, there's the possibility that inconsistencies may arise. The receiptStatus fields could get out of sync. So solve this problem, whenever a piece record's receivingStatus changes, we should emit an event which triggers the "calculation" of the corresponding poLine's receptStatus...
This builds upon the vertx eventBus work done in MODORDERS-218.
Also relevant for additional context/background: MODORDERS-106 and this wiki page
Acceptance Criteria:
- poLine.receiptStatus is "calculated" whenever a related piece record's receivingStatus is changed. This happens asynchronously via the vertx event bus.
- Unit tests are updated
- API tests are updated
TestRail: Results
Attachments
Issue Links
- relates to
-
MODORDERS-106 Spike: PO Line Status update during receiving (guarantee the status is up-to-date)
-
- Closed
-
-
UXPROD-1777 Ordering updates and fixes - Q3 2019
-
- Closed
-
-
MODORDERS-218 Automatically adjust order status based on poLine's paymentStatus and receivingStatus
-
- Closed
-