Skip to content
Tutorials Center
My learning

Topics

Lesson 35 of 39 ยท ITSM and Administration

Update Sets, Instances and Upgrades in ServiceNow

Move ServiceNow configuration between dev, test and production with update sets, handle collisions and previews, and plan clones, upgrades and scoped application deployments.

A company never edits production directly. It builds in a development instance, checks in test, and promotes to production. ServiceNow's classic vehicle for carrying configuration between instances is the update set. This lesson explains how update sets work, how to avoid their traps, and how clones, upgrades and application deployment fit around them.

Instances, update sets and upgrades are described here but cannot run on this site. The stand-ins model collision detection and ordering in JavaScript.

Instances and the usual path

A typical customer has at least three instances, each at its own URL: company-dev.service-now.com, company-test.service-now.com and company.service-now.com (production). Large organizations add sandbox, UAT and training instances. Configuration is not shared between them, so a business rule created in dev does not exist in test until you move it.

Configuration (metadata) travels by update set or application; data (incidents, users) does not, unless you import it. A clone copies production over a lower instance, replacing its data and configuration, to refresh a test environment with realistic content.

What an update set records

An update set (sys_update_set) is a container for customizations. While an update set is the current one (chosen in the Update Set picker in the header), every change you make to tracked configuration records is captured as an update (sys_update_xml): a snapshot of the XML for that record, such as a business rule, a UI policy, a form layout or a flow.

Tracked: scripts, UI configuration, workflow definitions, ACLs, tables and fields (dictionary), and system properties (when flagged). Not tracked: most data (incidents, users, groups), and some tables excluded to avoid noise.

Steps:

  1. Create an update set (System Update Sets > Local Update Sets > New), with a clear name like STRY0012345 - Add priority rule. Name it after the story or ticket.
  2. Make it current and do your work.
  3. Mark Complete when finished. It then cannot be edited.
  4. Export to XML, or let the target retrieve it directly.
  5. On the target instance: Retrieve Update Sets from the remote instance (System Update Sets > Retrieved Update Sets), or Import Update Set from XML.
  6. Preview the update set. The preview looks for problems.
  7. Commit to apply it.

Preview problems

Previewing finds:

  • Collisions: the target already has a newer version of a record the update set changes, so committing would overwrite someone else's edit. For each, decide Skip remote update or Accept remote update.
  • Missing references: the update set needs a record (a table, a role, a group) that does not exist in the target.
  • Uncommitted dependencies: it relies on another update set you have not loaded.

Resolve each item before commit. If you commit with unresolved problems, you may break a feature in production.

Rules for clean update sets

  1. One logical change per update set; keep them small.
  2. Do not mix data into configuration work.
  3. Watch for default update sets: changes saved to "Default" cannot be moved easily. Always select your set first.
  4. Apply update sets in the same order they were created, and batch them in an Update Set Batch (parent and children) for ordered deployment.
  5. Do not rely on sys_ids from data such as groups: reference by name or system property.
  6. Back out by using the update set's Back Out action (if allowed) or by preparing a reversing change.

Applications and the Source Control route

Larger work is better built as a scoped application, in App Engine Studio or Studio. A scope gives your tables and scripts a namespace (x_acme_expenses_...), clean boundaries and a package you can publish to an Application Repository, or link to Source Control (Git). Teams install a version in the next instance, and upgrade by installing a newer one. For global configuration, update sets still work. For anything product-like, prefer applications.

Clones and upgrades

  • Clone: production data and configuration copied to a target (usually test or dev). Plan exclusions (large tables), data preservers (keep some target tables, such as your test users), and cleanup scripts. After a clone, outbound email, integrations and schedules must be checked: clone-safe setups disable them on the target to avoid emailing real customers.
  • Upgrade: ServiceNow releases families two or more times per year (named alphabetically in the past, such as Washington DC, Xanadu, Yokohama). You schedule an upgrade of each instance, test first on a sub-production instance, review the Upgrade History and Skipped changes, and use Upgrade Center to see what changed. Customizations on base records are the biggest source of upgrade pain, because upgrade must keep your version or the new one. Prefer extending the platform (new tables, flows, scoped apps) over editing base records.

Skipped records after an upgrade appear in System Diagnostics > Upgrade Center > Skipped Changes (the exact menu label depends on the release). Review them: you decide whether to keep your customization or accept the new base version.

Model collisions

The first stand-in compares an update set with the target to find collisions, new records and updates.

JS Stand-in: preview an update set

Press Run (or Ctrl + Enter) to see the console output here.

No output.

The second stand-in orders update sets by dependency, as an update set batch would, so that a field exists before a rule refers to it.

JS Stand-in: order update sets by dependency

Press Run (or Ctrl + Enter) to see the console output here.

No output.

Check your understanding

Quick check ยท 4 questions

of 4 answered You scored / 4 ยท perfect!

  1. 1. What does an update set capture?

    Update sets hold snapshots of tracked configuration records; ordinary data is not included.
  2. 2. Which preview result means the target has a newer version of a record you are about to overwrite?

    A collision means the target record changed after your update was made.
  3. 3. Why choose your own update set before you start work?

    The Default update set is not meant for promotion, so work saved there is difficult to transport.
  4. 4. What is a clone?

    A clone refreshes a lower instance from production; after it, integrations and email must be checked.

Summary

  • Configuration moves between instances in update sets (or applications); data does not.
  • Preview finds collisions, missing references and dependencies; resolve them before commit.
  • Keep update sets small, named by story, and applied in order.
  • Clones refresh test instances; upgrades are easier when customizations avoid base records.

Next: Dashboards, Analytics and Knowledge Management