What is an Update Set?
An Update Set is a container that captures configuration changes (not data changes) made to a ServiceNow instance. When you edit a Business Rule, create a Script Include, or modify a form layout, those changes are recorded in the current Update Set.
What Update Sets capture
Update Sets capture: Business Rules, Script Includes, Client Scripts, UI Policies, UI Actions, Form layouts and views, Catalog items, Workflows and Flows, ACLs, System Properties, Dictionary entries.
Update Sets do NOT capture: data records (incidents, users, CIs), application data, attachments.
Setting the current Update Set
Always set your current Update Set before making changes. Go to the Update Set picker at the top right of the developer instance, or navigate to System Update Sets > Local Update Sets and mark yours as current.
If you forget to set one, changes go into "Default" — which becomes a maintenance nightmare when you need to isolate changes for release.
Moving an Update Set
- Mark the Update Set as Complete in the source instance
- Export: right-click > Export to XML
- In the target instance: System Update Sets > Retrieved Update Sets > Import XML
- Preview the Update Set to check for conflicts
- Commit the Update Set
Merging Update Sets
If you have multiple Update Sets that belong to the same release, merge them before moving to test. Select all, right-click, Merge. This creates a single Update Set that can be moved as one unit.
Common mistakes
Mistake 1: Making changes in production directly instead of going through Update Sets. This creates drift that is impossible to replicate or reverse cleanly.
Mistake 2: Committing an Update Set without previewing first. The preview step catches conflicts — records that exist in the target with newer sys_updated_on values.
Mistake 3: Moving data records via Update Sets. Update Sets are for configuration only. Move data via import sets or direct scripts.