Is it good practice to set Update Sets to State : Ignore after Completion in Dev, Test & Prod

[WazzaJC]

Is it good practice to set Update Sets to State : Ignore after Completion in Dev, Test & Prod

Hi Community friends/colleagues,

Is it good/recommended best practice, once one has successfully completed update sets in a client's Dev, Test and Prod instance, to eventually set the final State to 'Ignore', after successful migration of update sets through each environment?

I am sure I read somewhere in ServiceNow documentation, that this is a recommended approach, in order to avoid issues when clone backs are performed, it will ensure update sets are not reapplied, in case this may happen.

I just wanted to find out is this what other developers here are doing, is it necessary and is it recommended, rather than only leaving a committed update set in State : Complete.

I would appreciate any feedback in this regards, many thanks. 🙂 

[SanjivMeher]

We never mark any update set to Ignore in Dev, Test or Prod after committing. It doesn't make sense to me for a update set committed to marked ignored. Though I have come across post, where people recommend marking a Prod update set as ignored.

We mark it ignore in Dev, only if I dont have to move it to the next environment. 

So far, I have not seen any issues for not marking update set ignore after committing it. 

[g k1]

I do use Ignore in Dev, like while something is not working and I create a new update set for that and later on I acn't able to find out the solution or something else then I put it under ignore other wise I don't use ignore 

[swathisarang98 · Accepted solution]

Hi @WazzaJC ,

As i can see yes it seems to be one of the best practices to make the update set state to 'Ignore',

Please find the below article which supports this,

Community article,

https://www.servicenow.com/community/now-platform-articles/why-you-should-set-your-completed-update-... 

Servicenow Doc:

What to do next

For completed update set on the production instance, you should always change the state to Ignore. This state ensures that the update set is not committed again when cloning the instance.

https://docs.servicenow.com/bundle/tokyo-application-development/page/build/system-update-sets/task/... 

Please mark this comment as Correct Answer/Helpful if it helped you.

Regards,

Swathi Sarang

[jaredfhealy2]

Just to share the one benefit I have seen.

When you mark update sets as "Ignore" in production, future clones to lower environments will keep the update sets in that state for everything that has made it through all environments to production.

Now when you retrieve update sets, there is less comparison work that your ServiceNow instance needs to do to see if the update set is already present in your instance. Any update set that is set to "Ignore" is not even retrieved in the query to evaluate it.

My experience is that as your instance age increases and the volume of update sets increases, your update set retrieval will remain much quicker using this method.

Thanks,
Jared