Update capturing mechanism of the system

[Aman Sharma2]

Hi !

As I am aware of what all updates are captured in an update set (configuration records) and what not (data records), 

still I'm curious to know how the system decides what all records to capture in the update set. Where is the logic for this written? If I have my custom table (let's say, for some custom configuration), where I can add my logic to auto-capture the changes in the update set?

Any help is appreciated.

Thanks in advance!

[Community Alums]

Hi @Aman Sharma2 ,

The configuration changes we made in the system get captures in Update set. Such as Tables, fields, list and form layouts, form sections, scripting such as business rule, client script, UI Page, script include, UI Macros, UI scripts, UI policies etc., workflow, system properties, reports, views etc.

Note: Properties that are tagged as Private are excluded from update sets.

The transnational data such as incident, change, problem, knowledge, CI's etc data records, scheduled jobs, schedules, users, group, email etc are not get captured in update set.

[Ayush Roy]

I am using system property as the variable container, and it gets updated as the scheduled job is run daily.
Even though I have marked it as Private it's still getting captured in the update sets of other developers, even though they are not updating it, it's updated by the system.
Please provide a solution for this issue. I don't want the system property captured in the update sets now.

[Aman Sharma2]

I appreciate that!

But my question is slightly different. I wanted to understand the actual backend logic executing to capture or ignore them.
At last, all the things in the platform are stored in the form of tables and records only. So how the system decides which record to capture?

For example; the system inserts a record in the [sys_update_xml] table when a business rule is created/updated (record in [sys_script] table), but not when a user is created (again a record, but in [sys_user] table).

Hope you got my concern.

Thanks!