Upgrade information for all Australia features and products

  • Rversion finale: Australia
  • Mis à jour 12 mars 2026
  • 18 minutes de lecture

    • Cumulative release notes summary on upgrade information for Australia features and products.

    Before you upgrade to Australia, 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 Control Tower

    Not applicable.

    Asset Audit Response
    Care Team Operations for Biomed

    Strengthen your instance security and maintain backward compatibility through enhanced protections for read‑only fields across the ServiceNow AI Platform®. These back-end changes include a new “read_only_option” field with granular control levels, including “strict_read_only” and “client_script_modifiable". If you have custom client scripts that modify read‑only fields on the ServiceNow AI Platform® using g_form.setValue() or g_form.clearValue(), see the Remediation for strict read-only fields preventing client side updates [KB2718122] article in the Now Support Knowledge Base. This article provides additional technical details on how to identify affected fields and adjust their settings. For more information about granular read-only security options, see Configuring read-only security options.

    If you have the feature administrator role you can now complete tasks that were initially reserved for users with the broader administrator role.

    Care Team Operations for Environmental Services

    If you have the feature administrator role you can now complete tasks that were initially reserved for users with the broader administrator role.

    Care Team Operations for Facilities

    If you have the feature administrator role you can now complete tasks that were initially reserved for users with the broader administrator role.

    Care Team Operations for Healthcare IT

    Strengthen your instance security and maintain backward compatibility through enhanced protections for read‑only fields across the ServiceNow AI Platform®. These back-end changes include a new “read_only_option” field with granular control levels, including “strict_read_only” and “client_script_modifiable". If you have custom client scripts that modify read‑only fields on the ServiceNow AI Platform® using g_form.setValue() or g_form.clearValue(), see the Remediation for strict read-only fields preventing client side updates [KB2718122] article in the Now Support Knowledge Base. This article provides additional technical details on how to identify affected fields and adjust their settings. For more information about granular read-only security options, see Configuring read-only security options.

    If you have the feature administrator role you can now complete tasks that were initially reserved for users with the broader administrator role.

    Cloud Cost Management 10.0

    The Cloud Cost Management platform support is available beginning with the Xanadu release. For instructions on upgrading Cloud Cost Management to Australia, see Upgrade Cloud Cost Management.

    Configuration Management Database (CMDB)

    Due to changes in the Configuration Item [cmdb_ci] table, if you're upgrading to Australia, you might experience an increased upgrade time. To learn more about this change and reducing its impact, see the Increased Australia Upgrade Time due to cmdb_ci composite index addition [KB2588894] article in the Now Support Knowledge Base.

    If you're upgrading from Xanadu or Yokohama directly to the Australia release, you must run the Remove CMDB Roles from ITIL roles and Add CUD access to sn_cmdb_admin/sn_cmdb_editor roles scheduled job to correctly configure some user roles, such as CMDB Admin and CMDB Editor. For more information about this scheduled job and its use, see the CMDB Zurich release notes.

    Strengthen your instance security and maintain backward compatibility through enhanced protections for read‑only fields across the ServiceNow AI Platform®. These back-end changes include a new “read_only_option” field with granular control levels, including “strict_read_only” and “client_script_modifiable". If you have custom client scripts that modify read‑only fields on the ServiceNow AI Platform® using g_form.setValue() or g_form.clearValue(), see the Remediation for strict read-only fields preventing client side updates [KB2718122] article in the Now Support Knowledge Base. This article provides additional technical details on how to identify affected fields and adjust their settings. For more information about granular read-only security options, see Configuring read-only security options.

    Employee Center

    Strengthen your instance security and maintain backward compatibility through enhanced protections for read‑only fields across the ServiceNow AI Platform®. These back-end changes include a new “read_only_option” field with granular control levels, including “strict_read_only” and “client_script_modifiable". If you have custom client scripts that modify read‑only fields on the ServiceNow AI Platform® using g_form.setValue() or g_form.clearValue(), see the Remediation for strict read-only fields preventing client side updates [KB2718122] article in the Now Support Knowledge Base. This article provides additional technical details on how to identify affected fields and adjust their settings. For more information about granular read-only security options, see Configuring read-only security options.

    Employee Center Pro

    Strengthen your instance security and maintain backward compatibility through enhanced protections for read‑only fields across the ServiceNow AI Platform®. These back-end changes include a new “read_only_option” field with granular control levels, including “strict_read_only” and “client_script_modifiable". If you have custom client scripts that modify read‑only fields on the ServiceNow AI Platform® using g_form.setValue() or g_form.clearValue(), see the Remediation for strict read-only fields preventing client side updates [KB2718122] article in the Now Support Knowledge Base. This article provides additional technical details on how to identify affected fields and adjust their settings. For more information about granular read-only security options, see Configuring read-only security options.

    Encryption Key Management
    • In pre-Zurich releases, the GlideEncrypter API used 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 Australia release in preparation for a full deprecation of GlideEncrypter/3DES in the future:
      • New Australia instances can’t use GlideEncrypter. All base system scripts have been changed to use alternative encryption processes.
      • if you’re upgrading your Australia instances, you can still GlideEncrypter, which has been updated to use AES256-GCM encryption via the Key Management Framework.
      • Learn more about 3DES deprecation in KB1704481.
    Hardware Asset Management
    • To enhance security and manage admin access precisely, the granular admin roles are now installed. These roles replace broad admin checks by assigning specific privileges based on user tasks, rather than granting full admin access:
      • sn_hamp.ham_system_admin: Provides access to HAM licensing, HAM Guided Setup, HAM application properties and system properties, and a few tables.
      • sn_hamp.ham_asn_admin: Provides access to the Advanced Shipment Notification (ASN) feature.
      • asset_integration_admin: Provides access to Standard hardware Zero touch request and carrier integration features, and shipment tables.
      • asset_system_admin: Provides access to asset job log, content audit, transfer order, expense management, and model management.
      • asset_task_admin: Provides access to asset tasks.
      • procurement_system_admin: Provides access to procurement module, tables, and tasks.
      • contract_system_admin: Provides access to contract module, tables, and tasks.
      • asset_licensing_admin: Provides access to the ITAM licensing module.
      • asset_recommendation_admin: Provides access to recommendation actions.
    • Strengthen your instance security and maintain backward compatibility through enhanced protections for read‑only fields across the ServiceNow AI Platform®. These back-end changes include a new “read_only_option” field with granular control levels, including “strict_read_only” and “client_script_modifiable". If you have custom client scripts that modify read‑only fields on the ServiceNow AI Platform® using g_form.setValue() or g_form.clearValue(), see the Remediation for strict read-only fields preventing client side updates [KB2718122] article in the Now Support Knowledge Base. This article provides additional technical details on how to identify affected fields and adjust their settings. For more information about granular read-only security options, see Configuring read-only security options.
    Healthcare Operations Core

    Strengthen your instance security and maintain backward compatibility through enhanced protections for read‑only fields across the ServiceNow AI Platform®. These back-end changes include a new “read_only_option” field with granular control levels, including “strict_read_only” and “client_script_modifiable". If you have custom client scripts that modify read‑only fields on the ServiceNow AI Platform® using g_form.setValue() or g_form.clearValue(), see the Remediation for strict read-only fields preventing client side updates [KB2718122] article in the Now Support Knowledge Base. This article provides additional technical details on how to identify affected fields and adjust their settings. For more information about granular read-only security options, see Configuring read-only security options.

    If you have the feature administrator role you can now complete tasks that were initially reserved for users with the broader administrator role.

    Healthcare and Life Sciences Service Management Core

    Strengthen your instance security and maintain backward compatibility through enhanced protections for read‑only fields across the ServiceNow AI Platform®. These back-end changes include a new “read_only_option” field with granular control levels, including “strict_read_only” and “client_script_modifiable". If you have custom client scripts that modify read‑only fields on the ServiceNow AI Platform® using g_form.setValue() or g_form.clearValue(), see the Remediation for strict read-only fields preventing client side updates [KB2718122] article in the Now Support Knowledge Base. This article provides additional technical details on how to identify affected fields and adjust their settings. For more information about granular read-only security options, see Configuring read-only security options.

    If you have the feature administrator role you can now complete tasks that were initially reserved for users with the broader administrator role.

    Impact

    The Impact Store Application configuration requires a sequence of tasks in a unified registration process. See Configure the Impact Store Application.

    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 composed of seven shards, with five days for each shard. All log entries in this table that are created before the upgrade are automatically truncated.

    MCP Server Console
    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 21.0.7.

    If you have installed your own JRE, the upgrade process takes the following actions to verify 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 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, confirm that your customized code is updated with the new skill releases. Otherwise, certain functions might not work as expected.

    If you run into issues when you're upgrading a Now Assist product, see the Issues and mitigation for Now Assist (Generative AI) Applications and Plugin updates [KB1637452] article in the Now Support Knowledge Base. You might need to log in to view the article.

    The Australia release introduces enhanced protections for read‑only fields across the ServiceNow AI Platform. These changes include a new read_only_option field with granular control levels, including strict_read_onlyand client_script_modifiable. The changes occur in the back end and maintain backward‑compatible behavior. This update helps strengthen instance security while preserving flexibility. If you have custom client scripts that modify read‑only fields using g_form.setValue() or g_form.clearValue(), refer to the KB2718122 article in the Now Support Knowledge Base to identify affected fields and adjust the settings.

    The existing access control lists (ACLs) have been updated to replace the admin role with purpose-driven granular roles within scripts or security attributes. As part of this update, the getRoles() API is replaced with the hasRole() API for authorization purposes. Additionally, all references to the admin role in the code have been substituted with the granular roles for authorization use cases. For more information, see https://www.servicenow.com/docs/r/platform-security/granular-admin-roles.html.

    Now Assist for Configuration Management Database (CMDB)

    To enable Now Assist to provide detailed descriptions of CIs and classes, you must activate the 'External Content Connectors' plugin, install the ‘ServiceNow Product Documentation’ connector, and then crawl the product documentation. For configuration instructions, see Configure the CI form contextual help skill.

    Now Assist for Creator

    To upgrade the Build Agent application, upgrade the Now Assist for Creator application (sn_now_creator), which includes the Build Agent Pro plugin (sn_build_agent_pro). To upgrade the Build Agent (Trial) app, upgrade the sn_build_agent plugin.

    Now Assist for Employee Center Pro

    Now Assist for Employee Center Pro only provides employee or requester conversations and might require other Now Assist products to deliver AI agents or other related features.

    Now Assist for HR Service Delivery (HRSD)
    Now Assist for IT Service Management (ITSM)
    Now Assist for SFA
    Now Assist for Software Asset Management (SAM)
    Now Assist for Zero Copy Connector
    Now Assist in Virtual Agent
    Operational Resilience
    Beginning with Operational Resilience release 22.0.x, the following scheduled jobs are deactivated for new installations by default:
    • Calculate red flags for CSDM and dependencies
    • Update CSDM and other dependencies
    For existing installations, these jobs retain their current active or inactive state.
    Performance Analyzer

    Starting with the Zurich release, Performance Analyzer is available on your instance automatically. For access to Performance Analyzer for earlier instances, install Performance Analyzer from the ServiceNow® Store.

    Platform Analytics experience

    After upgrading, only admins can create Core UI analytics objects: reports, Performance Analytics widgets, responsive dashboards, and interactive filters. Other users can still view and edit Core UI objects but can create only Platform Analytics objects, such as data visualizations.

    When upgrading, the published status on all Core UI reports changes to false, making them unpublished.

    After upgrading, the Analytics Hub isn't available. Links to the Analytics Hub are redirected to KPI Details.

    Playbook

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

    Product Catalog Management and Pricing Management

    Pricing Management v16.0.0 provides a default pricing plan that includes changes to support pricing strategies introduced in this release. If you've been using a custom pricing plan from an earlier release, after upgrading to Pricing Management v16.0.0, the default pricing plan is in a Retired state. Determine whether you want to publish the default pricing plan for use or customize it.

    Public Sector Digital Services

    After the upgrade, certain public sector menus and menu items in 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.

    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 Australia.

    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 Australia.

    Before upgrading RPA Hub to Australia, 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 Australia, 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 Australia 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.

    ReleaseOps
    Service Exchange (formerly Service Bridge)
    Important :
    Do not upgrade your ServiceNow® instance to the Australia release if you rely on Service Exchange. A known RPS issue prevents Service Exchange from functioning correctly. Proceed with the upgrade only after Australia Patch 1 becomes available.
    • Service Exchange version 2.x.x, which was first released with the Xanadu release, doesn’t support migration of Service Exchange (Legacy) versions.

      Service Exchange (Legacy) version: Before you upgrade to the Australia release, consult the Service Exchange for Providers (Legacy) - Migration Utility [KB1499823] article in the Now Support Knowledge Base to find out how to migrate your configuration data.

    • Service Exchange version 1.x.x: When upgrading, consult the Upgrade Guide - Service Exchange for Providers and Consumers application (v2.x.x release) [KB1700387] article in the Now Support Knowledge Base to find out how to migrate your Service Exchange applications.
    • Service Exchange version 2.x.x: New entitlements that require the latest compatibility version cannot be activated until both consumers and providers upgrade to Service Exchange version 2.x.x. New entitlements configured with a lower compatibility version can be activated. Older active entitlements continue to work but new ones can’t be activated.
    • When using Service Exchange for Providers and Service Exchange for Consumers in a single instance, you must upgrade both applications simultaneously to the same version to maintain compatibility. If the versions diverge, a scan check will report version mismatches and the Health Dashboard will show a version mismatch issue. After upgrading, run and validate the post‑upgrade scan suite to identify and resolve any post‑upgrade issues.
    • If you have upgraded to Service Exchange version 2.0.55 before upgrading the platform to the Australia release and your instance has Sales and Order Management plug-in version 1.0.4 installed, the new Deny ACLs aren't installed. After upgrading to the Australia release, select Repair to reinstall the Service Exchange application to ensure Deny ACLs are installed.
    • When you install the Service Exchange application, the Service Exchange Global script include is automatically installed or updated on the following platform versions:
      • Yokohama
      • Zurich
      • Australia
    ServiceNow AI Platform core feature

    The dynamic schema application framework was revised in the Zurich release. If you implemented dynamic schema in the Xanadu or Yokohama releases, the application is automatically migrated to a new framework as part of the upgrade to releases starting with the Zurich release. For details on the migration and steps you might need to perform, see the Dynamic Schema Zurich Migration Guide [KB2146133] article in the Now Support Knowledge Base.

    Strengthen your instance security and maintain backward compatibility through enhanced protections for read‑only fields across the ServiceNow AI Platform®. These back-end changes include a new “read_only_option” field with granular control levels, including “strict_read_only” and “client_script_modifiable". If you have custom client scripts that modify read‑only fields on the ServiceNow AI Platform® using g_form.setValue() or g_form.clearValue(), see the Remediation for strict read-only fields preventing client side updates [KB2718122] article in the Now Support Knowledge Base. This article provides additional technical details on how to identify affected fields and adjust their settings. For more information about granular read-only security options, see Configuring read-only security options.

    ServiceNow IDE

    ServiceNow IDE version 3.2.3 is active by default on instances on the Australia release. Update to ServiceNow IDE version 4.0 or later to use the latest features. For information about updating ServiceNow IDE, see Install or update the ServiceNow IDE.

    ServiceNow SDK

    To upgrade to the latest version of the ServiceNow SDK globally or within an application, see Upgrade the ServiceNow SDK.

    ServiceNow SDK version 4.4 supports integration with ServiceNow instances beginning with the Washington DC release.

    On Windows systems, after upgrading to ServiceNow SDK version 4.3 or later, existing stored credentials aren’t supported due to the deprecation of Keytar. Users on Windows systems must add their user credentials again using the now-sdk auth --add command to authenticate with instances. For more information, see Authenticating to a ServiceNow instance with the ServiceNow SDK.
    Remarque :
    For more information about minor releases of the ServiceNow SDK, see the ServiceNow SDK repository on GitHub.
    ServiceNow Studio

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

    ServiceNow Vault
    ServiceNow Vault is a bundle of the following products:
    Source-to-Pay Operations Integrations
    Important :
    Due to a performance issue identified with the upgrade fix script, the sourcing fix script has been modified. This script will no longer execute automatically during the upgrade process. Instead, it is now delivered as an on-demand job. Administrators must manually execute this job outside of business hours after the upgrade is complete.
    Subscription Management

    Subscription Management version 6.1 is active by default on all instances of the Australia release. Update to Subscription Management version 6.1 or later to use the latest features. For more information about updating Subscription Management, see Update an application or plugin.

    Third-party Risk Management

    If you’re a VRM user upgrading to TPRM and upgrading to Australia from an earlier release, you must run each upgrade sequentially to ensure that fix scripts run correctly. For example, you must upgrade from Xanadu to Yokohama, Yokohama to Zurich, and so on. If the scripts don’t run in the correct order, you can get data inconsistencies, broken functionalities, and conflicts.

    After upgrading to version 21.0.x, you can enable the Smart Assessment Engine (SAE) by setting the Smart Assessment Engine enabled (sn_vdr_risk_asmt.sae_enabled) property. After setting this property, Smart Assessment Engine (SAE) becomes the default assessment engine and replaces the legacy experience. The transition isn’t reversible.
    Avertissement :

    Set this property in your non-production instances and conduct thorough testing before changing your production instances. Failure to do so may result in unexpected issues.

    For more information on upgrading from VRM to TPRM and the differences between the Smart and Classic Assessment engines, see Third-party Risk Management upgrade information.

    For existing TPRM customers, after upgrading to version 21.0.3, 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.

    UI Builder

    Saving section for later.

    Workflow Studio

    An earlier version of the save as you go feature was released and withdrawn from the Washington DC release. If you're upgrading from the Washington DC release, you might have manually turned off the save as you go features by setting a system property. To restore the save as you go features, see Restore save as you go functionality.

    Strengthen your instance security and maintain backward compatibility through enhanced protections for read‑only fields across the ServiceNow AI Platform®. These back-end changes include a new “read_only_option” field with granular control levels, including “strict_read_only” and “client_script_modifiable". If you have custom client scripts that modify read‑only fields on the ServiceNow AI Platform® using g_form.setValue() or g_form.clearValue(), see the Remediation for strict read-only fields preventing client side updates [KB2718122] article in the Now Support Knowledge Base. This article provides additional technical details on how to identify affected fields and adjust their settings. For more information about granular read-only security options, see Configuring read-only security options.

    Zero Copy Connector for ERP