Complete to Ignore Update Sets in PROD

[dormarchan]

Hi Experts and Gurus,

When we apply Update Sets in PROD, I believe that the XMLs overwrites those old ones. In this respect, As an analogy, I view the update set as a basket of goodies. Since they are applied, I think I don't need the update set anymore. It is like keeping aside the basket after I empty it. I am inclining to set them to Ignore state.

What is my concern? Well, at our DEV instance, those update sets (still in Complete) are still selectable for merging. Now, we have hundreds and it just simply time consuming.

So, can we set the update sets to Ignore at PROD after they are applied?

Thank you for your feedback.

Salvador

[David Pleasance]

I just did this in our Production instance - thank you.

[Pradeep Sharma]

Hi Salvador,

You should always set Completed update sets on the production instance to Ignore. This state will also ensure that the update set is not committed again when cloning the instance.

Here are the reference links.

Update Sets Best Practices - ServiceNow Wiki

Using Update Sets - ServiceNow Wiki  

Please let us know if you have any additional questions.

I hope this answers your question

[Bill Ye Zhang]

@Pradeep Sharma  @Chuck Tomasi Hi Pradeep, Chuck,

Could you confirm from a ServiceNow employee's side as there is a contradiction around this topic?

In this article, Allan explained that if left as 'Complete', after a clone, an update set in Production will have a 'Previewed' duplicated update set in the Retrieved Update Set list in the target instance.

However, in this article, Nia said the 'Previewed' update set in the Retrieved Update Set list is in the Production instance.

Can you please confirm which one is the actual scenario?

Thanks,

Bill

[dormarchan]

Thanks All,

I think I'll will also do a housekeeping for those very old Ignored update sets...probably a Scheduled Job that deletes a year-old u/sets (for a start).

Regards,

Salvador