- Release Notes
December 2021
You can now use the Automation Cloud Migration Tool to automatically copy your entities from standalone Orchestrator to either Automation Cloud or, as of now, to Automation Suite.
Documentation
The instructions for migrating to Automation Cloud have been updated to account for the user interface changes and remain applicable if you are migrating to Automation Cloud.
For instructions on migrating to Automation Suite, see the new dedicated instructions in Moving your data to Automation Suite.
Data residency for UiPath Automation Cloud allows you to choose in which region we store your tenant data. Today, we have expanded our data residency options to include a new region: Singapore.
When adding a tenant (Enterprise only), you now have a new option in the Tenant Region list: Singapore.
The tenant region dictates where the data for tenant-level services is stored.
For more information about the available tenant regions and the services that are available in each region, including Singapore, see Tenant and service regions for business data.
Commercial offering changes
Our commercial offering for licenses now includes a new SKU called Automation Developer. This new SKU consolidates the capabilities of the RPA Developer, RPA Developer Pro, and Test Developer Pro SKUs, being the bundle with the most capabilities out of the three.
User license changes
For existing customers who have RPA Developer Pro, RPA Developer, or Test Developer Pro user licenses, here's what changes you can see in the product:
- All existing RPA Developer Pro licenses are renamed to Automation Developer.
- Existing RPA Developer licenses remain as they are.
- Existing Test Developer Pro licenses, which were not shown in the product, are now added to your count of Automation Developer licenses.
Converting licenses
How? If you are on version 2020.4 or later, you can request to convert your existing RPA Developer and Test Developer Pro user licenses to Automation Developer user licenses by submitting a licensing ticket to Support.
Why? Converting your existing licenses to Automation Developer licenses lets you take advantage of having fewer license types to manage. Also, in the case of RPA Developer licenses, converting the license lets you upgrade to the full set of capabilities offered by Automation Developer.
Updating license allocation: After the conversion of licenses is complete and your Automation Developer licenses become available in Automation Cloud, you must update the license allocation. For those users or groups who had an RPA Developer license allocated either through a group or directly assigned, allocate an Automation Developer license to them instead.
How to allocate licenses:
- User license management: allocating licenses to users
- Legacy license management: allocating licenses to tenants
To increase performance in retrieving large users or groups lists in the Licenses page, we've made the following UI changes, which apply for tenants with the User License Management model enabled:
- The Users list can't be filtered by the Name column anymore.
- Searching for a user doesn't sort the list anymore.
- Deleted users or groups are identified with an N.A label.
Orphan licenses of deleted users or groups must be removed manually, so they can be reintroduced in the license pool for future reallocation.
