How can I revert customized OOTB script to Store version if this script was committed via update set on all instances

[Alex150]

Hello,

ServiceNow recommended set "Replace on upgrade" to true on Custom Updates table if OOTB script was changed It's a good way if it was done before an upgrade, but what should we do if an instance has already upgraded? I wonder if there is a different way to do it? 

What do you think? What is the best practices? 

[Mark Manders]

Hi Alex,

You can add the 'versions' related list to the script. There you can see all changes done to the script. Select the OOB version, open it and select the UI action 'revert to this version'. Your script will be back to OOB.

Best way is to follow the same route: start on your DEV and move it (via update set) to PROD. All your instances will have the same version again.

Kind regards,

Mark

[Alex150]

Hi, thank you for response.

If I revert a script on specific instance and save changes to some Update set and then commit it to another instance, the latest version of this script on remote instance would be with my Update set name, but not ServiceNow store. And in this case I'm not sure if on the second instance this script will be updated with OOTB changes. Store application version will have "History" state, and committed Update set will be current. 

[Mark Manders]

If you have reverted the script back to OOB (which in case of patch/upgrade can be done through skipped changes, using the 'revert' button), it doesn't matter in which update set it has been done. It's not the update set that is being checked for versioning, but the script itself. If that is OOB, it won't be skipped anymore. Once reverted, ServiceNow will be upgrading the script when it's in a patch/upgrade.

[Alex150]

Thank you!