[thomas-sc]

Purpose

On a PO line the "Automatic export" checkbox only tells the orderer that the line is flagged for export, not which integration will pick it up, and nothing shows when no integration matches at all. Add a read-only hint next to the checkbox, in the edit form and in the detail view, and align the checkbox calculation with the backend routing.

Approach

getApplicableOrderingIntegrations reproduces the PO line query that mod-data-export-worker builds for each integration (MapToEdifactOrdersTasklet#getPoLineQuery and #getVendorAccountFilter on master, MODEXPW-628). An integration applies to a line when the acquisition method is in its defaultAcquisitionMethods and the account filter matches:

• a non-default integration takes the lines whose vendor account is in its accountNoList, or every line of the vendor when the list is empty
• the default integration takes every line whose vendor account is not listed on another integration of the vendor

toggleAutomaticExport sets the checkbox to whether any integration applies. For EDI integrations with account numbers the result is the same as before. The one difference follows the backend: a line whose account is on no list is now flagged for export when the vendor has a default integration.

Only EDIFACT_ORDERS_EXPORT configs take part. Claiming configs store their settings in the same vendorEdiOrdersExportConfig structure, and the current lookup on master searches all configs of the vendor by account number without checking the type. So a claiming config with a matching account number decides the checkbox today, by its own acquisition methods.

The hint renders one of three states: the name of the single matching integration with its transmission method below the checkbox, an info popover listing several matches, or a warning icon when nothing matches while the checkbox is on. Several matches are not an error in the backend: the first scheduled job sets lastEDIExportDate and the others skip the line, so the popover says so. The hint is hidden while the checkbox is off, for manual orders (never exported, see UIOR-890), while the configs load, and in order templates, which pass no configs. The detail view fetches the configs only when the hint can show something.

Deliberately not part of the hint: lastEDIExportDate and the workflow status. The hint says which integration applies to the line, not whether the next run will take it.

Screenshots

show matching integration

no matching integration

multiple matching integrations

Refs UIOR-1556

Pre-Merge Checklist

Before merging this PR, please go through the following list and take appropriate actions.

• I've added appropriate record to the CHANGELOG.md
• Does this PR meet or exceed the expected quality standards?
  • Code coverage on new code is 80% or greater
  • Duplications on new code is 3% or less
  • There are no major code smells or security issues
• Does this introduce breaking changes?
  • If any API-related changes - okapi interfaces and permissions are reviewed/changed correspondingly
    • No interface or permission changes.
  • There are no breaking changes in this PR.

[github-actions]

Jest Unit Test Results

    1 files  ± 0    313 suites  +1   6m 54s ⏱️ -1s
1 225 tests +29  1 217 ✅ +29  8 💤 ±0  0 ❌ ±0 
1 233 runs  +29  1 225 ✅ +29  8 💤 ±0  0 ❌ ±0 

Results for commit 6513cc0. ± Comparison against base commit 0a365d1.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
93.6% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud