Combined RPA Hub release notes for upgrades from Zurich to Australia

  • Release version: Australia
  • Updated May 4, 2026
  • 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.

    Release Release notes

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

    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] article in the Now Support Knowledge Base.

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

    New features

    Between your current release family and Australia, new features were introduced for RPA Hub.

    Release Release notes

    Zurich
    Zurich Patch 7
    Try catch component enhancement
    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.
    Zurich Patch 4
    Role changed for creating, updating, and deleting the Robot License Distribution records
    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
    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.
    Zurich Patch 1
    New third-party AI model provider options available for all Now Assist applications
    Google Gemini and AWS Claude are available for RPA bot generation skill in addition to Now LLM Service and Azure OpenAI.
    Python connector
    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
    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.

    Enhanced ACLs for security measures
    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).

    Australia
    Try catch component enhancement
    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.

    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.

    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.

    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.

    Release Release notes

    Zurich

    Install RPA Hub by requesting it from the ServiceNow Store. Visit the ServiceNow Store 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.

    Australia

    Install RPA Hub by requesting it from the ServiceNow Store. Visit the ServiceNow Store 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.

    Additional requirements

    If any additional requirements were introduced or changed for RPA Hub we have noted them here.

    Release Release notes

    Zurich
    To use the Unattended Robot application, the hardware requirements for a single robot are as follows:
    Table 1. Hardware requirements for standard robots
    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
    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:
    Table 2. Hardware requirements for Attended Robot
    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
    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:
    Table 3. Hardware requirements RPA Desktop Design Studio
    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
    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
    To use the Unattended Robot application, the hardware requirements for a single robot are as follows:
    Table 4. Hardware requirements for standard robots
    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
    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:
    Table 5. Hardware requirements for Attended Robot
    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
    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:
    Table 6. Hardware requirements RPA Desktop Design Studio
    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
    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.

    Release Release notes

    Zurich

    ServiceNow workspaces don’t support mobile devices. For more information about the list of supported browsers, see Browser support.

    Australia

    ServiceNow workspaces don’t support mobile devices. For more information about the list of supported browsers, see Browser support.

    Accessibility information

    Review details on accessibility information for RPA Hub, such as specific requirements or compliance levels.

    Release Release notes

    Zurich
    Accessibility improvements
    Accessibility improvements were completed to support WCAG 2.1 Level AA conformance.

    Australia
    Accessibility improvements
    Accessibility improvements were completed to support WCAG 2.1 Level AA conformance.

    Localization information

    If there are specific localization considerations for RPA Hub we have noted them here.

    Release Release notes

    Zurich

    RPA Hub supports international languages. For more information, see Internationalization support for RPA Hub.

    Australia

    RPA Hub supports international languages. For more information, see Internationalization support for RPA Hub.

    Highlight information

    If there are specific highlight considerations for RPA Hub we have noted them here.

    Release Release notes

    Zurich
    Zurich Patch 7
    • 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
    • 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
    • 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 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 for more information.