Pre- and post-upgrade tasks for various products

Watch

Save as PDF

Share this page

Feedback

Vancouver release notes

HomeVancouver Release NotesVancouver release notesPrepare your upgradePre- and post-upgrade tasks for various products

Table of Contents

Pre- and post-upgrade tasks for various products

Release version:
Vancouver
Yokohama
Xanadu
Washington DC
UpdatedApr 30, 2025
39 minutes to read

Vancouver
Release Notes and Upgrades

The Vancouver release is no longer supported. As such, the product documentation and release notes are provided for informational purposes only, and will not be updated.

In preparation for your upgrade, review the upgrade and migration tasks for various applications and features. Plan to complete these tasks, when applicable, before or after the upgrade is complete.

Prepare your instance for a smoother upgrade

Pre-upgrade tasks, upgrade, post-upgrade tasks

Before you upgrade to Vancouver, review these pre- and post-upgrade tasks and complete the tasks as needed.

Upgrade and migration tasks

Important: For any changes in the upgrade procedure for self-hosted customers, see KB0563844 for details.

Search:

Product Release notes Family

AI Search

When you upgrade to Vancouver from an earlier release, AI Search automatically reindexes non-Task tables to allow for display of attachment search results with their parent record, but doesn't automatically reindex the Task [task] table and its child tables. Before you can display Task record attachment search results with their parent records, you must manually reindex the Task [task] table. For details on reindexing a table, see Perform a full table index or reindex for a single indexed source.
Note: Reindexing the Task table can take some time.
After you upgrade to Vancouver from an earlier release, you can optionally republish your search profiles that contain result improvement rules with block and promote actions. Republishing these search profiles resolves an issue where result improvement rules could fail to block or promote translated search results correctly. For instructions on republishing a search profile, see Publish a search profile. To learn more about how AI Search handles translated content, see Internationalization support for AI Search.

Vancouver

Assessments and Surveys

Update the Automated Test Framework (ATF) tests, if you're upgrading to Vancouver from any version prior to Utah. In the Utah release, all the buttons on the assessments or surveys cards have been removed. To run ATF tests successfully, the Click the Take Survey button step must be replaced with the Click the Survey card step for all tests that have this step.

Vancouver

Automated Test Framework

Copy and customize quick start tests provided by the Now Platform® to validate that your instance works after you make any configuration changes. For example, if you apply an upgrade or develop an application.

The tests can produce a pass result only when you run them on a base system without any customizations and with the default demo data that is provided with the application or feature plugin. To apply a quick start test to your instance-specific data, copy the quick start test and add your custom data. For more information, see Available quick start tests by application or feature.

Vancouver

Cloud Cost Management

For instructions on upgrading Cloud Cost Management to Vancouver, see Upgrade Cloud Insights.

Vancouver

Configuration Management Database (CMDB)

During upgrade, a fix script that re-parents the Reconciliation Definition Mapping [cmdb_reconciliation_definition_mapping] table, runs. The length of time that it takes this fix script to complete depends on the number of reconciliation rules in the upgraded instance and will typically add several minutes to the upgrade.

Re-parenting the Reconciliation Definition Mapping [cmdb_reconciliation_definition_mapping] table is necessary to ensure that data in that table is captured by update sets when exporting reconciliation rules between instances. After upgrading, any changes to reconciliation rules are fully captured by update sets and are properly ported to destination instances.

Vancouver

Customer Service Management (CSM)

Following an upgrade to the Vancouver release, you may need to retrain and redeploy Task Intelligence for Customer Service categorization and sentiment models. For more information, see Steps to complete after upgrading to Vancouver in the Task Intelligence for Customer Service documentation.

Vancouver

Document Intelligence

Document Intelligence 3.0 and later includes an updated schema to support its transition from a scoped application to a Now Platform plugin. For upgrade details, see Upgrade to Document Intelligence 3.0 or later from version 2.4 or earlier.

Vancouver

Goal Framework

Starting with v4.2.0, the existing targets with the Type field set to Milestone are considered as qualitative targets. After upgrading Goal Framework, for such existing targets, the unit of measure is set to Yes/No, the Base value is set to No, and the Target value is set to Yes automatically. Also, the Actual value is set to Yes if the progress value is 100%, otherwise the value is set to No.

Vancouver

ITOM Visibility

Microsoft Azure Alert configuration: After upgrading, configure the Microsoft Azure alert service to forward alert notifications to the Now Platform in a secure way. For more information, see Use a secure webhook to forward the Microsoft Azure alerts to the Now Platform.

Vancouver

Identity and Authentication

Authentication report_view access control lists (ACLs) that govern who can see reports in dashboards and elsewhere are enabled by default in the Vancouver release. For more information, see Report_view access control.

Vancouver

Industrial Process Manager

If you use the ISA Service Graph Connector that's packaged with the Manufacturing Process Manager and are upgrading to the Industrial Process Manager, ensure that any new ISA equipment model entities have a unique name field.

Vancouver

Instance Data Replication

Improve the performance and processing efficiency of Instance Data Replication (IDR) by upgrading your replication sets to V2, which uses the Hermes Messaging Service. For details, see Upgrading legacy replication sets to V2 in Instance Data Replication.

If the Replication Payload Error [idr_replication_payload_error] table on your instance has more than 10 million records, set up table rotation according to KB1364728. Using table rotation to delete records from the Replication Payload Error [idr_replication_payload_error] table is safe because that table only contains replication errors logged by IDR and not any replicated data.

Vancouver

MID Server

For the latest MID Server system requirements, see MID Server system requirements. The minimum JRE version supported is 11.0.9 and the recommended version is 11.0.16.1.

If you have installed your own JRE, the upgrade process takes the following actions to ensure that the MID Server uses a supported JRE:

If a MID Server is using an unsupported version of the JRE when it upgrades, the upgrade process displays a warning message with the minimum and recommended JRE version.
If a supported JRE is running on the MID Server host, the upgraded MID Server uses that version.

All MID Server host machines require access to the download site at install.service-now.com to enable auto-upgrades. For additional details, read how the system manages MID Server upgrades.

Only one Windows MID Server service is permitted per executable path. Upgraded Windows MID Servers that have multiple services pointing to the same installation folder cannot start. See MID Server fails to start for more information.

For more information about MID Server upgrades, see the following topics:

MID Server pre-upgrade check: Describes how the AutoUpgrade monitor tests the ability of the MID Server ability to upgrade on your system before the actual upgrade.
Upgrade the MID Server manually: Describes how to upgrade your MID Servers manually.

Vancouver

Now Assist

For more information about troubleshooting your Now Assist application and plugin upgrades, see the KB article for issues and mitigation for Now Assist upgrades.

Vancouver

Order Management

