What is the purpose of an update set?
An update set tracks changes to applications and platform features, then groups them together so they can be moved from one instance (dev instance) to another (test instance)
How do Update sets work?
Update sets work by writing changes from tracked tables into the Customer Update [sys_update_xml] table
What happens to older changes in an update set?
They are overwritten with the new changes captured in the Update Set
When we merge updates sets, what happens when a same object’s changes (like an incident form) have been tracked by many update sets?
The most recent change to that object will be moved to the merged update set
What is the Base System Update Set?
The Default instance update set.
It captures changes made to the instance without adding them to user-created update sets
What is captured in an Update set?
Customizations and configuration changes (i.e. Process records)
What is not captured in an Update set?
Check doc Move a dashboard with an update set
Where to navigate to create an update set?
All > System Update Sets > Local Update Sets > New
How to export a update set?
How to upload an update set?
What are 3 precautions to take regarding Update sets?
How to retrieve an Update set from a remote instance?
(Check doc Retrieve an update set)
What are some examples of standard integrations in ServiceNow?
What are the most common processes required for integration?
What techniques can be used for integration?
Which module provides a single solution for integration with 3rd party services?
Integration Hub
(used to extend Flow Designer capabilities)