{"revision":"c10276e953456835cdbb1f3a60d58ae1980be353","document":{"id":43212,"path":"release-notes/rn-summary-upgrade-info.md","title":"Upgrade information for all Australia features and products","bundle":null,"doc_type":null,"release":"australia","body":"\n# Upgrade information for all Australia features and products\n\nCumulative release notes summary on upgrade information for Australia features and products.\n\nBefore 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.\n\n\n
\n\nApplication or feature\n\n\n\nDetails\n\n
\n\nAI Admin Hub\n\n\n\nIf 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.\n\nIf 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\\]](https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB1637452) article in the Now Support Knowledge Base. Log in to view the article.\n\nThe 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](https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB2718122) article in the Now Support Knowledge Base to identify affected fields and adjust the settings.\n\nThe 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](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/platform-security/granular-admin-roles.md).\n\n
\n\nAI Control Tower\n\n\n\nFor details on upgrading to the redesigned AI Control Tower experience, see the [AI Control Tower Migration \\[KB3144679\\]](https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB3144679) article in Now Support.\n\n
\n\nAI Desktop Actions\n\n\n\nUpgrade 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 for defined desktop actions](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/intelligent-experiences/download-agentic-desktop-installer.md).\n\n
\n\nAdvanced Approval Management\n\n\n\nThe 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.\n\nAssign 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](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/order-management/components-installed-advanced-approval-management-for-sales.md).\n\n
\n\nApplication Manager\n\n\n\nApplication 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](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/release-notes/rn-prepare-landing-page.md).\n\n
\n\nApplication Vulnerability Response\n\n\n\n- 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.\n- For information about the new features of Vulnerability Response, see the [Vulnerability Response release notes](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/release-notes/secops-vuln-resp-rn.md).\n- 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\\]](https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB0856498) article in the Now Support Knowledge Base.\n\nStarting 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\\]](https://support.servicenow.com/kb_view.do?sysparm_article=KB0867184) article in the Now Support Knowledge Base.\n\nServiceNow 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.\n\n
\n\nAsset Audit Response\n\n\n\nThe 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](https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=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](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/platform-administration/read-only-option.md).\n\n
\n\nAutomated Test Framework\n\n\n\nCopy 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.\n\nThe tests can produce a pass result only when you run them on a base system without any customizations. They also require 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](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/application-development/available-quick-start-tests.md).\n\n
\n\nCare Team Operations for Biomed\n\n\n\nThe 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](https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=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](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/platform-administration/read-only-option.md).\n\nIf you have the feature administrator role, you can now complete tasks that were initially reserved for users with the broader administrator role.\n\n
\n\nCare Team Operations for Environmental Services\n\n\n\nIf you have the feature administrator role you can now complete tasks that were initially reserved for users with the broader administrator role.\n\n
\n\nCare Team Operations for Facilities\n\n\n\nIf you have the feature administrator role you can now complete tasks that were initially reserved for users with the broader administrator role.\n\n
\n\nCare Team Operations for Healthcare IT\n\n\n\nThe 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](https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=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](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/platform-administration/read-only-option.md).\n\nIf you have the feature administrator role you can now complete tasks that were initially reserved for users with the broader administrator role.\n\n
\n\nChange Management\n\n\n\nThe ITSM Enhanced Security Features plugin \\(com.snc.itsm.enhanced\\_security\\) is now activated automatically when you upgrade to the Australia release. Previously, the plugin was activated only on new instances. Activating the plugin adds \"deny unless authenticated\" access control list \\(ACL\\) rules to several IT Service Management tables.\n\nTo revert to the pre-upgrade behavior, contact ServiceNow Support for a list of ACLs to deactivate on specific tables. As a last resort, Support can run a script that deactivates all the new ACLs.\n\n
\n\nCloud Cost Management\n\n\n\nThe 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](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/it-asset-management/upgrade-cloud-insights-to-version-3-0.md).\n\n
\n\nConfiguration Compliance\n\n\n\nIf 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.\n\nStarting 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\\]](https://support.servicenow.com/kb_view.do?sysparm_article=KB0867184) article in the Now Support Knowledge Base.\n\nServiceNow 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.\n\nThe Missing Assets \\[sn\\_vul\\_wiz\\_missing\\_asset\\] table used for storing assets imported by the backfill integrations for the [Vulnerability Response Integration with Wiz](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/security-management/vr-wiz-exploring-host-cf.md) 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](https://www.servicenow.com/community/secops-articles/announcement-wiz-integration-with-servicenow-secops/ta-p/3325055).\n\nFor 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\\]](https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB0856498) article in the Now Support Knowledge Base.\n\n
\n\nConfiguration Management Database \\(CMDB\\)\n\n\n\nDue 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\\]](https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB2588894) article in the Now Support Knowledge Base.\n\nIf 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](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/release-notes/cmdb-rn.md).\n\nThe 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](https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=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](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/platform-administration/read-only-option.md).\n\n
\n\nContainer Vulnerability Response\n\n\n\nStarting 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\\]](https://support.servicenow.com/kb_view.do?sysparm_article=KB0867184) article in the Now Support Knowledge Base.\n\nServiceNow 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.\n\nEnhancements 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.\n\nIf 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.\n\nFor 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\\]](https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB0856498) article in the Now Support Knowledge Base.\n\n
\n\nContract Management Pro\n\n\n\nNo upgrade actions are required for this release.\n\n
\n\nCore Business Suite\n\n\n\n- 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](https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=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](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/platform-administration/read-only-option.md).\n- The ServiceNow AI Platform now brings you a new AI experience with three licensing tiers available:\n\n - Foundation: AI basics to deliver insights\n - Advanced: AI to boost productivity across relevant use cases\n - Prime: Act autonomously with all AI assets, and create your own\nFor more information, see [ServiceNow product tiers](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/intelligent-experiences/ai-native-sku-overview.md).\n\n- ServiceNow Otto 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.\n\n
\n\nCustomer Engagement Sequences\n\n\n\nIf 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 \\[Omitted image \"phone-fill-24.svg\"\\] Alt text: 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.\n\n
\n\nDispute Rules Content Pack for Mastercard\n\n\n\nThe 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.\n\n
\n\nEmployee Center\n\n\n\nThe 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](https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=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](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/platform-administration/read-only-option.md).\n\n
\n\nEmployee Center Pro\n\n\n\nThe 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](https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=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](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/platform-administration/read-only-option.md).\n\n
\n\nEmployee Slate\n\n\n\nEmployee Slate requires Zurich Patch 9 or later and an AI assistant \\(Moveworks or Now Assist\\).\n\n
\n\nFlows, subflows, and actions\n\n\n\nAn 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](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/build-workflows/restore-save-as-you-go-functionality.md).\n\nThe 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](https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=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](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/platform-administration/read-only-option.md).\n\n
\n\nGenerative AI Controller\n\n\n\nGenerative 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](https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB1637452) or open a support case.\n\n
\n\nHardware Asset Management\n\n\n\n- 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:\n - sn\\_hamp.ham\\_system\\_admin: Provides access to HAM licensing, HAM Guided Setup, HAM application properties and system properties, and a few tables.\n - sn\\_hamp.ham\\_asn\\_admin: Provides access to the Advanced Shipment Notification \\(ASN\\) feature.\n - asset\\_integration\\_admin: Provides access to Standard hardware Zero touch request and carrier integration features, and shipment tables.\n - asset\\_system\\_admin: Provides access to asset job log, content audit, transfer order, expense management, and model management.\n - asset\\_task\\_admin: Provides access to asset tasks.\n - procurement\\_system\\_admin: Provides access to procurement module, tables, and tasks.\n - contract\\_system\\_admin: Provides access to contract module, tables, and tasks.\n - asset\\_licensing\\_admin: Provides access to the ITAM licensing module.\n - asset\\_recommendation\\_admin: Provides access to recommendation actions.\n- 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](https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=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](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/platform-administration/read-only-option.md).\n- 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**.\n\n
\n\nHealthcare Operations Core\n\n\n\nThe 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](https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=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](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/platform-administration/read-only-option.md).\n\nIf you have the feature administrator role you can now complete tasks that were initially reserved for users with the broader administrator role.\n\n
\n\nHealthcare and Life Sciences Service Management Core\n\n\n\nThe 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](https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=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](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/platform-administration/read-only-option.md).\n\nIf you have the feature administrator role you can now complete tasks that were initially reserved for users with the broader administrator role.\n\n
\n\nImpact\n\n\n\nThe Impact Store Application configuration requires a sequence of tasks in a unified registration process. See [Configuring Impact](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/impact/configuring-impact-platform.md).\n\n
\n\nInstance Data Replication\n\n\n\nLog 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.\n\n
\n\nKey Management\n\n\n\n- In pre-Zurich releases, the GlideEncrypter API used the three-key Triple Data Encryption Standard \\(3DES\\) encryption standard, which [NIST 800-131A Rev 2](https://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-131Ar2.pdf) 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:\n - New Australia instances can’t use GlideEncrypter. All base system scripts have been changed to use alternative encryption processes.\n - 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.\n - Learn more about 3DES deprecation in [KB1704481](https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB1704481).\n\n
\n\nLive Connect\n\n\n\nServiceNow provided customers with a free SOAP-based ODBC client. If you have an active RaptorDB Professional entitlement, you can migrate to the REST-based Live Connect client by completing the required configuration on both the server and client sides. For more information, see [Configuring Live Connect](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/api-reference/web-services/configuring-sql-api.md).\n\n
\n\nMID Server\n\n\n\nFor the latest MID Server system requirements, see [MID Server system requirements](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/servicenow-platform/r_MIDServerSystemRequirements.md). The minimum JRE version supported is 17.0.10 and the recommended version is 21.0.7.\n\nIf you have installed your own JRE, the upgrade process takes the following actions to verify that the MID Server uses a supported JRE:\n\n- 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.\n- If a supported JRE is running on the MID Server host, the upgraded MID Server uses that version.\n\nAll 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](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/servicenow-platform/c_UpgradeAndTestMIDServer.md).\n\nOnly 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](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/servicenow-platform/mid-startup-fails.md) for more information.\n\nFor more information about MID Server upgrades, see the following topics:\n\n- [MID Server pre-upgrade check](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/servicenow-platform/c_UpgradeAndTestMIDServer.md): Describes how the AutoUpgrade monitor tests the ability of the MID Server to upgrade on your system before the actual upgrade.\n- [Upgrade the MID Server manually](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/servicenow-platform/c_UpgradeAndTestMIDServer.md): Describes how to upgrade your MID Servers manually.\n\n
\n\nNow Assist for Employee Center Pro\n\n\n\nNow 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.\n\n
\n\nOperational Resilience\n\n\n\nBeginning with Operational Resilience release 22.0.x, the following scheduled jobs are deactivated for new installations by default:\n\n- **Calculate red flags for CSDM and dependencies**\n- **Update CSDM and other dependencies**\n\nFor existing installations, these jobs retain their current active or inactive state.\n\n
\n\nOperational Sustainability Management \\(formerly Environmental, Social, and Governance\\)\n\n\n\nTo use campaigns, activate the following system properties:\n\n- sn\\_esg.metric\\_campaign: Enables campaigns on the Operational Sustainability Management workspace.\n- sn\\_esg.campaign\\_bulk\\_action\\_enabled: Enables bulk submission, approval, and rejection for campaigns.\n- 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.\n\n
\n\nPerformance Analyzer\n\n\n\nStarting 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.\n\n
\n\nPlatform Analytics experience\n\n\n\nWhen 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.\n\n**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.\n\nAll Core UI public reports are unpublished after upgrading. Report administrators can make these reports available to logged-in users.\n\nAfter upgrading, the Analytics Hub isn't available. Links to the Analytics Hub are redirected to KPI Details.\n\n
\n\nPlaybook\n\n\n\nAfter you upgrade to Australia, update the Workflow Studio application in the ServiceNow Store.\n\n
\n\nProduct Catalog Management and Pricing Management\n\n\n\nPricing 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.\n\nIf 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.\n\n
\n\nPublic Sector Digital Services\n\n\n\nAfter the upgrade, certain public sector menus and menu items in CRM 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**.\n\n
\n\nRPA Hub\n\n\n\nUpgrade any of these currently installed Microsoft Software Installers \\(MSIs\\) by downloading the RPA applications:\n\n- RPA Desktop Design Studio\n- Attended Robot\n- Unattended Robot\n- Unattended Robot Login Agent\n\nFor more information, see [Download the RPA applications from RPA Hub](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/integrate-applications/download-installer-rpa.md).\n\nThe following upgrade information is applicable only when you’re upgrading from San Diego or Tokyo to Australia.\n\nBased 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.\n\nBefore 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](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/platform-administration/t_AddAPropertyUsingSysPropsList.md).\n\nAfter you upgrade to Australia, the bot process definitions change to the new structure, which is the bot process configuration.\n\nAlthough 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\\]](https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB1223629) article in the Now Support Knowledge Base.\n\n
\n\nReleaseOps\n\n\n\nIf you have customized the ReleaseOps sample playbooks, the runbook task playbook activity will not automatically populate when you upgrade to Australia.\n\n
\n\nService Exchange \\(formerly Service Bridge\\)\n\n\n\n**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.\n\n- Service Exchange version 2.x.x, which was first released with the Xanadu release, doesn’t support migration of Service Exchange \\(Legacy\\) versions.\n\nService Exchange \\(Legacy\\) version: Before you upgrade to the Australia release, consult the [Service Exchange for Providers \\(Legacy\\) - Migration Utility \\[KB1499823\\]](https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB1499823) article in the Now Support Knowledge Base to find out how to migrate your configuration data.\n\n- Service Exchange version 1.x.x: When upgrading, consult the [Upgrade Guide - Service Exchange for Providers and Consumers application \\(v2.x.x release\\) \\[KB1700387\\]](https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB1700387) article in the Now Support Knowledge Base to find out how to migrate your Service Exchange applications.\n- 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.\n- 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.\n- 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.\n- 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](https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB2944968).\n- When you install the Service Exchange application, the Service Exchange Global script include is automatically installed or updated on the following platform versions:\n - Yokohama\n - Zurich\n - Australia\n\n
\n\nServiceNow AI Platform core feature\n\n\n\nThe 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\\]](https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB2146133) article in the Now Support Knowledge Base.\n\nThe 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](https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=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](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/platform-administration/read-only-option.md).\n\n
\n\nServiceNow IDE\n\n\n\nServiceNow 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](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/application-development/install-servicenow-ide.md).\n\n
\n\nServiceNow Otto for Configuration Management Database \\(CMDB\\)\n\n\n\nTo 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 .\n\n
\n\nServiceNow Otto for Creator\n\n\n\n[Australia Early Availability](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/release-notes/australia-all-other-fixes.md)\n\n- 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.\n\n
\n\nServiceNow Otto for IT Service Management \\(ITSM\\)\n\n\n\nTo 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.\n\n1. Go to **Admin** > **Now Assist admin**.\n2. Select **Now Assist Skills**.\n3. Select **Platform**.\n4. Select **Knowledge**.\n5. Make sure the knowledge content recommendation skill is active.\n\nThe 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](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/release-notes/australia-patch-1.md), if you have the \\[DEPRECATED\\] incident assist skill activated, consider deactivating it to avoid redundancy. For more information, see [Incident assist skill](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/it-service-management/now-assist-itsm-incident-assist.md).\n\nStarting with the [Australia Patch 2](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/release-notes/australia-patch-2.md), the Incident assist skill has been deprecated, moved to the **Archive** section, and is no longer available for use.\n\n
\n\nServiceNow Otto for Software Asset Management \\(SAM\\)\n\n\n\nTBD.\n\n
\n\nServiceNow SDK\n\n\n\nTo upgrade to the latest version of the ServiceNow SDK globally or within an application, see [Upgrade the ServiceNow SDK](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/application-development/upgrade-servicenow-sdk.md).\n\nServiceNow SDK version 4.4 supports integration with ServiceNow instances beginning with the Washington DC release.\n\nOn 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](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/application-development/authenticate-instance-now-sdk.md).\n\n**Important:** For minor releases of the ServiceNow SDK, see the [ServiceNow SDK release notes](https://github.com/ServiceNow/sdk/releases) on GitHub.\n\n
\n\nServiceNow Studio\n\n\n\nServiceNow Studio no longer has to be downloaded from the ServiceNow Store. It’s available on the ServiceNow AI Platform by default.\n\n
\n\nServiceNow Vault\n\n\n\nServiceNow Vault is a bundle of the following products:\n\n- [ServiceNow Vault](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/platform-security/servicenow-vault-landing.md)\n- [Data Discovery](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/platform-security/data-discovery-landing.md)\n- [Data Privacy](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/platform-security/data-privacy-landing.md)\n- [Zero Trust Access \\(ZTA\\)](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/platform-security/session-access.md)\n- [Field Encryption](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/platform-security/field-encryption.md)\n- [Code Signing](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/platform-security/code-signing-landing.md)\n- [Log Export Service \\(LES\\)](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/platform-security/les-intro.md)\n\n
\n\nSource-to-Pay Operations Integrations\n\n\n\n**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.\n\n
\n\nSubscription Management\n\n\n\nSubscription Management version 6.1 is active by default on instances of the Australia release. For more information about updating Subscription Management, see [Update an application or plugin](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/platform-administration/update-application-app-mgr.md).\n\n
\n\nThird-party Risk Management\n\n\n\nIf 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.\n\nAfter 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.\n\n**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.\n\nFor 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](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/release-notes/grc-tprm-rn.md).\n\nFor 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.\n\nAfter 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.\n\n
\n\nUI Builder\n\n\n\nSaving section for later.\n\n
\n\nUnified Security Exposure Management \\(USEM\\)\n\n\n\nStarting 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\\]](https://support.servicenow.com/kb_view.do?sysparm_article=KB0867184) article in the Now Support Knowledge Base.\n\nServiceNow 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.\n\nTo access the new AI native experience in the Unified Security Exposure Management \\(USEM\\) workspace, you must upgrade to the Australia release.\n\n- **[ServiceNow product tiers](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/intelligent-experiences/ai-native-sku-overview.md)**\n\nThe ServiceNow AI Platform now brings you a new AI experience with three licensing tiers available:\n\n - Foundation: AI basics to deliver insights\n - Advanced: AI to boost productivity across relevant use cases\n - Prime: Act autonomously with all AI assets, and create your own\nDepending on your license, you will have access to certain application features, generative AI skills, agentic workflows, and AI agents.\n\n\nUnified 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\\]](https://support.servicenow.com/kb?sys_kb_id=8652717893a8ba94f538fb2d6cba1078&id=kb_article_view) 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\\)](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/security-management/migrating-to-usem.md) and [Migrate to Unified Security Exposure Management \\(USEM\\) from Vulnerability Response](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/security-management/migrate-to-usem.md).\n\n
\n\nVulnerability Response\n\n\n\nStarting 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\\]](https://support.servicenow.com/kb_view.do?sysparm_article=KB0867184) article in the Now Support Knowledge Base.\n\nServiceNow 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.\n\nIf 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.\n\nFor 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\\]](https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB0856498) article in the Now Support Knowledge Base\n\nStarting with the Australia release, the Patch update and Collection fields on patch deployment records for the Microsoft SCCM and HCL BigFix Patch Orchestration integrations are deprecated in favor of new multi-value Patch updates and Collections fields, which support deploying more than one patch to more than one collection or computer group in a single deployment. Existing values in the deprecated fields are automatically migrated to the new fields during the upgrade. The deprecated fields remain on the form but are no longer used to create new deployments.\n\n
**Parent Topic:**[Release notes summaries for Australia features](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/release-notes/release-notes-summaries.md)\n\n"}}