Upgrade History Task form
Summarize
Summary of Upgrade History Task form
The Upgrade History Task form in ServiceNow enables you to update information about skipped record tasks during an upgrade. It is specifically designed to manage and modify tasks that were skipped to preserve customizations. You access the form by clicking a task number link on a task over the VTB (Version Task Board).
Show less
Key Features
- Task Details: Includes fields such as short description, priority, disposition, type, state, and work notes, which help you understand and manage skipped record tasks effectively.
- Priority Levels: Tasks are prioritized based on file type importance, ranging from Priority 1 (highest, e.g., UI pages and macros) to Priority 5 (lowest, e.g., other types).
- State Tracking: Tracks the review and merge status of tasks, including states like Not reviewed, Reviewed, Merged, Retained, and Reverted.
- Action Buttons:
- Update: Apply changes to a skipped record task.
- Resolve Conflicts: Review and resolve differences in the task.
- Revert to Base System: Revert customizations to the base system version.
- Delete: Remove the skipped record task.
- Old Resolution Details Related List: Displays historical actions taken on the skipped files in previous upgrade versions, including disposition, priority, state, assigned user, and version details.
Practical Use for ServiceNow Customers
This form helps you maintain control over upgrade processes by managing skipped records that contain customizations. By prioritizing tasks and tracking their review state, you can systematically address upgrade conflicts and ensure critical customizations are preserved or appropriately reverted. The ability to resolve conflicts and revert changes directly from the form streamlines upgrade management and reduces potential downtime or errors.
You can update information about a skipped record task using the Upgrade History Task form.
| Field | Description |
|---|---|
| Short description | Description about the task |
| Priority | Prioritization of the skipped records based on the importance of the file types. The prioritization is done as follows:
|
| Disposition | Disposition is Skipped since the task board is only for skipped records. The system did not change this record in order to preserve customizations. |
| Type | Type of file which determines the priority level. |
| State | State of the files.
|
| Work notes | Notes about the skipped record task |
| Update | Button to update the skipped record task |
| Resolve Conflicts | Button to resolve conflicts by reviewing the differences |
| Revert to Base System | Button to revert the customizations |
| Delete | Button to delete the skipped record task |
| Field | Description |
|---|---|
| Number | Task number of the skipped file where some actions were taken in the previous upgrade version. |
| Short description | Description about the task |
| Disposition | Action performed on this file during previous upgrade |
| Priority | Prioritization of the skipped records based on the importance of the file types. The prioritization is done as follows:
|
| State | State of the files.
|
| Assigned to | Name of the assigned user |
| From | Past previous version |
| To | Past current version |