Details
-
Story
-
Status: Closed (View Workflow)
-
P3
-
Resolution: Done
-
None
-
-
ACQ Sprint 88
-
2
-
Thunderjet
Description
Overview
There's a new requirement that we support the ability for a poLine to represent a single title, that's part of a package represented by another POL. So something like:
1000-1 - package
1000-2 - title that's part of the 1000-1 package
1000-3 - title that's part of the 1000-1 package
MODORDSTOR-136 adds the fields needed to do this to the poLine and title schemas. This story follows that by updating the related business logic.
Approach
upon title creation:
thePOL = getPOL(title.poLineId) if(thePOL.isPackage) { //POL is a package title.packageName = thePOL.titleOrPackage //} else { // POL represents a title //if(thePOL.packagPoLineId != null) { // We have a link to a packagePOL // packagePOL = getPOL(thePOL.packagePoLineId) // title.packageName = packagePOL.titleOrPackage } else { // We don't have a link to a packagePOL // get title by poLineId and if exist then throw error else populate } }
Also within scope of this story: Upon title creation copy over information from POL -> Title for new fields added in MODORDSTOR-136 (poLineNumber, receivingNote, expectedReceiptDate)
Introduce new error code "titleExist" that indicate the title for regular poLine already exist.
Acceptance Criteria
- Business logic is updated as described above
- unit tests are updated
- API tests are updated
TestRail: Results
Attachments
Issue Links
- has to be done after
-
MODORDSTOR-136 Title, PoLine schema updates
-
- Closed
-
- has to be done before
-
MODORDSTOR-151 Support "title" and "package" order lines with packagePoLIne
-
- Closed
-
- relates to
-
UIOR-564 Link title POL to Package POL
-
- Closed
-
-
UXPROD-2294 Check-in and Receiving updates and fixes
-
- Closed
-
-
UIREC-87 Handle additional error code from Title creation
-
- Closed
-