| File name |
File name has different description for different related lists
- Skipped Changes to Review related list: Name of skipped Upgrade Detail
record
- Skipped Changes Reviewed related list: Name of the reviewed Upgrade Detail
record
- Copies to Review related list: Name of the record that needs to be reviewed
- Copies Reviewed related list: Name of the record that has been reviewed
- Customization Unchanged related list: Name of unchanged sys_upgrade_history_log
record. Select it if you want to access Upgrade Details and add comment text, or
set a resolution status for it
- Changes Applied related list: Current upgrade file name
- Claim Outcomes to Review related list: Name of skipped Upgrade Detail
record
- Upgrade Details related list: Current upgrade file name
|
| 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.
- Skipped Error: The system didn't have the upgrade on this file but skipped due to reasons like the record already exist in the system in a different scope or a system property exists.
Note: This is editable only
by a maint.
- 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.Note: ServiceNow prioritizes the skipped records based on the importance of the file types. The
prioritization is done as follows:
- Priority 1 (highest priority): UI pages, UI macros, and more
- Priority 2: Business Rules, Security ACLs, and more
- Priority 3: Reports and more
- Priority 4: Form Sections, Choice Sets, and more
- Priority 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).
|
| Reason |
States the reason why a particular record has been moved to the Skipped Error disposition. |
| 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. |
| Changed by vendor |
Indicates whether the file has been changed by the vendor since the last upgrade. |