Upgrade information for all Australia features and products

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	For details on upgrading to the redesigned AI Control Tower experience, see the AI Control Tower Migration [KB3144679] article in Now Support.
AI Desktop Actions	Upgrade the currently installed AI Desktop Actions Software Installers (MSIs) by downloading and installing the newer version of the application. Make sure to close the current execution and close the desktop app before staring the installation for upgrade. For more information, see Download AI Desktop Actions installer.
Advanced Approval Management	The default value for the Rule order field in a chain is now 10. If you have rule orders in chains configured with different order values, review and update them as needed to align with the new default. Assign the approval_request_submitter role to requesters who submit approval requests only and don't have access to the full advanced approval workflow functionality and interface. Users with this role can't recall recall or update approval requests. For more information, see Components installed with Advanced Approval Management.
Application Manager	Application Manager is active by default on instances on the Australia release. Upgrade your instance to Australia patch 4 or later to use the latest features. For information about upgrading your ServiceNow AI Platform instance, see Prepare your upgrade.
Application Vulnerability Response	If you are currently using Application Vulnerability Response, and you do not intend to upgrade to Unified Security Exposure Management (USEM), install a version below v30.x of Application Vulnerability Response and for upgrades to supported third-party integration applications. For information about the new features of Vulnerability Response, see the 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 Australia release, see the Vulnerability Response Compatibility Matrix and Release Schema Changes [KB0856498] article in the Now Support Knowledge Base. Starting with Australia Patch 5, Now Assist for Vulnerability Response is being prepared for future deprecation. It will be hidden and no longer installed on new instances but will continue to be supported. For details, see the Deprecation Process [KB0867184] article in the Now Support Knowledge Base. ServiceNow Otto® is the new AI experience brand. This change is reflected in the name of ServiceNow products, including the Now Assist for Vulnerability Response product name, which will be replaced with ServiceNow Otto for Unified Security Exposure Management. Your product entitlements remain unchanged. Check your entitlements to determine your access to specific features.
Asset Audit Response	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_only” and “client_script_modifiable". The changes occur in the back end and maintain backward‑compatible behavior. This update helps strengthen your instance security while preserving the flexibility you need. Refer to KB2718122 for 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.
Care Team Operations for Biomed	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_only” and “client_script_modifiable". The changes occur in the back end and maintain backward‑compatible behavior. This update helps strengthen your instance security while preserving the flexibility you need. Refer to KB2718122 for 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	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_only” and “client_script_modifiable". The changes occur in the back end and maintain backward‑compatible behavior. This update helps strengthen your instance security while preserving the flexibility you need. Refer to KB2718122 for 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 Compliance	If you're currently using Configuration Compliance, and you don't intend to upgrade to Unified Security Exposure Management (USEM), install a version previous v30.x of Configuration Compliance and for upgrades to supported third-party integration applications. Starting with Australia Patch 5, Now Assist for Vulnerability Response is being prepared for future deprecation. It will be hidden and no longer installed on new instances but will continue to be supported. For details, see the Deprecation Process [KB0867184] article in the Now Support Knowledge Base. ServiceNow Otto® is the new AI experience brand. This change is reflected in the name of ServiceNow products, including the Now Assist for Vulnerability Response product name, which will be replaced with ServiceNow Otto for Unified Security Exposure Management. Your product entitlements remain unchanged. Check your entitlements to determine your access to specific features. The Missing Assets [sn_vul_wiz_missing_asset] table used for storing assets imported by the backfill integrations for the Vulnerability Response Integration with Wiz is deprecated. If you're currently using the Vulnerability Response with Wiz integrations, after updating to version 1.1, backdate any of your existing Wiz primary integrations by three days and run them. See more information about the Wiz integration at SecOps articles on the Security Operations Community. For more information about the released versions of the Vulnerability Response application and the third party and ServiceNow applications that are compatible with the Australia release, see the Vulnerability Response Compatibility Matrix and Release Schema Changes [KB0856498] article in the Now Support Knowledge Base.
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. 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_only” and “client_script_modifiable". The changes occur in the back end and maintain backward‑compatible behavior. This update helps strengthen your instance security while preserving the flexibility you need. Refer to KB2718122 for 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.
Container Vulnerability Response	Starting with Australia Patch 5, Now Assist for Vulnerability Response is being prepared for future deprecation. It will be hidden and no longer installed on new instances but will continue to be supported. For details, see the Deprecation Process [KB0867184] article in the Now Support Knowledge Base. ServiceNow Otto® is the new AI experience brand. This change is reflected in the name of ServiceNow products, including the Now Assist for Vulnerability Response product name, which will be replaced with ServiceNow Otto for Unified Security Exposure Management. Your product entitlements remain unchanged. Check your entitlements to determine your access to specific features. Enhancements to Container Vulnerability Response permit you to see enriched container vulnerability data on data imports from your third-party scanners. After you upgrade, perform a full import to view the features on discovered container image, container image finding, and container vulnerable item records that are described in the following New in the Australia release section. If you're currently using Container Vulnerability Response, and you do not intend to upgrade to Unified Security Exposure Management (USEM), install a version below v30.x of Container Vulnerability Response and for upgrades to supported third-party integration applications. For more information about the released versions of the Container Vulnerability Response application as well as the third-party and ServiceNow applications that are compatible with the Australia release, see the Vulnerability Response Compatibility Matrix and Release Schema Changes [KB0856498] article in the Now Support Knowledge Base.
Contract Management Pro	No upgrade actions are required for this release.
Core Business Suite	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_only” and “client_script_modifiable". The changes occur in the back end and maintain backward‑compatible behavior. This update helps strengthen your instance security while preserving the flexibility you need. Refer to KB2718122 for 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. The ServiceNow AI Platform now brings you a new AI experience with three licensing tiers available: Foundation: AI basics to deliver insights Advanced: AI to boost productivity across relevant use cases Prime: Act autonomously with all AI assets, and create your own For more information, see ServiceNow product tiers. Now Assist introduced AI on the platform. As that experience has evolved, there's a new name for the experience. ServiceNow Otto® is the conversational AI platform integrated into ServiceNow workflows. It provides agentic capabilities, supports multimodal interactions across web, mobile, and messaging channels, and enables autonomous orchestration for cross-system workflows.
Customer Engagement Sequences	If you configured sequences with the Schedule call activity on a release before Zurich, the activity is now labeled Schedule call - Deprecated in the activity picker in Workflow Studio. Existing sequences continue to work, but the Call icon doesn't appear on the Callback number field on the Sequence Steps page during runtime. To enable the click-to-call capability, update the Customer Engagement Sequences application to use the new Schedule call activity.
Dispute Rules Content Pack for Mastercard	The Australia release adds new data fields to the Authorization and Financial Transaction tables to support the new eligibility rules. The transactionAmountLocal field already exists in the Financial Transaction table but is being extended to the Financial Transaction Authorization table in this release. No other pre-existing fields are affected. After upgrading, confirm that the new fields are available and populated on your instance.
Employee Center	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_only” and “client_script_modifiable". The changes occur in the back end and maintain backward‑compatible behavior. This update helps strengthen your instance security while preserving the flexibility you need. Refer to KB2718122 for 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	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_only” and “client_script_modifiable". The changes occur in the back end and maintain backward‑compatible behavior. This update helps strengthen your instance security while preserving the flexibility you need. Refer to KB2718122 for 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.
Flows, subflows, and actions	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. 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_only” and “client_script_modifiable". The changes occur in the back end and maintain backward‑compatible behavior. This update helps strengthen your instance security while preserving the flexibility you need. Refer to KB2718122 for 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. The Australia release restricts the default flow reporting level available on production instances to the basic reporting level. While you can't set all flows to the full reporting level, you can still set individual flows to the full reporting level. For more information about setting a flow's reporting level, see Activate flow reporting.
Generative AI Controller	Generative AI Controller is installed or updated when you install or update a Now Assist application. If you have issues installing or updating applications, see this knowledge article or open a support case.
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. 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_only” and “client_script_modifiable". The changes occur in the back end and maintain backward‑compatible behavior. This update helps strengthen your instance security while preserving the flexibility you need. Refer to KB2718122 for 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. A new system property, sn_itam_restrict_asset_read, introduced in Australia Patch 5, controls read access to the Asset [alm_asset] table and its child tables for users with only the snc_internal role. When set to true, these users can only read asset records assigned to them or where they are referenced in fields such as Reserved for, Managed by, or Owned by. Users with any additional role retain full read access. By default, this property is set to false.
Healthcare Operations Core	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_only” and “client_script_modifiable". The changes occur in the back end and maintain backward‑compatible behavior. This update helps strengthen your instance security while preserving the flexibility you need. Refer to KB2718122 for 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	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_only” and “client_script_modifiable". The changes occur in the back end and maintain backward‑compatible behavior. This update helps strengthen your instance security while preserving the flexibility you need. Refer to KB2718122 for 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 Configuring Impact.
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.
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.
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: 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 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.
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.
Operational Sustainability Management (formerly Environmental, Social, and Governance)	To use campaigns, activate the following system properties: sn_esg.metric_campaign: Enables campaigns on the Operational Sustainability Management workspace. sn_esg.campaign_bulk_action_enabled: Enables bulk submission, approval, and rejection for campaigns. sn_esg.metric_approval: Sets the approval mode for campaigns. Set the value to Simple for a single data owner and approver, or Advanced for multi-level approval chains.
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	When upgrading, all Core UI reports and dashboards are identified as such in the library under the UI version column. Users can edit these legacy artifacts in the Report Builder and Dashboard Builder applications. Note: Users who have not migrated their instances to Platform Analytics experience have the option to create dashboards and data visualizations in either Core UI or Next Experience. Next Experience is recommended. All Core UI public reports are unpublished after upgrading. Report administrators can make these reports available to logged-in users. 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 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 a new version of Pricing Management, the default pricing plan is in a Retired state. Determine whether you want to publish the default pricing plan for use or customize it. If you've been using AI Search for product catalog in a previous release, after upgrading to Product Catalog Management Core v.19.0.0 or higher, republish the stop word dictionary, search profiles, and index tables used by AI Search. To republish, run the Scheduled job to publish stop words dictionary, search profiles and index tables. Republishing includes the changes for multilingual support of product catalog entities introduced in the v.19.0.0 release.
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	If you have customized the ReleaseOps sample playbooks, the runbook task playbook activity will not automatically populate when you upgrade to Australia.
SQL API	ServiceNow provided customers with a free SOAP‑based ODBC client. If you have an active RaptorDB Professional entitlement, you can migrate to the REST‑based SQL API client by completing the required configuration on both the server and client sides. For more information, see Configuring SQL API.
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 Customer Relationship Management 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. If you're upgrading Service Exchange to version 2.3.x, migrate the OAuth grant type on all existing connections from authorization code to client credentials to avoid a "User Not Authenticated" error. Complete this migration on both the provider and consumer instances after the upgrade and before using the connection. For details, see KB2944968. 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. 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_only” and “client_script_modifiable". The changes occur in the back end and maintain backward‑compatible behavior. This update helps strengthen your instance security while preserving the flexibility you need. Refer to KB2718122 for 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 Otto	If you customized actions on the user interface or other items that are associated with ServiceNow Otto 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 ServiceNow Otto product, see the Issues and mitigation for Now Assist (generative AI) Applications and Plugin updates [KB1637452] article in the Now Support Knowledge Base. 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_only and 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 Granular admin roles.
ServiceNow Otto 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.
ServiceNow Otto for Creator	Australia Early Availability To upgrade the Build Agent application, upgrade the ServiceNow Otto 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.
ServiceNow Otto for IT Service Management (ITSM)	To use the Knowledge Article Advanced Editor page in the generate a knowledge article skill, you must activate the knowledge content recommendation skill. Follow these steps to activate the skill. Go to Admin > Now Assist admin. Select Now Assist Skills. Select Platform. Select Knowledge. Make sure the knowledge content recommendation skill is active. The incident assist agentic workflow is active by default and includes all the capabilities of the [DEPRECATED] incident assist skill, with enhancements. When you upgrade to Australia Patch 1, if you have the [DEPRECATED] incident assist skill activated, consider deactivating it to avoid redundancy. For more information, see Incident assist skill. Starting with the Australia Patch 2, the Incident assist skill has been deprecated, moved to the Archive section, and is no longer available for use.
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. Important: For minor releases of the ServiceNow SDK, see the ServiceNow SDK release notes 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: ServiceNow Vault Data Discovery Data Privacy Zero Trust Access (ZTA) Field Encryption Code Signing Log Export Service (LES)
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) is set to the default assessment engine and replaces the legacy experience. The transition is irreversible. Warning: Set this property in your non-production instances and conduct thorough testing before changing your production instances. Failure to do so can 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. Update any customizations that reference the Industry field to use tprm_industry. After verifying the migration and updating customizations, you can drop the Industry column. After upgrading to version 22.3.3, the grc_business_user and grc_reader roles are no longer directly inherited by TPRM roles. During upgrade, most users are automatically migrated to new feature‑specific roles. Users with custom role combinations may not be migrated automatically and require manual review before the grace period ends.
UI Builder	Saving section for later.
Unified Security Exposure Management (USEM)	Starting with Australia Patch 5, Now Assist for Vulnerability Response is being prepared for future deprecation. It will be hidden and no longer installed on new instances but will continue to be supported. For details, see the Deprecation Process [KB0867184] article in the Now Support Knowledge Base. ServiceNow Otto® is the new AI experience brand. This change is reflected in the name of ServiceNow products, including the Now Assist for Vulnerability Response product name, which will be replaced with ServiceNow Otto for Unified Security Exposure Management. Your product entitlements remain unchanged. Check your entitlements to determine your access to specific features. To access the new AI native experience in the Unified Security Exposure Management (USEM) workspace, you must upgrade to the Australia release. ServiceNow product tiers The ServiceNow AI Platform now brings you a new AI experience with three licensing tiers available: Foundation: AI basics to deliver insights Advanced: AI to boost productivity across relevant use cases Prime: Act autonomously with all AI assets, and create your own Depending on your license, you will have access to certain application features, generative AI skills, agentic workflows, and AI agents. Unified Security Exposure Management is available to all customers who are entitled to Vulnerability Response. Migrating to USEM is a major upgrade that introduces a unified architecture for improved performance, scalability, and streamlined workflows. Before upgrading, leverage the Migration assistant for Unified Security Exposure Management that is available as an update set. See the Migration Guidance to Unified Security Exposure Management [KB2556844] Knowledge Base article for more information. This tool provides a guided experience for plugin installation, data mapping, rule migration, and post-migration validation, reducing risk and manual effort. Ensure that all integrations and workflows are reviewed for compatibility before initiating migration. For more information, see Migrating from Vulnerability Response to Unified Security Exposure Management (USEM) and Migrate to Unified Security Exposure Management (USEM) from Vulnerability Response.
Vulnerability Response	Starting with Australia Patch 5, Now Assist for Vulnerability Response is being prepared for future deprecation. It will be hidden and no longer installed on new instances but will continue to be supported. For details, see the Deprecation Process [KB0867184] article in the Now Support Knowledge Base. ServiceNow Otto® is the new AI experience brand. This change is reflected in the name of ServiceNow products, including the Now Assist for Vulnerability Response product name, which will be replaced with ServiceNow Otto for Unified Security Exposure Management. Your product entitlements remain unchanged. Check your entitlements to determine your access to specific features. If you're currently using Vulnerability Response, and you do not intend to upgrade to Unified Security Exposure Management (USEM), install a version below v30.x of Vulnerability Response and for upgrades to supported third-party integration applications. 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 Australia release, see the Vulnerability Response Compatibility Matrix and Release Schema Changes [KB0856498] article in the Now Support Knowledge Base