---
sourceDocument: Australia ServiceNow AI Platform Administration
sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/platform-administration

 Release :

    - australia

ft:locale :

    - en-US

ft:publication_title :

    - Australia ServiceNow AI Platform Administration

ft:clusterId :

    - platadm

bundleId :

    - platadm

workflow :

    - Platform


---

# Upgrade History Task form

# Upgrade History Task form {#ariaid-title1}

Release version: Australia  
Updated March 12, 2026  
![](https://www.servicenow.com/docs/portal-asset/ico-clock) 2 minutes to read
Summarize  
![AI sparkle icon](https://servicenow.com/docs/portal-asset/ai-sparkle-icon) Summarized using AI  
This content was generated using new OpenAI-powered functionality. Results are provided on an as is basis and are not guaranteed to be accurate or complete.  

## 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 full answer 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.
To make changes on a skipped record task, click a task number link on a task over VTB.{#um-history-task-form__table_tht_fp2_clb__entry__2}

| 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: * 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 {#um-history-task-form__ul_gpz_q2j_bmb} |
| 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. * Not reviewed: Tasks which have not been reviewed * Reviewed: Tasks which have been reviewed * Merged: Tasks which have both the old and new changes * Retained: Tasks which have retained the updates from the latest upgrade * Reverted: Tasks which have reverted its changes to the base system {#um-history-task-form__ul_ohx_f4f_flb} |
| 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 |
[Table 1. Upgrade History task form details]

{#um-history-task-form__table_tht_fp2_clb}  
The Old Resolution Details related list shows the actions taken in the previous upgrade version. {#um-history-task-form__table_shg_xqf_flb__entry__2}

| 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: 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 {#um-history-task-form__ol_bjl_cwf_flb} |
| State | State of the files. * Not reviewed: Tasks which have not been reviewed * Reviewed: Tasks which have been reviewed * Reviewed and Merged: Tasks which have been reviewed and have both the old and new changes * Reviewed and Retained: Tasks which have been reviewed and have retained the updates from the latest upgrade * Reviewed and Reverted: Tasks which have been reviewed and have reverted its changes to the base system {#um-history-task-form__ul_uhg_xqf_flb} |
| Assigned to | Name of the assigned user |
| From | Past previous version |
| To | Past current version |
[Table 2. Old Resolution Details related list]

{#um-history-task-form__table_shg_xqf_flb}