Starting with the November 2023 release, the Order Management application supports the complete life cycle of product and service orders, including the order fulfillment features provided with the Order Management for Telecommunications, Media, and Technology application. If you have a Telecommunications Service Management subscription, you install the Order Management for Telecom, Media and Tech application from the ServiceNow Store. This application installs the Order Management application, telecommunications demo data, and the following ServiceNow Open API implementations of TM Forum API REST specifications:

Product Catalog Open API
Service Catalog Open API
Product Order Open API
Service Order Open API
Product Inventory Open API
Technical Service Qualification Open API

If you're familiar with the Order Management for Customer Service Management application, you can optionally use that interface after installing the Order Management application. For more information, see Enable the user interface for Order Management for Customer Service Management KB1554296. For information on changes to the interface, see Changes to the Order Management for Customer Service Management application KB1560237.

During upgrade, the Order Task [sn_ind_tmt_orm_order_task] table is extended from the Planned Tasks [planned_tasks] table that is used in the Customer Service Management application. The Order Task table has also been modified. For details on changes to the Order Task table, see OMT Reparenting data model changes KB1496935.

If you upgraded to the Vancouver release and are using a version of the Order Management for Telecommunications, Media, and Technology application that is not version 5.2.0, the fixes for populating product inventory and product model characteristics aren’t available to you. To get those changes, upgrade to the current Vancouver patch.

Vancouver

Platform Analytics Workspace

The Vancouver version of Platform Analytics Workspace (3.0) includes the updates in versions 2.1.x, previously available only in the ServiceNow® Store.

Vancouver

Portfolio Planning

If you’re upgrading from an older version to Portfolio Planning v6.1.1 or higher, a fix script is run to remove the milestone_editor role from the roadmap_editor role because the roadmap_editor role is no longer used. In this case, you may experience a longer time for the upgrade to complete if your ServiceNow instance has a large number of users with the roadmap_editor role. For more information, see KB1443618.
If you’re upgrading from an older version to Portfolio Planning 7.0.0 or 7.1.0, the entities list may not load in the select entities step while you create or edit a portfolio plan. In this case, you must add the script in the List component for the Select entities page. For more information, see KB1566418.

Vancouver

Process Automation Designer

After you upgrade to Vancouver, update the Process Automation Designer application in the ServiceNow Store.

Vancouver

Public Sector Digital Services

Before you upgrade to Public Sector Digital Services v8.0, you must create custom service definitions for data in the Services Offered table, data in the Services Received table, and all other data affected by the conversion of the Services Offered table to the Service Definition table (Performance Analytics dashboard data, constituent or business report data, and so on). Any custom Services Offered and Services Received data created in previous releases will not be automatically migrated to the new release, and, after upgrade, will not be accessible within the application until the data is migrated from the legacy entities to the Service Definition table. For details, see Services Offered and Services Received Migration Guidance and Configure a service definition for Playbooks in Public Sector Digital Services.

After the upgrade, certain public sector menus and menu items in the CSM Configurable Workspace revert to their original CSM label names. You can relabel these items for public sector use by updating the UX List Categories for Customer and Service Organizations. For details, see Relabel items for public sector use after upgrade.

Vancouver

Robotic Process Automation (RPA) Hub

Ensure that you upgrade the current installed Microsoft Software Installers (MSIs) (RPA Desktop Design Studio, Attended Robot, Unattended Robot, and Unattended Robot Login Agent), by downloading the RPA applications. For more information, see Download the RPA applications from RPA Hub.

The following upgrade steps are applicable only when you’re upgrading from San Diego or Tokyo to Vancouver.

Based on the number of records in the application file table, you could experience a potential delay while upgrading the RPA Hub applications from Tokyo or before to Vancouver.

Before upgrading RPA Hub to Vancouver, you must set the value of the glide.rollback.blacklist.TableParentChange.change system property to false. If this property doesn't exist in the System Property [sys_properties] table, add the property and set its value to false.

After you upgrade to the Vancouver, the bot process definitions change to the new structure, that is, the bot process configuration. Although the bot process configuration doesn't replace the bot process completely. Most fields are moved from bot process to bot process configuration.

If you upgrade to the Utah version without updating the system property value, the tables don’t extend the Application File table. Manually to update the table changes, see the Restructuring RPA Hub tables to sys_metadata in Utah article in the Now Support Knowledge Base.

Vancouver

Security Incident Response

Vancouver

Service Bridge

For information on upgrading and using the new Service Bridge applications, see Migrate from Service Bridge (legacy).

Vancouver

Service Operations Workspace for ITSM

Ensure that the following applications have compatible upgraded versions:

Service Operations Workspace ITSM Applications application (sn_sow_itsm_cont)
Service Operations Workspace ITOM Applications application (sn_sow_itom_cont)

Search:

Table 2. Compatible SOW versions
SOW-ITSM (sn_sow_itsm_cont)	SOW-ITOM (sn_sow_itom_cont)
1.1.x	21.0.y
1.2.x	21.1.y
1.3.x	21.2.y, 21.5.y, and 21.6.y
2.0.x	22.0.y
2.1.x	22.1.y and 22.y.y
4.0.x	24.y.y

Here, x is the sub-version of Service Operations Workspace ITSM Applications application (sn_sow_itsm_cont) and y is the sub-version of Service Operations Workspace ITOM Applications application (sn_sow_itom_cont).

If the upgraded instance has any of the following customizations, you need to migrate standard record page changes. For more information, see Configure a Standard Record Page in Service Operations Workspace.

Any custom declarative action of the client type
Any custom modal
Any custom horizontal tab or contextual side panel tab's screen or screen condition

After the 3.0 upgrade, the Recommendation Framework feature is no longer available, and instead, only the standard version of the Recommended Actions for ITSM feature is available.

Vancouver

Service Portal

After upgrading, you must specify the tables from which guest users can access data for any public widgets that accept the table input parameter. By default in the Vancouver Patch 7 release and later, public widgets that accept the table input parameter can't access and return data from any tables for guest users. If you added the glide.service_portal.widget.table_allow_list or glide.service_portal.widget.allow_list system properties before upgrading, the values of these properties will be migrated to the Public Table Allow List for widgets after upgrading to the Vancouver Patch 7 release or later. For more information, see Configure widget security.

Additionally, field-level read ACLs are enforced for filter conditions in Simple List widget instances by default. A new system property, glide.service_portal.enable_acls_for_encoded_query_in_list, enforces these ACLs regardless of whether the Enforce field-level Read ACLs on Filter query terms option is selected for Simple List widget instances. To use the Enforce field-level Read ACLs on Filter query terms option, change the value of glide.service_portal.enable_acls_for_encoded_query_in_list to false. For more information, see Simple List widget.

Vancouver

Service Portfolio Management

Viewing availability results was introduced in the Tokyo release but also applies to subsequent releases. On upgrade, for customers identified as having a heavy data load, the system initiates a long-running background job, which could take a long duration. For more information, see KB1123644.

