- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎06-28-2021 09:43 AM
Hello,
I am only aware of upgrading my PDI in ServiceNow. I was curious to know what happens to the already committed UpdateSets(Configurations) when we upgrade the Development/TEST/Production instances. When the Upgrade is successful, will all the configurations be carried forward with no steps to follow regards to update sets or will it be a clean slate?
The product documentation on Upgrade to Quebec in ServiceNow is very detailed. Going through that. I would also like to hear any good pointers and things to watch out from own experiences during instance upgrade.
Thanks,
Swathi
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎06-28-2021 10:33 PM
Hi Swathi,
To make sure you can test the upgrade as good as possible, it's recommended to clone PROD over DEV/TEST before upgrading. Any committed update sets on PROD will be cloned over DEV/TEST (make sure you pick the correct backup to clone from, because if you commit an update set at 1PM and you clone a backup made at 8AM, you will loose that update set).
When cloning you can choose to safe 'in progress' update sets. Those will be put back after the clone, but also a warning here: this only works on 'global' update sets. Any others will be overwritten. Because of this I make it a point to always safe them all manually, to be sure I have everything.
After cloning you can upgrade and go through the skipped changes (the Upgrade Center is a real help here). If everything's OK you upgrade PROD, move the update set you created for the skipped changes and 9 out of 10 times you don't have to do anything, because the update set clears the skipped changes on PROD (but check them to be sure).
Since the upgrade is done, the freeze on NON-PROD is over and you can reapply the saved update sets. Import and commit them and you can continue development. Never reopen those update sets though! Either create a new one and merge it with the committed one, or created a 'b-version' of the update set and move them together (or as batch) when development is done.
I hope this helps!
Mark
Please mark any helpful or correct solutions as such. That helps others find their solutions.
Mark
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎06-29-2021 12:33 PM
Thank you all for the helpful quick responses. This definitely helps!