Managing upgrade risk
You will be notified of the possible conflicts that might result due to several customizations on a skipped metadata file, with a new UI message on the form pages of the metadata files.
One of the major conflict areas during an upgrade is resolving conflicts for skipped metadata files that are released by ServiceNow® but have been customized. These conflicts result due to multiple users updating the same files. ServiceNow might update the code in the files which you have customized over time. Whenever you install an
application or a plugin, you tend to make several customizations as per your requirements. During the next upgrade, you might have several skipped records depending on the previous customizations.
Important:
Avoid making modification on the high risk and medium risk (if possible) skipped metadata files that can potentially cause conflicted skipped metadata files in your next upgrade. You can edit the files if the
modifications are absolutely required.
The goal of the UI message is to make you aware of the friction that will be introduced during the upgrade process, if any high priority files have been modified. The notification is of the form of UI messages on the form pages of the
metadata files.