Vancouver

Skills Management

If you’ve customized the URL for the Manage skills page, you must manually update the URL to point to the new page. Here’s the relative path to the new Manage skills page: https://<instance name>.service-now.com/now/nav/ui/manage-skills/params/parent-skill/2eb1c2029f100200a3bc1471367fcfe4/parent-department/221f79b7c6112284005d646b76ab978c/recursive-departments/true/recursive-skills/true/group-by/department. You can replace the existing path with this one.

Note: Make sure that the parent-skill and the parent-department sys_ids are the same IDs that are in your existing URL.

Vancouver

Software Asset Management

For information about upgrading from the Software Asset Management Foundation plugin (com.snc.sams), see Revert Software Asset Management customizations.

On upgrading to Vancouver, the Version and Edition fields in discovery map (DMAP) definitions support the new is_empty value. If the Edition field for an existing Microsoft SQL Server component DMAP definition was previously set to is_anything, it is automatically updated with the new is_empty value following content update.

Vancouver

Strategic Planning

Starting with v2.1.0, accessing the Goals module in Strategic Planning requires the sn_apw_advanced.spw_goal_user_read and sn_apw_advanced.spw_goal_user roles for read and edit access, respectively. After upgrading Strategic Planning, assign these roles to the existing goal users to manage goals in Strategic Planning.
Starting with v2.1.0, the existing targets with the Type field set to Milestone are considered qualitative targets. After upgrading Strategic Planning, for such existing targets, the Unit of measure is set to Yes/No, the Base value is set to No, and the Target value is set to Yes automatically. Also, the Actual value is set to Yes if the progress value is 100%, otherwise the value is set to No.
If you’re upgrading from an older version to Strategic Planning v2.1.0 or higher, a fix script is run to remove the milestone_editor role from the roadmap_editor role because the roadmap_editor role is no longer used. In this case, you may experience a longer time for the upgrade to complete if your ServiceNow instance has a large number of users with the roadmap_editor role. For more information, see KB1443618.
If you’re upgrading from an older version to Strategic Planning v3.0.0 or v3.4.0, the entities list may not load in the select entities step while you create or edit a portfolio plan. In this case, you must add the script in the List component for the Select entities page. For more information, see KB1566418.

Vancouver

Telecommunications Service Operations Management

The Integration Hub starter package, along with the external trigger, is included as components of the starter package in Vancouver Patch 1. The customer must use the family release Vancouver Patch 1 to get the Telecommunications API notification functionality.

Vancouver

Third-party Risk Management

Vancouver

Virtual Agent

Some features that were delivered in Vancouver Patch 7 are not available in the initial Washington DC early access release. These features will be available in future Patch releases of Washington DC:

Input Collector control changes

Drag and drop to reorder inputs within the node.
Specify the type of input that the node will accept: Text, Email, IP Address, Phone Number, URL, or custom.
Maximum number of inputs per node is 5.

Enforced user prompt option in the Text user input control

Toggle switch in the Advanced properties area that allows topic authors to specify the message shown to the user instead of the response generated by the LLM.

Vancouver

Vulnerability Response integrations

For more information about the released versions of the Vulnerability Response application, as well as the third-party and ServiceNow applications that are compatible with Vancouver, see the Vulnerability Response Compatibility Matrix and Release Schema Changes [KB0856498] article in the knowledge base.
For information about the new features for Vulnerability Response, see Vulnerability Response release notes.

Vancouver

Vulnerability Response

Due to a data model change in the Vulnerability Response application, upgrading might take noticeably longer than previous upgrades. For more information, see KB0856498.

While upgrading to a newer version, the upgrade time might increase based on the data and version that you’re upgrading from. This issue is due to additional schema changes that were added during the upgrade. For more information, see KB0856498.

Starting with version 20.0 of the Vulnerability Response application and version 2.03 of the Vulnerability Emergency Response application, the Vulnerability Analyst Workspace is renamed to Vulnerability Assessment Workspace. All references to Vulnerability Analyst workspace now are Vulnerability Assessment workspace.

Vancouver

AI Search

Washington DC Patch 9:

After you upgrade to Washington DC Patch 9 from an earlier release, make knowledge block content searchable by reindexing all your indexed sources that include knowledge articles. For details on reindexing, see Perform a full table index or reindex for a single indexed source or Perform a full table index or reindex for multiple indexed sources.

Washington DC:

When you upgrade to Washington DC, AI Search automatically updates your existing Genius Result configurations to use the new AI Search Genius Result Configuration form fields. This update procedure makes the following changes:
- Removes existing Genius result answer type field values.
- Migrates Genius result logic field values to the new AI Search request processor and AI Search response processor fields as appropriate.
After you upgrade your instance to Washington DC, AI Search retains the value that you previously set for the Boolean search operator to use when a search query includes multiple terms ( glide.ais.query.search_operator ) system property. To gain the benefits of the new enhanced query mode for multi-term searches, set this system property's value to AND then OR 2+ key terms. For details on AI Search system properties, see AI Search system properties.
Starting in Washington DC, the User [sys_user] table defaults to sorting indexed records by their sys_created_on dates instead of sorting them by their sys_updated_on dates. This change requires reindexing of the User table indexed source for AI Search, which can be time-consuming. When you upgrade to Washington DC from a previous family release, AI Search does not automatically reindex the User table indexed source. If you need to be able to search the latest configuration for user records, you can manually reindex the User table indexed source, which may take some time. Otherwise, AI Search will reindex individual User table records as they're updated until all records have been reindexed.

Washington DC

Automated Test Framework

Washington DC

Business Continuity Management

After upgrading to the Washington DC release, you must note the following important information for the existing business impact analyses, business continuity plans, and events:

For business impact analyses, the Source column in the dependency assessment is renamed to Primary source and the BCM source is renamed to Manual for manually added dependencies following an upgrade. When you select the Update dependencies button, the system adds the CMDB dependencies.
For business continuity plans, the Source column is renamed to Primary source following an upgrade. When you select the Update dependencies button, the system adds the CMDB and BIA dependencies. To maintain compatibility with the previous releases, the BCM administrator can configure the sources and keep only the BIA upstream dependency and BIA downstream dependencies as the sources in the updated configuration.
For events and exercises, when you select the Update dependencies button, the system adds the CMDB, BIA, and Business Continuity Planning (BCP) dependencies after an upgrade. To maintain compatibility with the previous releases, the BCM administrator can configure the sources and keep only the BIA upstream dependency and BIA downstream dependencies as the sources in the updated configuration.

Washington DC

Configuration Management Database (CMDB)

