Skip to main content

10.x → 11.x

This guide describes the breaking changes required when upgrading from the 10.x to the 11.x release of enosix Cloud UI.

Sales Document UI​

SalesDocSettings.Header.Mode moved to SalesDocSettings.Mode​

10.x: The operating mode (Simulate, Create) was read from SalesDocSettings.Header.Mode.

11.x: Mode is now a top-level field on SalesDocSettings, a sibling of Header rather than a property of it. HeaderContext no longer has a Mode field.

This change was made so that the operating mode — which controls the whole document flow, not just header behavior — is no longer nested under header-specific data. Any host application, Test Harness configuration, or saved INITIAL-CONTEXT payload that sets Mode under Header must be updated.

  "SalesDocSettings": {
+     "Mode": "Simulate",
      "SalesDocumentId": "4500000001",
      "Header": {
-         "Mode": "Simulate",
          "SalesDocumentType": "OR",
          "SalesOrganization": "1000",
          "DistributionChannel": "10",
          "Division": "00",
          "SoldToParty": "100000"
      }
  }

Update any integration, saved Test Harness configuration, or automated test fixture that constructs this payload to move Mode out of Header and onto SalesDocSettings directly.

caution

If Mode is left under Header after upgrading, it will be silently ignored. The app will fall back to its default mode (Create) instead of the intended mode, since HeaderContext no longer defines a Mode field.

Variant Configuration UI​

The Variant Configuration UI is not impacted by this release. Existing integrations, embed configurations, and initial context payloads continue to work without modification.