Upgrade Summary Report
Summarize
Summary of Upgrade Summary Report
The Upgrade Summary Report provides a comprehensive overview of actions taken during an upgrade, tools for resolving conflicts between customizations and new changes, and estimates for future upgrades across instances.
Show less
Key Features
- Upgrade Details: Displays the upgraded version, duration of the upgrade, and links to view new features, problem fixes, personalized release notes, and known errors.
- Skipped Records: Highlights total record changes and lists skipped records to protect customizations. Administrators can review and resolve skipped updates, choosing to retain or revert customizations.
- Node Upgrades: Shows the upgrade status for each node with an icon color indicating status. Hovering over an icon provides detailed information.
- Application Upgrade Status: Lists installed and upgraded applications, including any that failed to install, with the option to view detailed application information.
- Schema Changes to Clone-excluded Tables: Identifies tables affected by upgrades that were excluded during cloning, highlighting the efficiency of the upgrade process.
- Top 10 Metrics: Provides insights into the duration of the top 10 fix scripts, schema changes, and plugins, allowing users to understand time-intensive components of the upgrade.
Key Outcomes
By utilizing the Upgrade Summary Report, ServiceNow customers can effectively manage upgrades, understand the impact of customizations, and optimize the upgrade process based on detailed metrics and insights. This enables smoother upgrades, better resource allocation, and informed decision-making moving forward.
The Upgrade Summary report summarizes the actions taken, provides tools to resolve conflicts between customizations and changes that are part of the upgrade, and provides information to help estimate time for upgrades to other instances.
| Field | Input Value |
|---|---|
| Upgraded version | Version to which the instance has been upgraded |
| Upgrade duration | Total time taken to make the upgrade |
| Find out what's new and changed | Links to view the new and changed features in the current upgrade version.
The following three links show up.
|
Skipped Records
| Field | Input Value |
|---|---|
| Total record changes | Total number of records that have changed since the previous upgrade
version. Review changes: List of records that have changed can be reviewed. See System Upgrade form for more details. |
| Skipped records | Skipped records to prevent your customizations from being overwritten. If
customizations are found in some records during the upgrade, those records are
skipped. As an admin, you can resolve each update that was skipped due to a
customization. To resolve a skipped update, you can review the reason for each
skipped record and then either retain the customization or revert the
customization to the base system. If you choose to revert some of the
customizations to the base version, those records are sent through the upgrade
without getting skipped.
|
| Skipped records by priority | ServiceNow prioritizes the skipped records based on the importance of the
file types. The prioritization is done as follows:
|
| Skipped records by product | Skipped records are sorted by product names |
| Skipped records code changed/code unchanged | Skipped records are sorted depending on if there are changes in the code or not. |
Node Upgrades
The Node Upgrades section shows the status of the upgrade for each node in the instance. The color of the icon denotes the status, as illustrated by the legend (key) and to the right of the node icons. To see details about a node, position the cursor above the icon for that node. An arrow points to the node selected, and the information below the icons pertains to that node.
Application Upgrade Status
The following message shows up if you have selected any of the failed applications link.
Schema Changes to Clone-excluded Tables
The Schema Changes to Clone-excluded Tables section shows a list of tables affected by the upgrade that were clone-excluded when you cloned the production instance to this instance. Because clone-excluded tables are empty, upgrading them takes less time than upgrading those same tables on the production instance. To estimate how much longer the production upgrade takes, note the size of the clone-excluded tables on the production instance.
Top 10 Fix Scripts by Duration
The Top 10 Fix Scripts by Duration helps you understand which fix scripts required the most time.
Top 10 Schema Changes by Duration
The Top 10 Schema Changes by Duration helps you understand which schema changes required the most time.
Top 10 Plugins by Duration
The Top 10 Plugins by Duration helps you see the plugins that required the most time. Click View all plugin duration to see the System Upgrade Metrics list filtered by current sys upgrade history log and sorted by duration. See View loaded files for a plugin for more information.