Leaving an update set in Loaded state

[guiguille]

Hey guys,

I'm preparing our instance to upgrade to Helsinki patch 8, and going through the best practices document, I saw that a cloning is recommended before applying the upgrade. The thing is that we have some development pending UAT, so I can't impact production just yet. My question is, if I retrieve the update sets in production but don't commit them, will I get into trouble? I'm a little worried about the loop that would happen by having loaded update sets in all the environments (after leaving them in that state in production, it would appear in all my sub prod environments).

Do you have any recommendations? My options today are:

• Apply the patches without a previous cloning
• Retrieve the update sets to prod and not applying them
• Wait for UAT and impact everything in production (I know this would be by far the best option)

Thanks!

[Pradeep Sharma · Accepted solution]

Hello Guillermo,

The below thread should answer your question.

Re: System Clone

Patches Best Practices - ServiceNow Wiki

[srinivasthelu]

I am second to vote on your choice.

1.

• Apply the patches without a previous cloning - You mentioned it as BEST PTRACTICE document says otherwise. so NO!!!.
• Retrieve the update sets to prod and not applying them - This is may be ok, if you are sure you will get sign off for sure. There is chance that priorities can change and features deployments can be put on indefinite hold
• so, the LAST is the best.