Working with update sets

will_smith · ‎03-25-2016

Can anyone guide me on how to better handle update sets? I am a newer administrator and am finding that when I am working on 3-5 different items at a time, some of the changes that go into an update set fall through the cracks and get applied to the inappropriate update set. Then I have to go back and figure out what update goes in what update set bucket. Could I get some community guidance on how to keep better track of the changes made in update sets, especially the ones the have 100+ changes?

Also, when I run a collision report - is there a way to go back to that collision report or would I need to rerun it?

gemini17 · ‎03-25-2016

Hey William:

To start of you go to Local update Sets, and create a new update Set, for whatever customizations you are planning. Give it a unique name: Like Releasexx_Configuringxx_your Initial_Date, submit and make it your current update set. The state will be in progress. for some reasons, you are going to stop working on it, make sure after all the updates, get out of it. When you log back again, your update set will show the same name, unless you are going to work on the same, you have to go to update sets and create a new one. You have to pay attention to what update set is being displayed on the update set picker window.

For further reading follow this link: Using Update Sets - ServiceNow Wiki

Hope this is helpful.

Hit it correct as you see the impact

Kind regards

Danny Raj

View solution in original post

will_smith · ‎06-20-2016

Hi Matt, when you click on the update set to open it there should be a customer updates tab. Open the customer updates you want to switch and on the form you'll find a field called update set. From here you can change where you want the customer update to reside.

Let me know if you've got any other questions Matt

jack_greene · ‎07-06-2018

Sorry to bump an old post, but I have a question similar to the issues presented in this thread.

We have several admins working on various sections of our SNow environment. I can't find any documentation to confirm or deny, but it seems that there can only be one current update set per system. If this is true, then the implication is that our various admins cannot work simultaneously without extreme coordination to ensure the proper update set is selected.

Can anyone conform or deny the per system vs per user basis of the current update set?

How are others dealing with multiple admins needing to configure update sets independently?