Add Audit attributes to the System's Site Property related entities
1661
Views
20
Comments
New
Service Center

Add the Audit's commonly known attributes:

- CreatedAt

- CreatedBy

- ModifiedAt

- ModifiedBy

To the System's Site Properties entities (Site_Property, Site_Property_Definition and Site_Property_Shared).

I know there are some audit logs when a user changes a site property, but having these in the entities would be helpful.


site_property.png

you could expand this idea to other already mapped system assets such as timers (eg. meta_cyclib_job) as well.


Changed the category to
Database
Merged this idea with 'Record site property last changed date and user name' (created on 22 Jun 2023 02:39:30 by John Porra)

Add attributes to Site properties which records the date the property was last changed and by whom so we can tell at what date/time a property was changed.

This can be useful in diagnosing issues.  if we know who it is we can ask them why they made the change and what their intent was.

if the site property last updated by is Null, that would represent it was part of the deployment process.

These attributes would only need to be displayed in the service center, not in the Service Studio


Merged this idea with 'Save information from Site Property changes' (created on 20 Aug 2024 14:34:30 by Antonia Tajes)

For big factories with many developers and different teams, it would be very useful to show in SC the information about last change of Site Properties (when and who), like we have for actions - Last modified by xxx@xx.com on 12/12/2024 at 12:12 AM

Really needed!

Good idea, but it already exists so I need to merge yours into it.

Merged this idea with 'Log Site Property Changes for Better Traceability' (created on 20 May 2025 06:46:46 by Shipra Joshi)

It would be valuable to have a logging mechanism that records every change made to Site Properties—like value changes. These logs could appear either in the General Log section or in a dedicated Site Property Logs section, similar to how Timer logs are tracked.

Each log entry should ideally include:

  • Site Property Name

  • Application Name

  • Module Name

  • Previous Value (masked if marked sensitive)

  • New Value (masked if marked sensitive)

  • Changed By

  • Timestamp

Merged this idea with 'Add Update Tracking Columns to Site Properties' (created on 25 Jun 2025 06:39:21 by Venkatesaiya)

Currently, the Site Properties details page includes columns such as Name, Description, Datatype, Effective Value, and IsSecret. 


                 I propose adding some more columns: Updated By, Updated On, and Previous Value. These additional columns will help track when a site property was last updated, who made the change, and what the previous value was. This information is crucial for auditing and understanding the purpose of each change. In the short term, we may remember recent changes, but over longer periods (More than 6 months or year), it becomes difficult to recall the history. Although logs are captured in the service center when updates occur, they are not retained for long durations, and searching for specific changes becomes little hard . Adding these columns would provide a long-term, accessible history of updates, which is particularly useful for applications running over extended periods or when implementing new business-related site properties. 

Good idea. These columns will help track changes better and make it easier to understand who updated what and when, especially in the long run.

Agree, this would really help in tracking.

Thanks for the Valuable Comment Guys

Merged this idea with 'Site property changed logs' (created on 05 Sep 2025 18:14:37 by Felipe Horta)
2026-01-28 14-34-48
Felipe Horta
Champion

When a site property is changed, save logs (general logs, for example) with value before and after change. Save user name too.


Changed the category to
Service Center
Merged this idea with 'Add ability to track which user updates Site Properties' (created on 11 Oct 2025 20:48:08 by Sangam Bhondele)

Idea Description: 

Currently, OutSystems does not provide any way to know which user has updated or modified a Site Property. There’s no link between Site Properties and the User entity, which makes it difficult to audit or trace configuration changes.

It would be very helpful if the platform could record and show who changed a Site Property and when it was changed, to improve accountability and auditability.