Skipped records after Patch Update

[pauladams]

Hello,

We have recently updated our development instance with patch Istanbul patch 10 C. I've looked at the upgrade monitor and have few questions for you experts:

1) After the upgrade, we have been testing the functionality we had before the patch and everything is working as expected. Do I still need to review the skipped updates and take action on them?

2) What does the priority of the skipped record indicate? Majority of the skipped records are Priority 5, few are 2, and a very few are 3 and 4. Does priority 5 mean take it easy and just ignore?

3) Do we need to repeat this exercise of reviewing the skipped records in all the environments as our Dev, UAT, Staging and Production instances are identical and it is likely to skip the same records in all the environments or can I capture the reviews in an update set and promote to the other instances?

4) If the reviews can be captured in an update set and can be moved to other environments, do I need to move the update set prior to the upgrade of the target instance?

5) Finally, what happens if I just leave them without reviewing?

Thanks

Pa

[Patrick DeCarl1]

Hello, 

I'll do my best to answer all your questions. But first, have you visted https://docs.servicenow.com/bundle/jakarta-platform-administration/page/administer/platform-upgrades/task/upgrademon-process-skip-list.html ?

1) After the upgrade, we have been testing the functionality we had before the patch and everything is working as expected. Do I still need to review the skipped updates and take action on them?

PD: Yes. ServiceNow does not update items you config that are deam OOTB. SO if you are looking for fixes or new features you might had mod you will not get those changes. However, when you look at the skipped record you can compare and choose to revert back to OOTB or merge the two codes by line. 

2) What does the priority of the skipped record indicate? Majority of the skipped records are Priority 5, few are 2, and a very few are 3 and 4. Does priority 5 mean take it easy and just ignore?

PD:  The priority the system has assigned to resolving this conflict. Values range from one to five, with one representing the highest priority.   Rule I tend to follow is, to review all P 1-3s and fix them if needed. P4 and 5 are usually form changes and related lists updates and etc. 

3) Do we need to repeat this exercise of reviewing the skipped records in all the environments as our Dev, UAT, Staging and Production instances are identical and it is likely to skip the same records in all the environments or can I capture the reviews in an update set and promote to the other instances?

PD:If you clone prod down to all sub instances before upgrade then your instances should be inline for the most part. So if you take care of the skips in dev and capture them in update set vs the ones you just roll back to OOTB then you will just need to revert the changes to OOTB and move your update sets. 

4) If the reviews can be captured in an update set and can be moved to other environments, do I need to move the update set prior to the upgrade of the target instance?

PD: After you clone PROD to Dev, run upgrade, review skips and make whatever changes you need to do, if those changes get captured in update set, then you move them after the upgrade is complete. 

5) Finally, what happens if I just leave them without reviewing?

PD: Two things, Nothing or new features don't work b/c it depends on a code you might changed. 

[pauladams]

Thank you Patrick. Very helpful.

One more question:

If I capture the reviews in an update set while reviewing them in Dev and move that update set to UAT/production and when I upgrade the UAT, will the upgrade monitor not show those records as Skipped?

[Patrick DeCarl1]

Only if your rolling them back to OOTB. But again its a hit or miss if reverting back to OOTB gets capture in an update set.