When the Default Update Set is needed

[d-aizawa]

Hi.

I have been using ServiceNow for the first time in almost a year.

Let me ask you a question about Update Set.

I was told to move to the default UpdateSet instead of deleting the unnecessary Updates recorded in the UpdateSet.

But when do you need the Update record you thought you didn't need again?

Is there a case where you have a problem by deleting the Update of UpdateSet?

Thank you!

[Community Alums]

Hi @d-aizawa ,

Basically Default update set is system generated update set, if you tried to ignore/completed the default update set again system will generates new update set with the name Default1 update set.

Default update set:

Only one update set can be the default set for any application scope.

To set an update set to be the default set, you set the Default set field to true. When you set Default set = true, the following actions occur:

• 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.

These are some common cases where the system auto-generates a default update set.

• 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.

Mark my answer correct & Helpful, if Applicable.

Thanks,
Sandeep

[d-aizawa]

Thank you for answering the question.

I would like to know why unnecessary updates should not be deleted.

Thank you!

[Community Alums · Accepted solution]

Hi @d-aizawa ,

I believe you lose the record of the changes, but not the changes themselves. So if you made some changes to a form in an update set, you delete that update set, the changes remain, but the history of those changes contained in the update set will go away.

Normally, you don't want to delete update sets...   you want those records of changes in the system in case they are ever needed to bail you out of trouble.   If you don't want these things applied, you could move then to a different update set and set it to ignore, rather than delete those records.   The caveat there is that if you made multiple changes to the same field, it only records the most recent state so if you move the latest update of 4 made, it's removing all updates to that record.

Mark my answer correct & Helpful, if Applicable.

Thanks,
Sandeep

[Sourabh26]

Hi,

You are using the default update set when you do not want to move the related changes (script or configuration changes) to other instance (suppose from your development instance to uat or prod).

Now if you need to move only some specific changes then you are creating your new update set and then capture that changes on that (for ex. changes on some business rule) and then after will move it to uat/prod.

Regards,

Sourabh