How to handle "skipped records" as part of ServiceNow Upgrade?

[Suggy]

We have 3 instances. DEV, TEST and PROD.

Lets say I have cloned PROD over DEV, then upgraded DEV instance, reviewed all the skipped records (assume I have 100 skipped records) in DEV and have captured required changes in Update set.

Now when upgrade TEST instance, I dont want to review all those 100 skipped records as I have already reviewed in DEV instance.

How should I handle this? If I move my update set to TEST after upgrading TEST instance, will there be any changes to my skipped records? or what exactly will happen to my skipped records after I move my update sets?

[Community Alums]

Hi @Suggy ,

When you manage skipped updates i.e review and merge, revert to base, etc the changes are saved in the update set you are currently working in. If you are not currently working in an update set then the changes are saved to the Default update set.

Hence, as per your requirement, the update set where you have captured the required changes , please move it to TEST after upgrading the TEST instance.

Mark my answer correct & Helpful, if Applicable.

Thanks,

Sandeep

[Suggy]

Hi @Sandeep Dutta Ok, once I upgrade my TEST instance, I will see those 100 records as skipped records.

Next I will move my update set to TEST. What will happen to those 100 skipped records?

[Craig Gruwell · Accepted solution]

Hi Suggy,

After you commit the update set in TEST, when you navigate to the Upgrade History you should expect to see the 100 skipped records appear on the "Skipped Changes Reviewed" related list (as if you performed the same remediation steps in TEST that you did in DEV).

[Suggy]

Thank you for that clarification @cgruw  🙂