Upgrade History Task form

  • Release version: Washingtondc
  • Updated February 1, 2024
  • 2 minutes to read
    • Summarize
    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 allows users to update information about skipped record tasks during system upgrades. Users can access this form by clicking on a task number link from the task board.

    Show full answer Show less

    Key Features

    • Field Descriptions:
      • Priority: Indicates the importance of file types, ranked from Priority 1 (highest) to Priority 5 (lowest).
      • Disposition: Fixed as "Skipped" to maintain customizations.
      • Type: Defines the file type influencing priority.
      • State: Shows the review status of the tasks (Not reviewed, Reviewed, Merged, Retained, Reverted).
      • Work Notes: Contains notes about the skipped record task.
      • Action Buttons: Options to update, resolve conflicts, revert customizations, or delete tasks.
    • Old Resolution Details: Displays actions taken in previous upgrade versions, including task numbers, descriptions, dispositions, priorities, and states.

    Key Outcomes

    By utilizing the Upgrade History Task form, ServiceNow customers can effectively manage and update skipped record tasks, ensuring that necessary changes are made while preserving custom configurations. This functionality aids in maintaining system integrity during upgrades and enhances overall operational efficiency.

    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.
    Table 1. Upgrade History task form details
    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
    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
    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
    The Old Resolution Details related list shows the actions taken in the previous upgrade version.Image showing the Old Resolution Details related list
    Table 2. Old Resolution Details related list
    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
    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
    Assigned to Name of the assigned user
    From Past previous version
    To Past current version