Details
-
Bug
-
Status: Closed (View Workflow)
-
P2
-
Resolution: Done
-
None
-
-
ACQ Sprint 137
-
3
-
Thunderjet
-
Lotus (R1 2022) Bug Fix
-
!!!ALL!!!
-
Implementation coding issue
Description
Overview: Job ID is not a part of compPO or ediExportConfig model so it's not set when mapping our models to EDIFACT format.
Steps to Reproduce:
- Get any export job to run
- Open EDI file and check the number at the end of UNB line and the beginning of UNH line
Expected Results: Job ID generated by mod-data-export-spring is present at the end of UNB line and at the beginning of UNH line
Actual Results: Spring JobInstanceId is present instead, which is not unique between files and is unrelated to our Job ID
Additional Information: Possible solution is to add Job ID to ediExportConfig so that it's available at mod-export-worker during the mapping.
Interested parties:
TestRail: Results
Attachments
Issue Links
- blocks
-
MODEXPW-97 MODEXPW (mod-data-export-worker) for Lotus BF#2 release
-
- Closed
-
- defines
-
UXPROD-531 Export FOLIO orders in EDIFACT format
-
- Closed
-