Upgrade Details related list

  • Release version: Washingtondc
  • Updated February 1, 2024
  • 2 minutes to read
    • Summarize
    Summarized using AI
    This content was generated using new OpenAI-powered functionality. Results are provided on an as is basis and are not guaranteed to be accurate or complete.

    Summary of Upgrade Details related list

    The Upgrade Details related list provides a comprehensive overview of all records associated with the current upgrade for ServiceNow users. It enables administrators to track the outcomes of various upgrade actions and manage the resolution of any issues that arise during the upgrade process.

    Show full answer Show less

    Key Features

    • Disposition: Indicates the action taken on each record during the upgrade, such as inserted, updated, deleted, or skipped. Understanding this helps in assessing the impact of the upgrade on customizations.
    • Priority: Reflects the importance of conflicts that may have led to skipped updates, ranked from highest (xml content) to lowest (other).
    • Claim Status: Provides insights into any conflicts with loaded files, with outcomes like N/A, Won conflict, No conflict, or Lost conflict, aiding in conflict resolution.
    • Resolution Options: Administrators can add comments during the resolution process for clarity and future reference.
    • File Information: Displays details such as the target name, plugin, file type, and whether the file has been altered by the vendor, which is crucial for tracking changes.

    Key Outcomes

    By utilizing the Upgrade Details related list, ServiceNow customers can effectively monitor and manage upgrade processes, resolve conflicts, and maintain system integrity. This functionality is essential for ensuring that upgrades do not adversely affect existing customizations and that any issues are promptly addressed.

    Upgrade Details lists all Upgrade Details records for this upgrade.

    Navigate to System Diagnostics > Upgrade History to view the Upgrade Details related list.

    Table 1. Upgrade Details related list
    Field Input Value
    Disposition Action performed on this file during the selected upgrade:
    • Inserted: The system inserted a new record.
    • Updated: The system updated this record.
    • Deleted: The system deleted this record.
    • Skipped: The system did not change this record in order to preserve customizations.
    • Reverted: This record was reverted to the base version.
    • Table not found: The system could not find the table that contains this record.
    • Unchanged: The system did not change this record because the baseline component has not changed since the last release.
    • Skipped Manual Merge: The system did not change this record because updating it requires manual intervention.
    • Skipped Apply Once: The system skipped this record because it had already applied an update from an xml file in the apply once folder.
    • Not Latest: The system applied a change, but this change was overwritten later during the same upgrade.
    Priority Relative importance of the conflict that caused the skip based on the following criteria:
    • 1 (highest priority): xml content
    • 2: script or script_plain
    • 3: html content
    • 4: sys_ui_form_section, sys_ui_related_list, or sys_choice_set
    • 5 (lowest priority): other
    Claim Status Outcomes:
    • N/A: There are no claims on the record (no need to review)
    • Won conflict: The loading application loaded the file but is in conflict with the previously loaded file. Recommendation: Review the two versions of the file to confirm your intended outcome.
    • No conflict: There may be one or more applications loading but there is no conflict. However, it is still good to review the outcome to see if it's what you intended.
    • Lost conflict: The file was not loaded because another application has a better claim on the file. Recommendation: Review the two versions of the file to see which should be loaded (or if they should be merged).
    Resolution
    • Reviewed
    • Retained
    • Reverted
    Comment During the process of resolving a skipped update, you have the option to add a Comment to any record. For example, the comment might explain the action that you took to future reviewers.
    Target name Name of the record corresponding to the current file.
    Plugin Plugin that contains the record.
    Type Current file type (such as Business Rule or UI Policy).
    Table Table that contains the record.
    File name Current upgrade file name.
    Changed by vendor Indicates whether the file has been changed by the vendor since the last upgrade.