configuration changes that are not tracked by update sets

[harsha328]

Hi,

Can anyone tell me the list of configuration changes or important changes that are not tracked by an update set?

I understand that, update sets capture configuration changes and leaves out task or process data. But I have heard that update sets leave out a few important changes. I would like to know what those changes are.

Thank You,

Harsha.

[Deepa Srivastav]

Do mark the answer Correct or let me know if you need any other info on this..

[Andras Kisgyorg · Accepted solution]

Hi Harsha,

Yes, there are couple significant things which are not captured by update sets,

below is not an exhaustive list:

- Plugin activation: not captured in your update set, you have to make sure appropriate plugins are active on your target instance when moving your update sets

- Scheduled jobs (as mentioned above)

- user Groups - this maybe obvious but important to mention, as groups are often put into condition builders or scripts or assignment rules by referencing their sys_id. They may be   exported and imported into target instance (rather than recreated) to match sys_id.

There may be some more which others may add in comments below.

Please let me know if this helped.

best regards,

Andras

[akashsrm100]

HI harsha

This knowledge article will give you some detail what changes are not captured by update sets

ServiceNow KB: Checking which records will be captured within an Update Set (KB0535262)

Administrators can configure options for update sets, such as excluding certain fields from updates .

To exclude a field from updates, add this dictionary attribute to the field:

update_exempt