Upgrade information for all Washington DC features and products

Cumulative release notes summary on upgrade information for Washington DC features and products.

Before you upgrade to Washington DC, review the upgrade information for any products you may have. Some products require you to complete specific tasks before you upgrade.

Application or feature	Details
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 AI Search indexed source or Perform a full table index or reindex for multiple AI Search 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.
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 Available quick start tests by application or feature.
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.
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 .
Core ServiceNow AI 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.
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.
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.
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.
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.
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. The script creates records in the Business Location table for existing records in the Healthcare Organization table to form a 1:1 reference. Records that refer to a service organization are updated with a reference to the appropriate business location. 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. 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.
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
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. 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 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.
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.
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 1. 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
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. 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.
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.
Platform Analytics Experience	Platform Analytics Experience functionality was previously located in the Platform Analytics Workspace. The functionality is now part of the core ServiceNow AI 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.
Playbooks in Workflow Studio	After you upgrade to Washington DC, update the Playbooks and Workflow Studio applications in the ServiceNow Store.
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.
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.
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.
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.
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.
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.
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.
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) 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 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.
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. 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. 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.
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.
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.
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 Operations.
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.
User Experience Analytics	Users can opt out of basic tracking. A funnel data visualization is available for Usage Insights data sources.
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.
Workflow Studio	To receive Workflow Studio performance improvements, install one of these versions of the Workflow Studio application from the ServiceNow Store. 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