The column product_instance_id has been added to the base Configuration Item [cmdb_ci] table to support the new product instance identifier (PID), which enables the lookup and linking of any pre-existing related assets, CIs, and Install Base Items (IBI). For more information about the impact of that change during upgrade and how to minimize that impact, see the Upgrade impact of CMDB_CI schema changes for Washington release [KB1534035] knowledge base article.
If you enable CMDB 360 for the first time after upgrading to the Washington DC release, to enable the capture of CMDB 360 data for CIs from non-CMDB classes (classes not derived from the Configuration Item [cmdb_ci] class) you must set the glide.identification_engine.multisource_non_cmdb_ci_enabled system property to true.
If you have been using the legacy Data Certification application on Core UI, then any associated definitions won’t be available in the new implementation of Data Certification in CMDB Workspace. After upgrading to the Washington DC release and to CMDB Workspace version 6.0, you can convert definitions created in the legacy Data Certification application into draft Data Manager Certification policies in CMDB Workspace. For more information, see .

Washington DC

Core Now Platform

Previously, if a transaction was canceled, certain auditable operations were not being recorded. This behavior of missing audit records is because the platform executes some operations between the record change and is canceled before audit creation. But now, audits are created immediately after the record is changed, reducing the chance of a canceled transaction aborting the operation before the audit is recorded. To facilitate this update, audits are now recorded in the same thread as the transaction. Earlier audits were created in a background thread.

This change redefines the default value of the glide.db.audit.lazy property from true to false. Ideally, this property is not defined in the Properties table, which means that the majority of instances start using the new default value and behavior with the Washington DC release. On some instances, this property may have been inserted with the value set to true, which means that these instances won’t be able to use this change to audit behavior. Delete this property to leverage this update.

Washington DC

Encryption Key Management

If you upgrade your instance to Washington DC but don’t upgrade your MID Server, Secrets Management authentication fails. Avoid authentication failures by upgrading your MID Server to Washington DC. If you can’t upgrade, you must turn off authentication until MID Server is upgraded to Washington DC to avoid authentication failures.

For details on MID Server upgrades, see MID Server upgrades.

Washington DC

Enterprise Asset Management

After you upgrade to Washington DC, the model_component field isn't available in the Enterprise asset [sn_ent_asset] table. Instead, a new model_component_id field is available in the Asset [alm_asset] table. The ENT - Migrate to new model component script moves the existing model_component field data to the model_component_id field.

Note the following upgrade scenarios for the Total Cost of Ownership (TCO) of assets:

Upgrade works for all Enterprise Asset Management flow tasks
You must have task rate cards for each workflow task.
The TCO upgrade populates the Asset and Expense category fields on expense lines corresponding to each task.
Expense category is populated based on the expense lines and the source of the expense line.
You need to populate the TCO benchmark cost and the TCO benchmark threshold field on all existing models manually or using the bulk import functionality.
TCO upgrade populates following fields on asset forms:
- Asset end of useful life: The created date plus the useful life in months.
- Asset first used date: The created date.
- Asset TCO: The aggregated sum of all the expense lines related to the asset. For simple assets, Asset TCO is the aggregated sum of expense lines under it. For complex assets, Asset TCO is the aggregated sum of expense lines of the parent as well as its child assets.

Washington DC

Financial Services Operations Core

During the upgrade to Washington DC, the Financial Services Operations Core plugin reparents the following tables:

Note: You may experience a longer time for the upgrade to complete if your upgraded instance has a large number of records.

