Uploaded image for project: 'mod-data-export-worker'
  1. mod-data-export-worker
  2. MODEXPW-93

Job ID is not set correctly during EDIFACT mapping

    XMLWordPrintable

Details

    • 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:

      1. Get any export job to run
      2. 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

            Activity

              People

                dennisbridges Dennis Bridges
                andriy_kundyukov Andriy Kundyukov
                Dennis Bridges Dennis Bridges
                Votes:
                0 Vote for this issue
                Watchers:
                2 Start watching this issue

                Dates

                  Created:
                  Updated:
                  Resolved:

                  TestRail: Runs

                    TestRail: Cases