Skipped Changes Reviewed related list

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

    • Skipped Changes Reviewed lists update records that previously appeared on the Skipped Changes to Review related list and have been reviewed. When you select a skipped record to review and set a Resolution Status to a value other than Not Reviewed, the update record moves to the Skipped Changes Reviewed related list.

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

    Table 1. Skipped Changes Reviewed related list
    Field Input Value
    File name Name of reviewed Upgrade Details 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 (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
    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
    File differences Comparison of the file in the upgrade with the customized version.
    Changed by vendor Indicates whether the file has been changed by the vendor since the last upgrade.