Dear Sage X3 Community,

Following our previous posts:

• Important Alert: Chrome/Edge Version 144 Impact on Sage X3 Action-Menu Buttons
• New Syracuse Server Hotfixes Now Available

we would like to share an additional update regarding customers running Syracuse versions not covered by the Lifecycle Policy.

 Background

As previously communicated, Chromium-based browsers v144 (Chrome / Edge) may cause Sage X3 action-menu buttons to stop working:

• Affected: Syracuse 12.22 and earlier
• Not affected: Syracuse 12.23 and above

For supported versions, this issue is already resolved via the recently released Syracuse Server Hotfixes.

️ Temporary Browser Workaround (Use at Your Own Risk)

For non-maintained Syracuse versions, a temporary workaround has been identified at browser level.

️ Disclaimer

• This workaround is provided for information purposes only.
• It is applied entirely at the customer’s own risk.
• It does not replace an upgrade to a supported Sage X3 version.
• Sage’s recommendation remains to upgrade to a release covered by the Lifecycle Policy.

Google Chrome

Option 1 – 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)

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

️ Notes

• Always test in non-production environments
• Be aware of potential side effects and security implications
• Environments using this workaround may fall outside standard support conditions
• Sage Support may require removal of the workaround or an upgrade before further analysis

 Final Reminder

This workaround is intended only as a temporary mitigation for legacy environments.
For long-term stability and full support, upgrading to a Sage X3 release within the Lifecycle Policy remains strongly recommended.