Dear Sage X3 Customers,

Following our recent communications regarding the impact of Chromium-based browsers on Sage X3 user interface behaviour, we would like to provide an additional update.

It has been observed that, in certain Chromium browser releases, some Sage X3 UI action elements may stop functioning.
This issue affects Syracuse versions 12.22 and earlier, while Syracuse 12.23 and above are not impacted.

A temporary workaround has been identified that customers may consider using while awaiting hotfixes or planning an upgrade to a Sage X3 version covered under the Lifecycle Policy.

Important Disclaimer

• This workaround is provided for information purposes only.
• It must be implemented entirely at the customer’s own risk and responsibility.
• Sage cannot be held accountable for any issues, regressions, security exposure, or operational consequences resulting from the actions described below.
• This workaround is temporary and does not replace the need to upgrade to a supported and maintained Sage X3 release.

Sage’s official recommendation remains to upgrade your environment to the latest Sage X3 release.

Affected Versions

• Syracuse 12.22 and earlier: UI action elements may stop functioning
• Syracuse 12.23 and above: No issues observed

Temporary Workaround – Chromium Browser Flag (Use at Your Own Risk)

Disabling a specific Chromium feature flag may temporarily restore Sage X3 UI behaviour.

Google Chrome

Option 1 – Using Chrome Flags

1. Open Google Chrome;
2. Navigate to: chrome://flags
3. Search for “boundary event”, or directly locate:
   #boundary-event-dispatch-tracks-node-removal
4. Set the flag to Disabled;
5. Clear the browser’s Cache;
6. Relaunch Google Chrome;

Option 2 – Launch Command (All Chrome instances must be closed)

"C:\Program Files (x86)\Google\Chrome\Application\chrome.exe" --disable-features=BoundaryEventDispatchTracksNodeRemoval

Microsoft Edge

Currently, this option does not appear to be available via Edge flags.

In Google Chrome, you can disable the flag, and then every time you launch the browser after that, the flag setting is used.

However, in Edge, you need to run the below command every time you launch the browser:

 "C:\Program Files (x86)\Microsoft\Edge\Application\msedge.exe" --disable-features=BoundaryEventDispatchTracksNodeRemoval

Alternatively, you can create a Microsoft Edge shortcut where this command is already included for your Sage X3 domain:

"C:\Program Files (x86)\Microsoft\Edge\Application\msedge.exe" --disable-features=BoundaryEventDispatchTracksNodeRemoval http://servername:8124

Testing and Security Considerations

Before applying any of the above changes, customers should:

• Test all modifications in a dedicated non-production environment.
• Be aware that disabling or altering Chromium behavior may introduce unexpected side effects.
• Apply standard validation and change management procedures, as with any technical modification.
• Understand that disabling automatic Chromium updates may expose systems to security risks due to missing future patches.
• Involve IT and security teams to assess and approve the associated risks.

Supportability Notice

Please note that:

• Environments relying on this workaround may fall outside standard support conditions.
• Sage Support may require the workaround to be removed or the environment to be upgraded before further investigation.

We strongly encourage customers to plan an upgrade to a Sage X3 release within the Lifecycle Policy, which remains fully supported.

Thank you for your attention and cooperation.