Sage X3 development guidelines

The Sage X3 development platform provides virtually unlimited capabilities for personalization and customization (specific development).

Sage provides guidelines that help you keep your developments safe from conflicts with future application patches contained in the Sage X3 releases and possible future upgrades.

Developing and extending Sage X3 within the correct guidelines also helps you manage your developments and deliver them more easily to your customers.

The rules cover items such as the following ones. This list covers only a few examples and is not exhaustive.

• As much as possible, do not protect a standard field with a specific activity code.

• Do not change standard data types.

• Do not develop inside supervisor entities (objects, screens, tables, and so on).

• As much as possible, group your specific fields into specific screens or tabs that you will add to standard windows, rather than inserting them into standard screens.

• As much as possible, group your specific business logic inside object actions rather than field actions.

Those rules evolve as new capabilities are added by Sage to safely extend the Sage X3 business logic.

The Sage X3 customization audit tool reviews your customizations (specific developments) and highlights elements that create risk or are non-compliant with development guidelines. You can then use the resulting dashboard to drill into the details and fix the identified issues.