Track Page Configuration Changes

Hi ​@Tharshan SM,

IFS Cloud does not provide an out‑of‑the‑box capability to track page configuration changes in the level of detail you described (i.e., what was changed, which projection it belongs to, who made the change, and when it was done). While page configurations created via Page Designer are stored in the database as part of the Configuration Layer of the application architecture, this storage is designed to hold the current state of the configuration rather than maintain a historical audit trail of changes.

As a result, there is no standard audit mechanism or system log available to track configuration changes over time. In particular, the system does not maintain version history, “last modified by,” or timestamp tracking for page configuration updates in a reliable or supported way. Although configuration data resides in backend tables, these are treated as internal implementation details and are not intended or documented for audit or tracking purposes. This means that querying the database directly to derive such information is neither reliable nor recommended, as table structures and behaviors may change between releases without notice.

Hi ​@Tharshan SM,

Also refer to the following community post: 

Not possible to track versions of pages configurations | IFS Community

From my research, there may be technically possible to build a custom solution around this.

One possible approach would be to monitor the AurenaPageDesigner projection, specifically the PublishConfigurations2 call, and then use the ConfigurationHandling projection entities such as ConfigModelData / QueryConfiguredPagesSet to retrieve the related configured page data.

In theory, a custom workflow could capture and store details such as:

• current user
• date/time
• page/context/projection information
• previous configuration JSON
• new configuration JSON

The previous and new JSON payloads could then be compared to identify what was changed, by who and when. A custom entity could be used to store this data.

That said, this is quite a complex workaround for what is essentially a governance/audit requirement. This should be a native IFS Cloud feature.