When the system auto-generates a default Update 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.

Here are some common cases where the system auto-generates a default Update Set:

When the user logs in for the first time

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 the default set is marked as Ignored or Completed

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.

When the user changes application scope

The system auto-generates a new default Update Set for a scope when the following conditions occur:
  • You change application scope and
  • Your preferred Update Set is Complete or Ignored and
  • There is no In-Progress default Update Set for the new scope