Default update set
Summarize
Summary of Default Update Set
The default update set is crucial for managing changes within a specific application scope in ServiceNow. Only one update set can be designated as the default for any given scope, ensuring organized and efficient management of updates. Setting an update set as the default reassigns the default status to that set while marking others as non-default.
Show less
Key Features
- Default Set Configuration: Setting the Default set field to true designates an update set as the default for its scope, while automatically marking others as false for the same scope.
- Global Default Set: The global default update set allows changes without adding them to user-created update sets. This set should remain unchanged and is essential for system functionality.
- Auto-Generated Default Set: The system auto-generates a default update set when there isn't one for the current scope, ensuring continuous tracking of changes. This includes scenarios like an admin's first login or when changing application scopes.
Key Outcomes
By effectively managing your default update sets, you can ensure that all changes are captured without loss, maintain organization across application scopes, and avoid issues related to untracked updates. It is recommended to refrain from ignoring or completing the default set to prevent unnecessary auto-generation of new sets.
Only one update set can be the default set for any application scope.
- The update set becomes the default update set for its scope.
- The system sets Default set = false for all other update sets with the same scope. This ensures that there is only one default update set for each scope.
Global default set
Use the global default update set to make changes to an instance without adding the changes to any user-created update sets. The global default update set is the set where Default set = true and application scope is global. The global default set (regardless of the Name of the set) provides system functionality and should not be changed, deleted, or moved between systems. Use this update set to make changes to an instance without adding the changes to any user-created update sets.
Auto-generated default set
At all times, to ensure that no updates to an instance are lost, the system ensures that there is a default set for the user’s current scope. If the system finds that a default update set does not exist (or is marked Ignored or Completed) for the current scope, then the system auto-generates an update set and sets Default set = true.
- The very first time that an admin logs in, the system sets the system’s global default
update set as the administrator’s update set. In addition, the application picker sets
the administrator’s application scope to global.If a global default update set does not exist (or is marked Ignored or Completed), the system creates a new update set for the global application scope and performs the following actions:
- The system sets Default set = true for the new set.
- The system sets the name of the new set to start with the name of the former default set and appends the next numeral (in the sequence SetName, SetName 1, SetName 2, …, SetName n).
- The system sets the newly created set as the administrator’s update set.
- When a user marks the default set for a scope as Ignored or Completed (not a recommended practice), the system immediately auto-generates a new default set for the scope.
- The system auto-generates a new default update set for a scope when all the following
conditions occur:
- You change application scope.
- Your preferred update set is Complete or Ignored.
- There is no In-Progress default update set for the new scope.