- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago
I have modified the built-in business role 'getMyApprovers' in the system, which is recorded in the update set, but the previous version has not been modified. Now facing a system upgrade, in order to restore the content I modified to the previous version. How to operate without affecting the upgrade effect.
The update version in the screenshot above does not include the original version. How should we restore this business role to its original version.
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago - last edited 3 weeks ago
Hello again @shiz !
If the XML you import is truly identical to the vendor’s base version for your current release, the upgrade behavior is typically clean. However, if ServiceNow modifies that same rule in the new release, you may be prompted to review or merge the change because the platform sees that record as having been touched locally.
Also, the suggestion about “Replace on upgrade” is valid and a very good idea: Setting Replace on upgrade = true for that customized Business rule causes the platform to overwrite your local/customized version with the ServiceNow-delivered version during the next upgrade or patch, so it’s a good option if your intent is “always take the vendor version going forward” (just be aware it will discard any local changes to that item).
You can read more about this approach in the official ServiceNow docs here: https://www.servicenow.com/docs/r/application-development/system-update-sets/t_OverwriteCustomizsDur...
Please consider marking my answer as helpful and accepting it as the solution if it assisted you in any way.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago
You screenshot looks good. After any patch upgrade. it will be reverted to OOB
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago
I think both suggestions are correct and it really depends on what the developer wants. If the goal is to revert to OOTB and proceed this way for some time then, when the upgrade comes, the system will mark it as a skipped record to be reviewed (fairly easy to review and till then the system will work with the ootb BR so its a win-win). If you are right before the upgrade and do not care about the current state of the BR but you only care about what will happen after the upgrade, then you proceed with the other approach and mark the business rule by setting the field Replace on Upgrade to true.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago
When I change the value of the 'replace_on_upgrade' field to true, the system prompts a message.
Will the content of the BR I modified be overwritten during the next system update?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago
Mark the "Replace on Upgrade" flag on the business rule. This ensures the rule is replaced during upgrades or any patch releases.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago
'Replace on Upgrade' How to operate it specifically? If there were any examples, that would be really great
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago
You screenshot looks good. After any patch upgrade. it will be reverted to OOB
