Upgrade History Task form
Summarize
Summary of Upgrade History Task form
The Upgrade History Task form enables users to update information regarding skipped record tasks within ServiceNow. Customers can access this form by clicking on a task number link from a task over the VTB (Visual Task Board). This functionality is essential for managing upgrade tasks efficiently, ensuring that important records are prioritized and reviewed appropriately.
Show less
Key Features
- Task Information: Each task includes fields such as Short Description, Priority, Disposition, Type, State, and Work Notes to provide comprehensive details about the skipped record.
- Priority Levels: Tasks are prioritized from Priority 1 (highest) for critical components like UI pages, to Priority 5 (lowest) for less critical elements.
- State Tracking: The state of tasks is tracked with options including Not Reviewed, Reviewed, Merged, Retained, and Reverted, allowing users to see the status of each record.
- Action Buttons: Users can Update, Resolve Conflicts, Revert to Base System, or Delete tasks directly from the form.
- Old Resolution Details: A related list provides information on actions taken during previous upgrades, maintaining a history of changes for reference.
Key Outcomes
By utilizing the Upgrade History Task form, ServiceNow customers can efficiently manage and prioritize their upgrade tasks, ensuring that important customizations are preserved and conflicts are resolved. This leads to a smoother upgrade process and helps maintain system integrity while facilitating timely updates to critical components.
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 |