The Service Definition [sn_bom_service_definition] table extends from the Service Definition [sn_case_type_selection] table instead of the Request Definition [sn_ind_request_definition.
The Financial task [sn_bom_task] table extends from the Customer Service Task [sn_customerservice_task] table instead of the Global Task [task] table.
The Policy Participant [sn_bom_policy_participant] table extends from the Sold Product Related Party [sn_install_base_sold_product_related_party] table.

Reparenting enables leveraging of the benefits and advancements introduced by ServiceNow® Customer Service Management (CSM) while preserving the functionality of existing applications.

Washington DC

Hardware Asset Management 10.0.0

After your upgrade to Washington DC, keep in mind the following upgrade scenarios for the Total Cost of Ownership (TCO) of assets:

Upgrade works for all Hardware Asset Management flow tasks.
You must have task rate cards for each workflow task.
TCO upgrade populates an asset and expense category field on the expense line corresponding to each task.
Expense category is populated based on the expense lines and the source of the expense line.
You must populate the TCO benchmark cost and the TCO benchmark threshold field on all existing models manually or using the bulk import functionality.
TCO upgrade populates the following fields on assets:
- Asset end of useful life: Created date along with useful life in months.
- Asset first used date: Same as the created date.
- Asset TCO: Aggregated sum of all the expense lines related to the asset. For simple assets, Asset TCO is the aggregated sum of expense lines under it. For complex assets, Asset TCO is the aggregated sum of expense lines of the parent as well as its child assets.

Washington DC

Healthcare and Life Sciences Service Management Core

During the upgrade to Washington DC, the Healthcare sold product [sn_hcls_sold_product] parent table changes to Install base item [sn_install_base_item] for the following tables:

Member Plan [sn_hcls_member_plan]
Medication [sn_hcls_medication]
Immunization [sn_hcls_immunization]
Enrolled Program [sn_hcls_enrolled_program]
Enrolled Program Service [sn_hcls_enrolled_program_service]

In addition, the following tables have had their parent tables removed and are standalone tables:

Healthcare Organization[sn_hcls_organization]
Healthcare Location[sn_hcls_location]
Practitioner Location[sn_hcls_practitioner_facility]

This reparenting enables customers to use the organizations and location tables for a broader set of use cases.

Existing data is migrated in the following manner so that existing functionality isn’t impacted:

Reference of location field in sn_hcls_immunization updated to use cmn_location.
All data is moved from Healthcare Sold Product to Install Base Item tables.
Rows in the affected Install Base Item are populated based on the source_task value from the Healthcare Sold Product.
The state of sn_hcls_enrolled_program and sn_hcls_enrolled_program_service are copied from hcls_state.
All data moves to the standalone tables of Healthcare Organization, Healthcare Location, and Practitioner Location.
1. The script creates records in the Business Location table for existing records in the Healthcare Organization table to form a 1:1 reference.
2. Records that refer to a service organization are updated with a reference to the appropriate business location.
3. Any practitioner who has a record in the practitioner location will have a record created in the Service Organization Member table with the appropriate business location.
4. Records that contain healthcare location data will contain the parent service organization of that healthcare location.

Note: You may experience a longer time for the upgrade to complete if your upgraded instance has a large number of records.

Washington DC

Industrial Process Manager

The Industrial Process Manager application now has a dependency with the Operational Technology Service Management applications, which include Operational Technology Incident Management and Operational Technology Change Management. To install Industrial Process Manager on your instance, one of the following SKUs is required:

Operational Technology Visibility SKU
Operational Technology Service Management SKU
Any custom SKU that entitles Industrial Process Manager

Washington DC

Instance Data Replication

Log rotation is automatically enabled for the Replication Payload Error [idr_replication_payload_error] table after the upgrade. By default, the log rotation schedule is comprised of seven shards, with five days for each shard. All log entries in this table created before the upgrade are automatically truncated.

Washington DC

MID Server

For the latest MID Server system requirements, see MID Server system requirements. The minimum JRE version supported is 11.0.9 and the recommended version is 11.0.16.1.

If you have installed your own JRE, the upgrade process takes the following actions to ensure that the MID Server uses a supported JRE:

If a MID Server is using an unsupported version of the JRE when it upgrades, the upgrade process displays a warning message with the minimum and recommended JRE version.
If a supported JRE is running on the MID Server host, the upgraded MID Server uses that version.

All MID Server host machines require access to the download site at install.service-now.com to enable auto-upgrades. For additional details, read how the system manages MID Server upgrades.

Only one Windows MID Server service is permitted per executable path. Upgraded Windows MID Servers that have multiple services pointing to the same installation folder can’t start. See MID Server fails to start for more information.

For more information about MID Server upgrades, see the following topics:

MID Server pre-upgrade check: Describes how the AutoUpgrade monitor tests the ability of the MID Server to upgrade on your system before the actual upgrade.
Upgrade the MID Server manually: Describes how to upgrade your MID Servers manually.

Washington DC

Now Assist for Creator

To receive Workflow Studio performance improvements, install one of these versions of the Workflow Studio application from the ServiceNow Store. For more information about upgrading Workflow Studio, see Update to the latest version of Workflow Studio.

Table 3. Upgrade path for the flow generation skill
Is Now Assist for Creator already installed?	Version of Workflow Studio to use for upgrade
No	Upgrade Workflow Studio to version 25.1.3
Yes	Upgrade Workflow Studio to version 25.0.0

Washington DC

Now Assist

For more information about troubleshooting your Now Assist application and plugin upgrades, see the KB article for issues and mitigation for Now Assist upgrades.

Washington DC

Order Management

New features introduced in this Washington DC release aren’t supported in earlier releases of Order Management for Telecommunications, Media, and Technology.

Starting with the Washington DC release, the Monthly Recurring Charges (MRC) and the Non Recurring Charges (NRC) set for product offerings and product attribute characteristics are stored in the Pricing data model in price lists and price list lines, rather than the Product Offering data model. If you want to upgrade your pricing information to use price lists after upgrading to Washington DC, see the Price Management Plugin (com.sn_csm_pricing) uptake for Telecommunications, Media, and Technology customers upgrading to Washington [KB1585863] article in the Now Support Knowledge Base.

After upgrading to the Washington DC release, a fix script runs automatically to deactivate certain telecommunications list records that are no longer needed to resume the capture of an unfinished order. For more information on these records and using the former order capture process if needed, see the Deprecating Telco List for Order Capture [KB1586538] article in the Now Support Knowledge Base.

After upgrading to the Washington DC, review the reconfiguration workarounds for working on new change orders or orders with disconnect, suspend, or resume actions while using the product configurator. For details, see the Order line reconfiguration issues in Washington when using Order Capture UI [KB1585976] article in the Now Support Knowledge Base.

Washington DC

Order Management

Features introduced in this Washington DC release aren’t supported in earlier releases of Order Management.

If you’re upgrading from Order Management for Telecommunications and Media version 6.0 or earlier:

Starting with the  Washington DC  release, the  Monthly Recurring Charges  (MRC) and the  Non-Recurring Charges  (NRC) for product offerings and product attribute characteristics are stored in the Pricing data model in price lists and price list lines rather than in the Product Offering data model. If you want to upgrade your pricing information to use price lists after upgrading to  Washington DC, see the  Price Management Plugin (com.sn_csm_pricing) uptake for Telecommunications, Media, and Technology customers upgrading to Washington [KB1585863]  article in the Now Support Knowledge Base.
After upgrading to the  release, a fix script runs automatically to deactivate certain telecommunications list records that are no longer needed to resume the capture of an unfinished order. For more information on these records and using the former order capture process if needed, see the  Deprecating List for Order Capture [KB1586538]  article in the Now Support Knowledge Base.

After upgrading to the  Washington DC release, review the reconfiguration workarounds when working with new change orders or orders with disconnect, suspend, or resume actions while using the product configurator. For details, see the  Order line reconfiguration issues in Washington when using Order Capture UI [KB1585976]  article in the Now Support Knowledge Base.

Washington DC

Performance Analytics

The legacy PA Scores [pa_scores] table is being deprecated. If you still have indicator scores captured in the PA Scores table and the number of such scores is fewer than 43 million, these scores will be migrated automatically to the pa_scores_l1 and pa_scores_l2 tables upon upgrade. The expected amount of time added to upgrade is approximately two hours. For more information, see KB1294371 or Migrating Performance Analytics scores.

Washington DC

Platform Analytics Experience

Platform Analytics Experience functionality was previously located in the Platform Analytics Workspace. The functionality is now part of the core Now Platform, accessible through the Next Experience Unified Navigation. You can migrate any dashboards, reports, and Performance Analytics widgets that were created in Core UI to this functionality.

Washington DC

Playbooks in Workflow Studio

After you upgrade to Washington DC, update the Playbooks and Workflow Studio applications in the ServiceNow Store.

Washington DC

Portfolio Planning

Starting with v8.0.0, you can access the Strategic Portfolio Management (SPM) Pro-licensed features only in Strategic Planning Workspace. If you have been using Portfolio Planning Workspace to access SPM Pro-licensed features, such as Goals, Product Feedback, and Hybrid Portfolio Planning, you must now install Strategic Planning to access these features. For more information on the features that can be accessed only in Strategic Planning Workspace, see Comparing Portfolio Planning with Strategic Planning.

Washington DC

Predictive Intelligence

If you’re upgrading to Washington DC, you won't be able to create new regression solutions. If you have existing solutions, they will still be supported and you will be able to train and modify them, but you won't be able to create new ones.

The changes to the similarity and clustering solutions apply to all instances that are on Washington DC.

Washington DC

Proactive Service Experience Workflows

Customers who prefer not to receive trouble ticket notifications can disable the business rules related to the incident and case tables. To learn more about how to disable the business rules for trouble ticket notification, see Deactivate trouble ticket notification.

Washington DC

Product Catalog Management and Pricing Management

If you used attribute characteristics in the Standard Price Adjustment matrix in the initial release of the Sales and Order Management applications, and you're upgrading to the May 2024 release of Sales and Order Management applications, you must run a scheduled job that corrects the format of the automatically generated Code values. Run the Schedule job to modify code field on characteristic records that contain special characters on demand job to replace any character that is not a letter (a-z, A-Z), a number (0-9), an underscore (_), or a dollar sign ($) with an underscore (_). This job corrects the Code value so that it doesn’t start or end with an underscore, doesn’t begin with a digit, and contains no consecutive underscores.

Washington DC

Public Sector Digital Services

After the upgrade, certain public sector menus and menu items in the CSM Configurable Workspace revert to their original CSM label names. You can relabel these items for public sector use by updating the UX List Categories for Customer and Service Organizations. For more details on relabeling, navigate to All > Constituent Service > Administration > Guided Setup, and select Configurable Workspace for Public Sector Digital Services > Customize Workspace Labels Manually.

Washington DC

Robotic Process Automation (RPA) Hub

Ensure that you upgrade any of the following currently installed Microsoft Software Installers (MSIs) by downloading the RPA applications:

RPA Desktop Design Studio
Attended Robot
Unattended Robot
Unattended Robot Login Agent

For more information, see Download the RPA applications from RPA Hub.

The following upgrade steps are applicable only when you’re upgrading from San Diego or Tokyo to Washington DC.

Based on the number of records in the application file table, you could experience a potential delay while upgrading the RPA Hub applications from Tokyo or before to Washington DC.

Before upgrading RPA Hub to Washington DC, you must set the value of the glide.rollback.blacklist.TableParentChange.change system property to false. If this property doesn't exist in the System Property [sys_properties] table, add the property and set its value to false. For more information on how to add a property, see Add a system property.

After you upgrade to the Washington DC, the bot process definitions change to the new structure, which is the bot process configuration.

Although the bot process configuration doesn't replace the bot process completely, most fields are moved from bot process to bot process configuration. If you upgrade to the Utah version without updating the system property value, the tables don’t extend the Application File table. To update the table changes manually, see the Restructuring RPA Hub tables to sys_metadata in Utah article in the Now Support Knowledge Base.

Washington DC

Security Posture Control

For a complete list of the applications that are required to implement Security Posture Control, see Install the supported applications for Security Posture Control.

Washington DC

Service Operations Workspace for IT Service Management

Ensure that the following applications have compatible upgraded versions:

Service Operations Workspace ITSM Applications application (sn_sow_itsm_cont)
Service Operations Workspace ITOM Applications application (sn_sow_itom_cont)

Search:

Table 4. Compatible SOW versions
SOW-ITSM (sn_sow_itsm_cont)	SOW-ITOM (sn_sow_itom_cont)
1.1.x	21.0.y
1.2.x	21.1.y
1.3.x	21.2.y, 21.5.y, and 21.6.y
2.0.x	22.0.y
2.1.x	22.1.y and 22.y.y
3.1.x	23.y.y
4.x.x	24.y.y

In the table, x is the subversion of the Service Operations Workspace ITSM Applications application (sn_sow_itsm_cont) and y is the subversion of the Service Operations Workspace ITOM Applications application (sn_sow_itom_cont).

After the 3.0 upgrade, the Recommendation Framework feature is no longer available. Instead, only the standard version of the Recommended Actions for ITSM feature is available.

Washington DC

Service Portal

After upgrading, you must specify the tables from which guest users can access data for any public widgets that accept the table input parameter. By default in the Washington DC release, public widgets that accept the table input parameter can't access and return data from any tables for guest users. If you added the glide.service_portal.widget.table_allow_list or glide.service_portal.widget.allow_list system properties before upgrading, the values of these properties will be migrated to the Public Table Allow List for widgets after upgrading. For more information, see Configure widget security.

If a user previously selected a user consent preference for user experience analytics for portals different from the rest of the platform, the preference selected for the platform is also used for portals in the Washington DC release. For example, if users opted out of tracking for portals but opted in to tracking for the rest of the platform in the Vancouver release, user experience analytics for portals are tracked for them in the Washington DC release. Users can update their selection from the user profile page in portals at any time.

Washington DC

Software Asset Management

After upgrading to Washington DC, you must redo all your customizations related to Adobe and Microsoft 365 integrations with your ServiceNow instance because the functionalities of these integrations are moved to the Software Asset Management – SaaS License Management store application.

If you’ve customized an impacted file, the upgrade process skips the file and indicates a conflict. You must manually resolve the conflict and ensure that the old existing file is deleted.
If you haven't customized an impacted file, the file gets deleted as part of the upgrade, and a file with a new sys_id is created.

Washington DC

Strategic Planning

Starting with v4.0.2, you can access the Strategic Portfolio Management (SPM) Pro-licensed features only in Strategic Planning Workspace. If you have been using Portfolio Planning Workspace to access SPM Pro-licensed features, such as Goals, Product Feedback, and Hybrid Portfolio Planning, you must now install Strategic Planning to access these features. For more information on the features that can be accessed only in Strategic Planning Workspace, see Exploring Portfolio Planning in Strategic Planning.

If you’re upgrading to Strategic Planning v4.1.2 and previously had customized the List view or the Hierarchy view of the Goals page using the Personalization side panel, the user interface enhancements done in v4.1.2 may not appear. In this case, you must delete your user preference records. For more information on how to delete user preferences made using the Personalization side panel, see KB1642037.

Washington DC

Supplier Lifecycle Operations

After upgrading from the Vancouver release to the Washington DC release, you will see only the Source-to-Pay Workspace on the All navigation tab. You don't have to do anything if you choose to continue to use the Source-to-Pay Workspace.

However, you will see both the Source-to-Pay Workspace and Supplier Manager Workspace on the Workspaces tab. If you want to use the Supplier Manager Workspace instead of the default Source-to-Pay Workspace, ensure that you run the fixscript_migrate_workspace_to_smw.xml fix script after upgrading to the Washington DC release. You can download the fixscript_migrate_workspace_to_smw.xml file from the ServiceNow Store.

If you want to revert to using the Source-to-Pay Workspace, run the fixscript_migrate_workspace_to_s2p.xml fix script. You can download the fixscript_migrate_workspace_to_smw.xml file from the ServiceNow Store. For more information about how to run a fix script, see Run fix scripts.

After you upgrade to Washington DC, you must review all the post-upgrade tasks and complete them as needed. For more information, see Post-upgrade tasks for Supplier Lifecycle Management.

Washington DC

Third-party Risk Management

If you are a VRM user upgrading to TPRM, when upgrading to Vancouver or later from an earlier release, you must run each upgrade sequentially to ensure that fix scripts run correctly. This means upgrading from Utah to Vancouver, Vancouver to Washington DC, and so on. If the scripts do not run in the correct order, it can result in data inconsistencies, broken functionalities, and conflicts.

For more information on upgrading from VRM to TPRM, see Third-party Risk Management upgrade information.

Washington DC

Vulnerability Response integrations

For more information about the released versions of the Vulnerability Response application as well as the third-party and ServiceNow applications that are compatible with the Washington DC release, see the Vulnerability Response Compatibility Matrix and Release Schema Changes [KB0856498] article in the Now Support Knowledge Base.
For information about the new features of Vulnerability Response, see Vulnerability Response release notes.

Washington DC

Workflow Studio

To receive Workflow Studio performance improvements, install one of these versions of the Workflow Studio application from the ServiceNow Store.

Table 5. Upgrade path for the flow generation skill
Is Now Assist for Creator already installed?	Version of Workflow Studio to use for upgrade
No	Upgrade Workflow Studio to version 25.1.3
Yes	Upgrade Workflow Studio to version 25.0.0

Washington DC

AI Control Tower

General availability release, no upgrade.

Yokohama

Accounts Payable Operations

If you’re upgrading from a previous release, you must configure the reference field in the Tax Code [sn_fin_tax_code] table. The exception engine validates the invoice using the tax code and raises exceptions if necessary.

Yokohama

App Engine Studio

Due to a new process for assigning groups in AEMC, the same version of the Application Intake plugin must be activated on each of your instances.

For more information, see App Readiness and Compliance Report

Yokohama

Application Vulnerability Response

For information about the new features of Vulnerability Response, see Vulnerability Response release notes.
For more information about the released versions of the Application Vulnerability Response application as well as the third-party and ServiceNow applications that are compatible with the Xanadu release, see the Vulnerability Response Compatibility Matrix and Release Schema Changes [KB0856498] article in the Now Support Knowledge Base.

Yokohama

Automated Test Framework

Yokohama

Data Management

A data management policy record is automatically created for each table that is configured with an archive rule or a table cleaner rule prior to the upgrade.

Yokohama

Data Privacy

Licensing changes enable you to install Data Discovery, Data Discovery APIs, Data Anonymization, and Data Privacy APIs without an entitlement, but you must have an entitlement to run a job.

Yokohama

DevOps Change Velocity

If you are a new customer or are using a zBoot instance and you want to create type-based workflow change requests in DevOps Change Velocity, you must add the com.snc.change_management.change_model.type_compatibility property and set it to True. For more information, see Add a system property.

If you are an upgrading customer, you must run the ReConfigure Bitbucket Server Repositories for PullRequest job to re-configure your existing Bitbucket Server or Bitbucket Data Center repositories so that pull request records can be imported. You can navigate to All > System Definition > Scheduled Jobs to search for this job and run it.

Yokohama

Encryption Key Management

The GlideEncrypter API uses the three-key Triple Data Encryption Standard (3DES) encryption standard which NIST 800-131A Rev 2 has recommended against using after 2023. The following changes are taking place in the Yokohama release in preparation for a full deprecation of GlideEncrypter/3DES in the future.
- New Yokohama instances can’t use GlideEncrypter. All base system scripts have been changed to use alternative encryption processes.
- if you’re upgrading your Yokohama instances, you can still use 3DES, but you can also disable 3DES usage with a system property.
- Learn more about 3DES deprecation in KB1704481.

Yokohama

External Content Connectors

Beginning with version 2 of the External Content Connectors application, external content connectors implement semantic vector indexing for crawled items. When you upgrade to a version that supports semantic vector indexing, your existing connectors will reindex all previously retrieved items the next time they're visited by a crawl, even if those items' content is unchanged. To force semantic vector indexing of your external content items as soon as possible after upgrading, cancel any running crawls, then restart the canceled crawls manually.

Yokohama

Field Service Management

Upgrading to Yokohama may extend the upgrade maintenance time of a customer due to Appointment Booking. The Appointment Booking configuration tables get extended to the Application File [sys_metadata] table as a part of the upgrade. After upgrading to Yokohama, re-parenting occurs automatically and the duration of the re-parenting depends on the number of records in Application File [sys_metadata] table.

Yokohama

Financial Services Card Operations

During the upgrade to Yokohama, the Financial Services Card Operations plugin reparents the Card Disputes Transaction table [sn_bom_credit_card_disputes_transaction] to the Financial Task table [sn_bom_task] in Financial Services Operations Core.

Reparenting leverages the benefits and advancements of ServiceNow® Financial Services Operations Core while preserving the functionality of existing applications.

Note: If your instance uses the Card Disputes Transaction table [sn_bom_credit_card_disputes_transaction] and it contains a large amount of data, you may experience increased upgrade times.

Yokohama

ITOM Visibility

3DES support is planned for permanent removal from the MID Server for MID Servers with SSH-based Discovery or SSH-based integrations. For more information, see 3DES deprecation in SSH from Xanadu [KB1644950].

Yokohama

Impact

The Impact Store Application configuration requires a sequence of tasks. See Configuring the Impact Store Application for details.

Yokohama

Now Assist Analytics

Now Assist Analytics is installed and updated when you install or update any Now Assist application. If you have issues installing or updating applications, see this knowledge article for steps that may address your issue. Otherwise, you can make a Support case.

Yokohama

Now Assist for Security Incident Response and Now Assist for Vulnerability Response

For more information about required applications for Now Assist for Vulnerability Response, see Supporting information for Now Assist for Vulnerability Response. For more information about required applications for Now Assist for Security Incident Response, see Supporting information for Now Assist for Security Incident Response.

Starting with version 2.0.1, the name of the Now Assist for Security Operations application in ServiceNow® Store and in your Now Platform® instance has changed to Now Assist for Security Incident Response. You must upgrade to version 2.0.1 to access the following features:

Generate resolution notes in the Now Assist context menu.
Generate correlation insights for a security incident investigation from the Now Assist panel.

The AI Search application must be enabled so that the recommended actions skill works for security incidents. To verify that AI Search is enabled on your instance, navigate to All > AI Search > AI Search Status. Contact support if the page indicates that AI Search is not enabled.

Yokohama

Now Assist in Contract Management

If you’re upgrading to Now Assist in Contract Management from a previous version and you have customized agentic workflows, run a fix script to migrate the existing data to the Now Assist Admin console.

Navigate to All > System Definition > Fix Scripts.
In the Name field, search for Upsert DI skill config.
In the script, add the agentic workflow ids that you want to migrate to the Now Assist Admin console.
Select Run Fix Script.

For more information, see Post-upgrade steps for Now Assist in Contract Management.

Yokohama

Platform Analytics experience

If you had previously migrated your analytics assets to Platform Analytics, assets that were in compatibility mode but are newly supported in Yokohama are migrated automatically.

Yokohama

Playbooks in Workflow Studio

After you upgrade to Yokohama, update the Workflow Studio application in the ServiceNow Store.

Yokohama

Product Catalog Management and Pricing Management

After upgrading to the May 2025 release of Sales and Order Management applications, you must run a scheduled job that automatically enables the Allow multiple configurations option when your catalog admin creates product offerings with an associated product specification. This job is called Scheduled job with an upgrade script to set 'allow_multiple_configurations' to true on an Offering. When multiple product offering configurations are allowed in configurable opportunities, quotes, or orders, agents can create multiple instances of a child product offering and define custom configurations for each offering instance.

Note: The Allow multiple configurations option is always enabled (set to true) for all product offerings that have an associated product specification. However, if the product specification has a child hierarchy, this option is honored only for orders placed through the TMF APIs. For specifications without a hierarchy, the flag is honored across all ordering channels.

The May 2025 release provides a default pricing plan that includes a new step, Apply Renewal Adjustment. If you've been using a custom pricing plan from an earlier release, review the default pricing plan, which is in a Retired state after upgrading to the May 2025 release. Determine whether you want to publish the default plan or customize the default pricing plan for your needs and then publish the custom plan to be used.

Yokohama

Public Sector Digital Services

After the upgrade, certain public sector menus and menu items in the CSM Configurable Workspace revert to their original CSM label names. You can relabel these items for public sector use by updating the labels for the Customer, Accounts, and Service Organizations UX list category records. For more details on relabeling, navigate to All > Constituent Service > Administration > Guided Setup, and select Configurable Workspace for Public Sector Digital Services > Customize Workspace Labels Manually.

Yokohama

RPA Hub

Upgrade any of these currently installed Microsoft Software Installers (MSIs) by downloading the RPA applications:

RPA Desktop Design Studio
Attended Robot
Unattended Robot
Unattended Robot Login Agent

For more information, see Download the RPA applications from RPA Hub.

The following upgrade information is applicable only when you’re upgrading from San Diego or Tokyo to Yokohama.

Based on the number of records in the application file table, you may experience a delay while upgrading the RPA Hub applications from Tokyo or earlier releases to Yokohama.

Before upgrading RPA Hub to Yokohama, you must set the value of the glide.rollback.blacklist.TableParentChange.change system property to false. If this property doesn't exist in the System Property [sys_properties] table, add the property and set its value to false. For more information on how to add a property, see Add a system property.

After you upgrade to Yokohama, the bot process definitions change to the new structure, which is the bot process configuration.

Although the bot process configuration doesn't replace the bot process completely, most fields are moved from the bot process to the bot process configuration. If you upgrade to Yokohama without updating the system property value, the tables don’t extend the Application File [sys_metadata] table. To update the table changes manually, see the Restructuring RPA Hub tables to sys_metadata in Utah and beyond release [KB1223629] article in the Now Support Knowledge Base.

Yokohama

Service Bridge

When using Service Bridge for Providers and Service Bridge for Consumers in a single instance, you must upgrade both applications simultaneously to the same version to maintain compatibility.
The Service Bridge Global Script Include is automatically installed or updated when you install the Service Bridge application on the following platform versions:
- Washington DC Patch 9
- Xanadu Patch 4
- Yokohama
Service Bridge 2.x.x, which was first released with the Xanadu release, does not support migration of Service Bridge (Legacy) versions. If you are using a Service Bridge (Legacy) version, before you upgrade to the Yokohama release, you must follow instructions in the Service Bridge for Providers (Legacy) - Migration Utility [KB1499823] article in the Now Support Knowledge Base to migrate your configuration data.
If you are upgrading from Service Bridge version 1.x.x, follow the steps in Upgrade Guide - Service Bridge for Providers and Consumers application (v2.x.x release) [KB1700387] to migrate your Service Bridge applications.
Due to the introduction of mismatched version support, new entitlements cannot be activated until both the consumers and providers upgrade to Service Bridge version 2.x.x. Older active entitlements will continue to work but new ones cannot be activated.
If you upgrade to Service Bridge version 2.0.55 with Sales and Order Management plug-in version 1.0.4 before upgrading the platform to the Yokohama release, the new Deny ACLs will not be installed. To ensure the Deny ACLs get installed, after upgrading to Yokohama, you must click Repair to reinstall the Service Bridge application.

Yokohama

ServiceNow IDE

ServiceNow IDE version 1.1.4 is active by default on instances on the Yokohama release. Update to ServiceNow IDE version 2.0 or later to use the latest features. For information about updating ServiceNow IDE, see Installing applications in Application Manager.

Yokohama

ServiceNow SDK

Upgrade to the latest version of the ServiceNow SDK with the now-sdk upgrade command. For more information, see Upgrade the ServiceNow SDK.

ServiceNow SDK version 3.0 supports integrating with ServiceNow instances beginning with the Washington DC release.

Note: For more information about minor releases of the ServiceNow SDK, see the ServiceNow IDE, SDK, and Fluent articles in the ServiceNow Community.

Yokohama

ServiceNow Studio

ServiceNow Studio no longer has to be downloaded from the ServiceNow Store. It’s available on the Now Platform by default.

Yokohama

Software Asset Management

Starting from the Yokohama release, all the reconciliation script includes are being moved from the family release to the Software Asset Management store application (com.sn_itam_samp). When upgrading to Yokohama, if you have made customizations to reconciliation script includes, you must move your customizations to the new script includes. The old script includes will be deprecated.

When upgrading to Yokohama Patch 1 with the Software Asset Management (sn_itam_samp) 2.1.0 store application installed, you must delete the entitlements for the existing CrowdStrike integration profiles. Then, create new entitlements for various CrowdStrike products, such as CrowdStrike Falcon Endpoint Protection and CrowdStrike Falcon Discover, based on their license metrics. These metrics include the Reserved Hourly Average Sensor and Sensor Subscription, which are found under the CrowdStrike License Metric Group.

If any existing CrowdStrike profiles are in the Draft state, create new integration profiles and delete the existing ones.
If any existing CrowdStrike profiles are in the Published state, their state changes to Draft.

Yokohama

Telecommunications Service Operations Management (TSOM)

After installing Telecommunications Service Operations Management TSOM, any customized IRE identification rules applied to interface cards, slots, sub-slots and network interfaces may be affected. You must review and validate the rules to ensure proper functionality.

Yokohama

Third-party Risk Management

Starting with the Vancouver release, if you’re a VRM user upgrading to TPRM, from an earlier release, you must run each upgrade sequentially to ensure that fix scripts run correctly. This means upgrading from one release to the next rather than skipping to the latest release. Not running scripts in the correct order can result in data inconsistencies, broken functionalities, and conflicts.

For more information on upgrading from VRM to TPRM, see Third-party Risk Management upgrade information.

Yokohama

Vulnerability Response integrations

For more information about the released versions of the Vulnerability Response application as well as the third-party and ServiceNow applications that are compatible with the Yokohama release, see the Vulnerability Response Compatibility Matrix and Release Schema Changes [KB0856498] article in the Now Support Knowledge Base.
For information about the new features of Vulnerability Response, see Vulnerability Response release notes.

Yokohama

Vancouver Release Notes

Filters

Versions

Products