Upgrade to the Washington DC release

Washington DC Release Notes

Release

washingtondc

ft:locale

en-US

ft:publication_title

Washington DC Release Notes

ft:clusterId

bundleId

Upgrade to the Washington DC release

Release version: Washingtondc

Updated February 1, 2024

2 minutes to read

Summarize

Summarized using AI

Summary of Upgrade to the Washington DC release

Upgrading to the Washington DC release involves careful planning, testing, and validation to ensure a smooth transition. It is essential to follow the structured phases outlined for a successful upgrade process.

Show full answer Show less

Key Features

Phase 1: Read the release notes and plan your upgrade to understand necessary tasks.
Phase 2: Prepare for the development instance upgrade by cloning your production instance for testing.
Phase 3: Verify upgrade configurations and schedule the upgrade in Now Support.
Phase 4: Upgrade and validate your development instance using the Upgrade Monitor and conduct functional testing.
Phase 5: Upgrade additional non-production instances and apply necessary post-upgrade changes.
Phase 6: Prepare to upgrade your production instance after refining your test environment.
Phase 7: Upgrade your production instance last, validate completion, and conduct user acceptance testing.

Key Outcomes

Following this upgrade process ensures that your ServiceNow environment is updated safely and effectively, minimizing disruptions to your production instance while allowing for thorough testing and validation of new features and functionalities. By adhering to the outlined phases, you can expect a streamlined upgrade experience and improved system performance post-upgrade.

Upgrading and patching your instance requires planning, testing, and validation. To ensure a safe and effective upgrade, read the release notes, create upgrade plans, and test your upgrade on non-production instances before upgrading your production instance.

Important:

These topics contain in-depth explanations about upgrades. For a step-by-step reference of upgrade steps, refer to the Upgrade planning checklist.


	Phase 1 - Read the release notes and plan your upgrade Before you begin the upgrade process, it is essential to read the release notes for your target version so you understand the required upgrade and migration tasks. This information helps you plan a safe and effective upgrade.
	Phase 2 - Prepare for the development instance upgrade For a better understanding of your production upgrade duration, request a full clone of your production instance (including large tables and attachments) onto a non-production instance. Confirm your current and target release versions, because you will later use this information when scheduling your upgrade in Now Support.
	Phase 3 - Verify your upgrade configurations and schedule the development instance upgrade in Now Support Check the configuration of the Check distribution for possible upgrade scheduled job to view how often and when it runs. Review information about timing your upgrade in coordination with the Check distribution for possible upgrade scheduled job. Then, schedule your upgrade in Now Support.
	Phase 4 - Upgrade and validate the development instance Track the progress of your upgrades with the Upgrade Monitor. For your first non-production instance upgrade (your development instance), use the Upgrade Monitor to process the skipped list of records that were not addressed in the upgrade. Then identify your update sets and perform functional testing.
	Phase 5 - If applicable: Upgrade and validate your other non-production instances, such as your test instance After you've configured and refined your development instance, request to upgrade any other non-production instances you have, such as a test instance. Immediately after the upgrade is complete, apply the post-upgrade changes made to your development instance, including activating optional plugins, installing and upgrading applications, and applying update sets.
	Phase 6 - Prepare to upgrade the production instance After you have configured and refined your test environment to be a good representation of your production environment, prepare to upgrade your production instance.
	Phase 7 - Upgrade the production instance After you have upgraded your development, non-production, and test instances, upgrade your production instance last. Then validate that the upgrade was complete, apply update sets and fix scripts, and perform post-upgrade user acceptance testing (UAT).