Upgrade information for all Yokohama features and products
Cumulative release notes summary on upgrade information for Yokohama features and products.
| Application or feature | Details | ||||||
|---|---|---|---|---|---|---|---|
| AI Control Tower | General availability release, no upgrade. | ||||||
| AI Search | When you upgrade to Yokohama 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 AI Search indexed source or Perform a full table index or reindex for multiple AI Search indexed sources. | ||||||
| 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. | ||||||
| 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 . | ||||||
| Application Manager | Application Manager is active by default on instances on the Yokohama release. Upgrade your instance to Yokohama patch 11 or later to use the latest features. For information about upgrading your ServiceNow AI Platform instance, see Prepare your upgrade. | ||||||
| Application Vulnerability Response |
| ||||||
| Automated Test Framework | Copy and customize quick start tests provided by the ServiceNow AI 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 . | ||||||
| Configuration Management Database (CMDB) | Three new indexes (parent, type), (child, type), and (child, parent, type, port) are added to the CI Relationship [cmdb_rel_ci] table to improve the performance of Identification and Reconciliation Engine (IRE) querying this table. This change is likely to increase upgrade time. For more information about the impact of this change during upgrade and to learn how to minimize that impact, see Increased Yokohama Upgrade Time due to cmdb_rel_ci index additions [KB1703367]. | ||||||
| Data Management |
| ||||||
| 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. | ||||||
| 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 to search for this job and run it. | ||||||
| Digital End-User Experience | To upgrade your DEX
Desktop Assistant, do the following:
| ||||||
| Encryption Key Management |
| ||||||
| 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. When you upgrade to version 4 of the External Content Connectors application from an earlier version, searches may not show all previously crawled content until you've completed both a content crawl and a user mapping crawl for each upgraded connector. The first content crawl run after the upgrade will reindex all searchable content from the source system, and the user mapping crawl will reindex all security principals from the source system. All crawled content should be shown in searches after both of these crawls are complete. | ||||||
| Field Service Management |
| ||||||
| 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. | ||||||
| Generative AI Controller | Generative AI Controller 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. | ||||||
| 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]. | ||||||
| Impact | The Impact Store Application configuration requires a sequence of tasks. See Configuring the Impact Store Application for details. | ||||||
| Instance Data Replication | Improve the performance and processing efficiency of Instance Data Replication (IDR) by upgrading your replication sets to V2, which uses Hermes Messaging Service. For details, see Upgrading legacy replication sets to V2 in 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. | ||||||
| MID Server | For the latest MID Server system requirements, see MID Server system requirements. The minimum JRE version supported is 17.0.10 and the recommended version is 17.0.12. If you have installed your own JRE, the upgrade process
takes the following actions to verify that the MID Server uses a
supported JRE:
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 according to the 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:
| ||||||
| Now Assist | If you customized UI actions or other items that are associated with Now Assist skills, ensure that your customized code is updated with the new skill releases. Otherwise, certain functions may not work as expected. If you run into issues when you're upgrading a Now Assist product, see KB1637452: Issues and mitigation for Now Assist (Generative AI) Applications and Plugin updates. You may need to log in to view the article. | ||||||
| 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. | ||||||
| Now Assist Skill Kit | If you customized UI actions or other items that are associated with Now Assist skills, ensure that your customized code is updated with the new skill releases. Otherwise, certain functions may not work as expected. If you run into issues when you're upgrading a Now Assist product, see KB1637452: Issues and mitigation for Now Assist (Generative AI) Applications and Plugin updates. You may need to log in to view the article. | ||||||
| Now Assist for Hardware Asset Management (HAM) | Only users with the procurement_user role can access the Help manage hardware asset requests agentic workflow including the following AI agents:
| ||||||
| Now Assist for IT Service Management (ITSM) | When you upgrade to the Zurich Patch 4 release, any customizations you may have made to the Now Assist context menu (NACM) won’t be preserved. For more information, see the Community article Upgrade information for the NACM support in Now Assist for ITSM. | ||||||
| Now Assist for Security Incident Response | For more information about required applications for Now Assist for Security Incident Response, see Supporting information for Now Assist for Security Incident Response. Note:
Upgrading the Now Assist plugins activate any designated skills that were previously untouched by the customer.
Starting with version 2.0.1, the name of the Now Assist for Security Operations application in ServiceNow® Store and in your ServiceNow AI Platform® instance has changed to Now Assist for Security Incident Response. You must upgrade to version 2.0.1 to access the following features:
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 . Contact support if the page indicates that AI Search is not enabled. | ||||||
| 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. Note:
Upgrading the Now Assist plugins activate any designated skills that were previously untouched by the customer.
| ||||||
| Now Assist in Contract Management | If you’re upgrading to Now Assist in Contract Management starting with Yokohama Patch 3 from a previous version and you have customized use cases, run a fix script to migrate the existing data to the Now Assist Admin console.
| ||||||
| 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. | ||||||
| Playbooks in Workflow Studio | After you upgrade to Yokohama, update the Workflow Studio application in the ServiceNow Store. | ||||||
| Portfolio Planning | After upgrading to Portfolio Planning v8.8.0, the custom view settings previously saved under user preferences will be cleared. You must reapply these changes and create views as needed. For instructions, see and . | ||||||
| Product Catalog Management and Pricing Management | After upgrading to the May 2025 release of Sales Customer Relationship 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. | ||||||
| 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 , and select . | ||||||
| RPA Hub | Upgrade any of these currently installed Microsoft Software Installers (MSIs) by downloading the RPA applications:
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. | ||||||
| Security Posture Control | For a complete list of the applications that are required to implement Security Posture Control, see Install Security Posture Control. | ||||||
| Service Exchange |
| ||||||
| Service Operations Workspace for ITSM | Ensure that the following applications have compatible upgraded versions:
For more information on compatible versions, see . | ||||||
| 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 Updating applications. | ||||||
| ServiceNow SDK | Upgrade to the latest version of the ServiceNow SDK with the 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. | ||||||
| ServiceNow Studio | ServiceNow Studio no longer has to be downloaded from the ServiceNow Store. It’s available on the ServiceNow AI Platform by default. | ||||||
| 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.
| ||||||
| Strategic Planning | After upgrading to Strategic Planning v4.7.0, the following changes apply to user preferences:
| ||||||
| Subscription Management | Subscription Management version 4.1 is active by default on all instances of the Yokohama release. Update to Subscription Management version 6.0.2 or later to use the latest features. For more information about updating Subscription Management, see Update an application or plugin. | ||||||
| Telecommunications Network Inventory | The Yokohama release needs the Xanadu platform version to support the Design and Assign playbook feature. | ||||||
| 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. | ||||||
| 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. For existing TPRM customers, after upgrading to version 20.2.4, data from the Industry column in the Company [core_company] table is automatically migrated to the tprm_industry column. Migration can take several hours depending on the number of records in the Company [core_company] table. After migration, a system log message confirms that the migration is complete. Review the Company [core_company] table content and update any customizations referencing the Industry field to use tprm_industry. After verifying the migration and updating customizations, you can drop the Industry column. | ||||||
| Usage Insights |
| ||||||
| Vulnerability Response Integration with Claroty CTD | Claroty CTD v5.1 is also supported for the Vulnerability Response Integration with Claroty CTD application. | ||||||
| Vulnerability Response integrations |
| ||||||
| Workforce Optimization for ITSM |
|