--- sourceDocument: brazil Combined Product Files sourceDocumentLink: https://www.servicenow.com/docs/r/delta-australia-brazil Release : - brazil ft:locale : - en-US ft:publication_title : - brazil Combined Product Files ft:clusterId : - delta3ba bundleId : - delta3ba --- # Combined RPA Hub release notes for upgrades from Australia to Brazil # Combined RPA Hub release notes for upgrades from Australia to Brazil {#ariaid-title1} Release version: Brazil Updated October 8, 2026 ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 6 minutes to read Summarize ![AI sparkle icon](https://servicenow.com/docs/portal-asset/ai-sparkle-icon) Summarized using AI This content was generated using new OpenAI-powered functionality. Results are provided on an as is basis and are not guaranteed to be accurate or complete. ## Summary of Combined RPA Hub release notes for upgrades from Australia to Brazil This consolidated document provides essential information for ServiceNow customers upgrading the RPA Hub from the Australia release family to Brazil. It summarizes critical upgrade tasks, new features, changes, activation procedures, hardware and software requirements, and other considerations to ensure a smooth transition and optimal use of RPA Hub capabilities. Show full answer Show less ## Important Upgrade Information Before upgrading to Brazil, review and complete all pre- and post-upgrade tasks. Notably, upgrades from Tokyo or earlier to Australia require setting the system property **glide.rollback.blacklist.TableParentChange.change** to *false* to prevent upgrade issues related to table extensions. This property must be added manually if missing. After upgrading to Australia, bot process definitions change to a new configuration structure, improving management but requiring attention to system properties. Brazil release itself has no additional updates affecting upgrade procedures. ## New Features and Enhancements * **Australia release:** Enhanced Try-Catch component allows precise control over which workflow actions are included within exception handling blocks, improving error handling granularity and workflow reliability. * **Brazil release:** No new features introduced. ## Changes, Removals, and Deprecations There are no reported changes, removals, or deprecations between Australia and Brazil releases. ## Activation and Installation RPA Hub is available via the ServiceNow Store. Customers should request installation through the Store and can find cumulative release notes and version histories there for reference. ## Hardware and Software Requirements **Australia release requirements apply:** * **Unattended Robot:** Minimum 2-core Intel 1.8 GHz CPU, 4 GB RAM, 50 GB free disk space; recommended specs are 4-core Intel 2.4 GHz CPU, 8 GB RAM, 100 GB disk space. High density robots scale requirements by concurrent runtimes. * **Attended Robot:** Minimum Intel 1vCPU, 4 GB RAM, 20 GB disk space; recommended Intel 4vCPU, 8 GB RAM, 50 GB disk space. * **RPA Desktop Design Studio:** Minimum Intel Core i5, 4 GB RAM, 20 GB disk space; recommended Core i7, 8 GB RAM, 50 GB disk space. Requires 1920x1080 resolution monitor. * **Software:** Supported OS includes Windows 10 and Windows Server 2016/2019/2022 (for applicable components). .NET Framework 4.7.1 or greater is required. DPI scaling must be disabled. * Unattended robots must run on persistent, always-on virtual machines and map to a single machine; attended robots map to a single user. * Ensure robot MSI installers are updated to the latest Australia release versions when upgrading. ## Browser and Accessibility Considerations * ServiceNow workspaces do not support mobile devices. * Accessibility improvements have been made in Australia release to enhance usability and compliance. ## Localization and Internationalization RPA Hub supports multiple international languages as part of its localization capabilities. ## Summary Upgrading from the Australia to Brazil release family of RPA Hub involves important preparation steps, particularly related to system properties and hardware/software compatibility established in Australia. The Brazil release itself introduces no new features or changes. Customers should focus on ensuring system properties are correctly configured, use updated robot MSI installers, and meet hardware and software prerequisites to maintain reliable RPA operations. The enhanced Try-Catch control introduced in Australia improves workflow error handling. Activation through the ServiceNow Store remains the standard process. Consolidated page of all release notes for RPA Hub from Australia to Brazil. ## 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 Australia to Brazil. 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 Brazil Before you upgrade to Brazil, review these pre- and post-upgrade tasks and complete the tasks as needed. {#dfrn3-rpahub-summary__entry__2} | Release | Release notes | |-|-| | 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. | | Brazil | No updates for this release. | [ ] ## New features Between your current release family and Brazil, new features were introduced for RPA Hub. {#dfrn3-rpahub-summary__entry__8} | Release | Release notes | |-|-| | 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. | | Brazil | No updates for this release. | [ ] ## Changes Between your current release family and Brazil, some changes were made to existing RPA Hub features. {#dfrn3-rpahub-summary__entry__14} | Release | Release notes | |-|-| | Australia | No updates for this release. | | Brazil | No updates for this release. | [ ] ## Removed Between your current release family and Brazil, some RPA Hub features or functionality were removed. {#dfrn3-rpahub-summary__entry__20} | Release | Release notes | |-|-| | Australia | No updates for this release. | | Brazil | No updates for this release. | [ ] ## Deprecations Between your current release family and Brazil, some RPA Hub features or functionality were deprecated. {#dfrn3-rpahub-summary__entry__26} | Release | Release notes | |-|-| | Australia | No updates for this release. | | Brazil | No updates for this release. | [ ] ## Activation information Review information on how to activate RPA Hub. {#dfrn3-rpahub-summary__entry__32} | Release | 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. | | Brazil | No updates for this release. | [ ] ## 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 | |-|-| | Australia | 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 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__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. | | Brazil | No updates for this release. | [ ] ## Browser requirements If any specific browser requirements were introduced or changed for RPA Hub we have noted them here. {#dfrn3-rpahub-summary__entry__80} | Release | Release notes | |-|-| | 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). | | Brazil | No updates for this release. | [ ] ## Accessibility information Review details on accessibility information for RPA Hub, such as specific requirements or compliance levels. {#dfrn3-rpahub-summary__entry__86} | Release | Release notes | |-|-| | Australia | Accessibility information : Accessibility improvements : Improvements were completed to support accessibility. | | Brazil | No updates for this release. | [ ] ## Localization information If there are specific localization considerations for RPA Hub we have noted them here. {#dfrn3-rpahub-summary__entry__92} | Release | Release notes | |-|-| | 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). | | Brazil | No updates for this release. | [ ] ## Highlight information If there are specific highlight considerations for RPA Hub we have noted them here. {#dfrn3-rpahub-summary__entry__98} | Release | Release notes | |-|-| | 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. | | Brazil | No updates for this release. | [ ]