Skip to content
Tutorials Center
My learning

Topics

Lesson 8 of 39 ยท Platform and Navigation

Scoped Applications and Update Sets

Learn how global and scoped applications differ, how update sets capture and move changes between instances, and how to avoid collisions and lost work.

You build in a development instance and need to get the result into test and production. ServiceNow gives you two mechanisms: update sets (a bag of captured changes) and applications (a named container with its own namespace, deployable from an application repository or source control). Understanding both avoids the classic "it worked in dev" disasters.

Global versus scoped

Everything lives in a scope:

  • Global is the shared, default scope. Anything in it can see and change almost anything else, which is easy but can collide.
  • A scoped application has a unique scope name such as x_acme_laptops, created through Studio or App Engine Studio. Its tables, scripts and files are prefixed with that name, and access to other scopes is controlled by cross-scope privileges.
Global Scoped
Namespace Shared Own prefix (x_company_app)
Table names u_ custom prefix x_company_app_table
Isolation Low High, by default other scopes cannot change it
Packaging Update sets Update sets or application repository
Best for Small tweaks to the platform New applications

The application picker in the header (the gear/Settings panel, Developer tab, or the application picker in classic UI) shows which scope you are working in. A frequent mistake is building a global change while the picker is set to a scoped app, or the reverse, so look before you create records.

What is an update set?

An update set is a record in sys_update_set. While it is your current update set, every configuration change you make (a business rule, a form layout, a UI policy) is captured as a row in sys_update_xml. Data records such as incidents are normally not captured, only configuration.

flowchart LR
  A["Dev: build in<br/>current update set"] --> B["Mark Complete"]
  B --> C["Export XML or<br/>retrieve from remote"]
  C --> D["Test: preview<br/>and commit"]
  D --> E["Prod: preview<br/>and commit"]

The usual promotion path for an update set.

Working with update sets

  1. Open System Update Sets > Local Update Sets and press New. Give a descriptive name, for example LAPTOP-12 request form changes.
  2. Make it your current update set (the update set picker in the header, or the Make this my current set link).
  3. Do your work. Each change appears in the Customer Updates related list.
  4. Set the State to Complete when finished.
  5. In the target instance, define a remote instance (System Update Sets > Update Sources) and use Retrieve Update Sets, or export the update set as XML and Import Update Set from XML.
  6. Open the retrieved update set, press Preview Update Set, resolve any problems, and then Commit Update Set.

The preview step is where you find collisions: the target record changed after the source was captured. You can accept the remote update, or skip it, case by case.

Python Preview collisions (stand-in)

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

Program input ยท what you'd type while the program runs

Type the answers before you press Run, one per line. Each time the program reads a line (with input()), it gets the next line from this box.

Habits that save you

  • One update set per task, small and named after the ticket. Large "everything" update sets are hard to review and often collide.
  • Check the current update set before you start. The Default update set catches changes if you forget, and it cannot be moved cleanly.
  • Do not capture test data or unfinished work. Back out a change by Back Out on a committed set if necessary, but test first.
  • Keep the Parent update set only for batching a series of finished sets.
  • Some changes are not captured (for example, some system properties and records in excluded tables); the documentation lists them. Keep a note to repeat these steps manually on target instances.
  • Do not edit a committed update set's contents; create a new one instead.

Application repository and source control

Scoped applications can also be published to the application repository, which holds versions that other instances install, or linked to Git, which makes changes visible to a normal code review workflow. Many teams use update sets for global changes and source control for scoped apps. Either way the guiding rule is the same: one source of truth, versioned, reviewed and promoted in order.

Python Choose a delivery method (stand-in)

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

Program input ยท what you'd type while the program runs

Type the answers before you press Run, one per line. Each time the program reads a line (with input()), it gets the next line from this box.

Check your understanding

Quick check ยท 4 questions

of 4 answered You scored / 4 ยท perfect!

  1. 1. What does a scoped application give you over global customization?

    A scope prefixes and isolates the application's artifacts; cross-scope access must be granted.
  2. 2. What is the purpose of Preview Update Set?

    Preview checks the incoming changes against the target and lists problems to resolve.
  3. 3. Which approach is recommended?

    Small named sets are easy to review, move and back out.
  4. 4. What do update sets capture by default?

    Update sets track configuration; data is moved separately.

Summary

  • Global scope is shared; scoped apps have their own prefix and isolation.
  • Update sets capture configuration while they are your current set.
  • Promote by retrieving or importing, previewing, resolving problems and committing.
  • Keep sets small, named and finished before moving them.

Next: Tables and Records