--- sourceDocument: australia Combined Product Files sourceDocumentLink: https://www.servicenow.com/docs/r/australia/delta-zurich-australia Release : - australia ft:locale : - en-US ft:publication_title : - australia Combined Product Files ft:clusterId : - delta3az bundleId : - delta3az --- # Combined RPA Hub release notes for upgrades from Zurich to Australia # Combined RPA Hub release notes for upgrades from Zurich to Australia {#ariaid-title1} Release version: Australia Updated October 8, 2026 ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 12 minutes to read Consolidated page of all release notes for RPA Hub from Zurich to Australia. ## How to use this page To help you prepare for your upgrade, we have combined the cross-family RPA Hub release notes onto one page. Read this summary of the new features, changes, and updated information for your product from Zurich to Australia. Tip: If there were no updates for a release notes section in a certain family release, we included a short note for your reference. For example, if a product did not have any updates in Tokyo, the row says "No updates for this release." ## Important information for upgrading RPA Hub to Australia Before you upgrade to Australia, review these pre- and post-upgrade tasks and complete the tasks as needed. {#dfrn3-rpahub-summary__entry__2} | Release | Release notes | |-|-| | Zurich | Upgrade information : 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](https://www.servicenow.com/docs/access?context=download-installer-rpa&family=zurich&ft:locale=en-US). The following upgrade information is applicable only when you're upgrading from San Diego or Tokyo to Zurich. 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 Zurich. Before upgrading RPA Hub to Zurich, 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://www.servicenow.com/docs/access?context=t_AddAPropertyUsingSysPropsList&family=zurich&ft:locale=en-US). After you upgrade to Zurich, 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 Zurich 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. | | Australia | Upgrade information : 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](https://www.servicenow.com/docs/access?context=download-installer-rpa&family=australia&ft:locale=en-US). 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](https://www.servicenow.com/docs/access?context=t_AddAPropertyUsingSysPropsList&family=australia&ft:locale=en-US). 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\]](https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB1223629) article in the Now Support Knowledge Base. | [ ] ## New features Between your current release family and Australia, new features were introduced for RPA Hub. {#dfrn3-rpahub-summary__entry__8} | Release | Release notes | |-|-| | Zurich | [Try catch component enhancement](https://www.servicenow.com/docs/access?context=use-general-try-catch&family=zurich&ft:locale=en-US) : You can now precisely control the scope of Try-Catch blocks by selecting which actions (components) to include within exception handling and which to manage outside it. This enhancement provides better control over error handling logic and improves workflow reliability. [Role changed for creating, updating, and deleting the Robot License Distribution records](https://www.servicenow.com/docs/access?context=create-lua-record&family=zurich&ft:locale=en-US) : Role for Create, Update, and Delete ACLs in the Robot License Distribution table is changed from admin to sn_rpa_fdn.rpa_admin. [Long term stable models](https://www.servicenow.com/docs/access?context=long-term-stable-models&family=zurich&ft:locale=en-US) : Long term stable (LTS) models are part of Now LLM Service and provide longer model stability windows for regulated industries. These models can integrate with tools to provide governance, monitoring, and compliance controls. [Enhanced ACLs for security measures](https://www.servicenow.com/docs/access?context=installed-with-rpa-hub&family=zurich&ft:locale=en-US) : Enhanced access controls for RPA bot generation skill for Now Assist for RPA Hub in compliance with AI security directives. Access to RPA bot generation skill is now restricted to users with the RPA developer or RPA admin role. These roles contain the RPA Hub Admin user role (sn_nowassist_admin.user). [New third-party AI model provider options available for all AI applications](https://www.servicenow.com/docs/access?context=exploring-large-language-models&family=zurich&ft:locale=en-US) : Google Gemini and AWS Claude are available for RPA bot generation skill in addition to Now LLM Service and Azure OpenAI. [Python connector](https://www.servicenow.com/docs/access?context=python-connector-rpa&family=zurich&ft:locale=en-US) : Execute custom Python scripts or files as part of an automation workflow in the RPA Desktop Design Studio. The connector comprises two methods: * Execute: Runs Python scripts set up in the configuration window. * InvokeScript: Runs Python script on local computers and gets the output. Ensure to install the Scripting plugin from the Plugins Manager as a prerequisite. Along with Python, VB.NET, C#, and Javascript connectors are available with this plugin. [Smart Card authentication](https://www.servicenow.com/docs/access?context=smart-card-il&family=zurich&ft:locale=en-US) : Use a physical smart card instead of a username and password for logging into a Windows machine. You can run unattended automations on the machines that use smart cards for authentication. While configuring a robot credential, you can store the smart card username and password to allow the unattended robot to log in to machines that use smart card. | | Australia | [Try catch component enhancement](https://www.servicenow.com/docs/access?context=use-general-try-catch&family=australia&ft:locale=en-US) : You can now precisely control the scope of Try-Catch blocks by selecting which actions (components) to include within exception handling and which to manage outside it. This enhancement provides better control over error handling logic and improves workflow reliability. | [ ] ## Changes Between your current release family and Australia, some changes were made to existing RPA Hub features. {#dfrn3-rpahub-summary__entry__14} | Release | Release notes | |-|-| | Zurich | No updates for this release. | | Australia | No updates for this release. | [ ] ## Removed Between your current release family and Australia, some RPA Hub features or functionality were removed. {#dfrn3-rpahub-summary__entry__20} | Release | Release notes | |-|-| | Zurich | No updates for this release. | | Australia | No updates for this release. | [ ] ## Deprecations Between your current release family and Australia, some RPA Hub features or functionality were deprecated. {#dfrn3-rpahub-summary__entry__26} | Release | Release notes | |-|-| | Zurich | No updates for this release. | | Australia | No updates for this release. | [ ] ## Activation information Review information on how to activate RPA Hub. {#dfrn3-rpahub-summary__entry__32} | Release | Release notes | |-|-| | Zurich | Activation information : Install RPA Hub by requesting it from the ServiceNow Store. Visit the [ServiceNow Store](https://store.servicenow.com/sn_appstore_store.do#!/store/home) website to view all the available apps and for information about submitting requests to the store. For cumulative release notes information for all released apps, see the [ServiceNow Store version history release notes](https://www.servicenow.com/docs/access?context=sn-store-release-notes&family=zurich&ft:locale=en-US). Important: RPA Hub is available in the ServiceNow Store. For details, see the "Activation information" section of these release notes. | | Australia | Activation information : Install RPA Hub by requesting it from the ServiceNow Store. Visit the [ServiceNow Store](https://store.servicenow.com/sn_appstore_store.do#!/store/home) to view all the available apps, and for information about submitting requests to the store. For cumulative release notes information for all released apps, see the [ServiceNow Store version history release notes](https://www.servicenow.com/docs/access?context=sn-store-release-notes&family=australia&ft:locale=en-US). Important: RPA Hub is available in the ServiceNow Store. For details, see the "Activation information" section of these release notes. | [ ] ## Additional requirements If any additional requirements were introduced or changed for RPA Hub we have noted them here. {#dfrn3-rpahub-summary__entry__38} | Release | Release notes | |-|-| | Zurich | Additional requirements : To use the Unattended Robot application, the hardware requirements for a single robot are as follows:{#dfrn3-rpahub-summary__entry__43} | Resource | Minimum | Recommended | |-|-|-| | CPU | 2 cores of Intel 1.8 GHz 64-bit processor | 4 cores of Intel 2.4 GHz 64-bit processor | | RAM | 4-GB RAM | 8-GB RAM | | Disk space | Minimum 50-GB free disk space after installing the OS, patches, and base software | Minimum 100-GB free disk space after installing the OS, patches, and base software | [Table 1. Hardware requirements for standard robots] To use the Unattended Robot application, the minimum and recommended hardware requirements for a high density robot are multiplied by the number of runtimes. Multiple robots execute jobs concurrently on the same Windows Server machine. For example, with three users concurrently executing jobs, the minimum hardware requirements for a high density robot are: * 6 cores of Intel 1.8GHz 64-bit (6 cores of 1.8GHz 64-bit per runtime). * 12 GB of RAM (4 cores per runtime). To use the Unattended Robot application, the software requirements for a standard robot are: * Operating system: Microsoft Windows 10, Windows Server 2016, Windows Server 2019, Windows Server 2022. * NET framework: Windows 4.7.1 or greater. * DPI scaling setting must be deactivated. To use the Unattended Robot application, the software requirements for a high density robot are: * Operating system: Windows Server 2022. * NET framework: Windows 4.7.1 or greater. * DPI scaling setting must be deactivated. If you are upgrading to Zurich, verify that you have the latest robot MSI from Zurich installed. The older versions of the robots do not work. An unattended robot is mapped to only one machine. This is applicable for standard robot. Virtual Machines (VMs) that are used for the Unattended Robot application must be persistent and constantly on. To use the Attended Robot application, the hardware requirements are:{#dfrn3-rpahub-summary__entry__55} | Resource | Minimum | Recommended | |-|-|-| | CPU | Intel Processor (1vCPU) | Intel Processor (4vCPU) | | RAM | 4-GB RAM | 8-GB RAM | | Disk space | Minimum 20-GB free disk space after installing the OS, patches, and base software | Minimum 50-GB free disk space after installing the OS, patches, and base software | [Table 2. Hardware requirements for Attended Robot] To use the Attended Robot application, the software requirements are: * Operating system: Microsoft Windows 10 or Windows Server 2016 or Windows Server 2019. * NET framework: Windows 4.7.1 or greater. * DPI scaling setting must be deactivated. An attended robot is mapped to only one user. To use the RPA Desktop Design Studio application, the hardware requirements are: {#dfrn3-rpahub-summary__entry__67} | Resource | Minimum | Recommended | |-|-|-| | CPU | Intel Processor (At least, Core i5) | Intel Processor (Core i7). | | RAM | 4-GB RAM | 8-GB RAM | | Disk space | Minimum 20-GB free disk space after installing the OS, patches, and base software | Minimum 50-GB free disk space after installing the OS, patches, and base software | [Table 3. Hardware requirements RPA Desktop Design Studio] To use the RPA Desktop Design Studio application, the software requirements are: * Operating system: Microsoft Windows 10 or Windows Server 2016 or Windows Server 2019. * NET framework: Windows 4.7.1 or greater. * Monitor with 1920x1080p resolution. * DPI scaling setting must be deactivated. | | Australia | Additional requirements : To use the Unattended Robot application, the hardware requirements for a single robot are as follows:{#dfrn3-rpahub-summary__entry__81} | Resource | Minimum | Recommended | |-|-|-| | CPU | 2 cores of Intel 1.8 GHz 64-bit processor | 4 cores of Intel 2.4 GHz 64-bit processor | | RAM | 4-GB RAM | 8-GB RAM | | Disk space | Minimum 50-GB free disk space after installing the OS, patches, and base software | Minimum 100-GB free disk space after installing the OS, patches, and base software | [Table 4. Hardware requirements for standard robots] To use the Unattended Robot application, the minimum and recommended hardware requirements for a high density robot are multiplied by the number of runtimes. Multiple robots execute jobs concurrently on the same Windows Server machine. For example, with three users concurrently executing jobs, the minimum hardware requirements for a high density robot are: * 6 cores of Intel 1.8GHz 64-bit (6 cores of 1.8GHz 64-bit per runtime). * 12 GB of RAM (4 cores per runtime). To use the Unattended Robot application, the software requirements for a standard robot are: * Operating system: Microsoft Windows 10, Windows Server 2016, Windows Server 2019, Windows Server 2022. * NET framework: Windows 4.7.1 or greater. * DPI scaling setting must be deactivated. To use the Unattended Robot application, the software requirements for a high density robot are: * Operating system: Windows Server 2022. * NET framework: Windows 4.7.1 or greater. * DPI scaling setting must be deactivated. If you are upgrading to Australia, verify that you have the latest robot MSI from Australia installed. The older versions of the robots do not work. An unattended robot is mapped to only one machine. This is applicable for standard robot. Virtual Machines (VMs) that are used for the Unattended Robot application must be persistent and constantly on. To use the Attended Robot application, the hardware requirements are:{#dfrn3-rpahub-summary__entry__93} | Resource | Minimum | Recommended | |-|-|-| | CPU | Intel Processor (1vCPU) | Intel Processor (4vCPU) | | RAM | 4-GB RAM | 8-GB RAM | | Disk space | Minimum 20-GB free disk space after installing the OS, patches, and base software | Minimum 50-GB free disk space after installing the OS, patches, and base software | [Table 5. Hardware requirements for Attended Robot] To use the Attended Robot application, the software requirements are: * Operating system: Microsoft Windows 10 or Windows Server 2016 or Windows Server 2019. * NET framework: Windows 4.7.1 or greater. * DPI scaling setting must be deactivated. An attended robot is mapped to only one user. To use the RPA Desktop Design Studio application, the hardware requirements are: {#dfrn3-rpahub-summary__entry__105} | Resource | Minimum | Recommended | |-|-|-| | CPU | Intel Processor (At least, Core i5) | Intel Processor (Core i7). | | RAM | 4-GB RAM | 8-GB RAM | | Disk space | Minimum 20-GB free disk space after installing the OS, patches, and base software | Minimum 50-GB free disk space after installing the OS, patches, and base software | [Table 6. Hardware requirements RPA Desktop Design Studio] To use the RPA Desktop Design Studio application, the software requirements are: * Operating system: Microsoft Windows 10 or Windows Server 2016 or Windows Server 2019. * NET framework: Windows 4.7.1 or greater. * Monitor with 1920x1080p resolution. * DPI scaling setting must be deactivated. | [ ] ## Browser requirements If any specific browser requirements were introduced or changed for RPA Hub we have noted them here. {#dfrn3-rpahub-summary__entry__116} | Release | Release notes | |-|-| | Zurich | Browser requirements : ServiceNow workspaces don't support mobile devices. For more information about the list of supported browsers, see [Browser support](https://www.servicenow.com/docs/access?context=browser-support&family=zurich&ft:locale=en-US). | | Australia | Browser requirements : ServiceNow workspaces don't support mobile devices. For more information about the list of supported browsers, see [Browser support](https://www.servicenow.com/docs/access?context=browser-support&family=australia&ft:locale=en-US). | [ ] ## Accessibility information Review details on accessibility information for RPA Hub, such as specific requirements or compliance levels. {#dfrn3-rpahub-summary__entry__122} | Release | Release notes | |-|-| | Zurich | Accessibility information : Accessibility improvements : Improvements were completed to support accessibility. | | Australia | Accessibility information : Accessibility improvements : Improvements were completed to support accessibility. | [ ] ## Localization information If there are specific localization considerations for RPA Hub we have noted them here. {#dfrn3-rpahub-summary__entry__128} | Release | Release notes | |-|-| | Zurich | Localization information : RPA Hub supports international languages. For more information, see [Internationalization support for RPA Hub](https://www.servicenow.com/docs/access?context=rpa-hub-international-language-support&family=zurich&ft:locale=en-US). | | Australia | Localization information : RPA Hub supports international languages. For more information, see [Internationalization support for RPA Hub](https://www.servicenow.com/docs/access?context=rpa-hub-international-language-support&family=australia&ft:locale=en-US). | [ ] ## Highlight information If there are specific highlight considerations for RPA Hub we have noted them here. {#dfrn3-rpahub-summary__entry__134} | Release | Release notes | |-|-| | Zurich | [Zurich Patch 7](https://www.servicenow.com/docs/access?context=zurich-patch-7&family=zurich&ft:locale=en-US) * You can now selectively define which actions (components) are handled within a Try-Catch block and which are handled outside it. * Versions of model provider are now supported for RPA bot generation skill. [Zurich Patch 4](https://www.servicenow.com/docs/access?context=zurich-patch-4&family=zurich&ft:locale=en-US) * Promote stability with the Long-Term Support (LTS) model for generative AI. * Only the sn_rpa_fdn.rpa_admin role can create, update, and delete records in the Robot License Distribution table. [Zurich Patch 1](https://www.servicenow.com/docs/access?context=zurich-patch-1&family=zurich&ft:locale=en-US) * Use Google Gemini and Anthropic Claude on AWS as AI model providers for RPA bot generation skill in addition to Now LLM Service and Azure OpenAI. * Use the Python connector to execute custom Python scripts or files as part of an automation workflow. * Use a Smart Card authentication for enhanced security. * Enhanced access controls for RPA bot generation skill. See [Robotic Process Automation (RPA) Hub](https://www.servicenow.com/docs/access?context=rpa-main-landing-page&family=zurich&ft:locale=en-US) for more information. | | Australia | * You can now selectively define which actions (components) are handled within a Try-Catch block and which are handled outside it. * Versions of model provider are now supported for RPA bot generation skill. See [Learn about RPA suite of applications](https://www.servicenow.com/docs/access?context=rpa-explore&family=australia&ft:locale=en-US) for more information. | [ ]