Skipped Changes to Review related list

  • Release version: Xanadu
  • Updated August 1, 2024
  • 2 minutes to read

    • To prevent your customizations from being overwritten during system upgrades, the upgrade process skips (does not apply the update to) objects that have been customized. To assist you in tracking and resolving skipped update records that need review, Skipped Changes to Review lists all updates skipped during the upgrade process.

    By default, the list is filtered by Disposition Skipped Error, Disposition Skipped Manual Merge, Disposition Skipped, or Disposition Skipped (second pass), and the resolution status is either empty or not reviewed.

    Navigate to System Diagnostics > Upgrade History to view the Skipped Changes to Review related list.

    Table 1. Skipped Changes to Review related list
    Field Input Value
    File name Name of skipped Upgrade Detail record.
    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.
    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).
    Priority Relative importance of the conflict that caused the skip based on the following criteria:
    • 1: UI pages, UI macros, and more
    • 2: Business rules, security ACLs, and more
    • 3: Reports and more
    • 4: Form sections, choice sets, and more
    • 5 Everything else
    Resolution
    • Not reviewed: Records which have not been reviewed
    • Reviewed: Records which have been reviewed
    • Reviewed and Merged: Records which have been reviewed and have both the old and new changes
    • Reviewed and Retained: Records which have been reviewed and have retained the updates from the latest upgrade
    • Reviewed and Reverted: Records which have been reviewed and have reverted changes to the base system
    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.