- Release notes
November 2022
The VPN Gateway feature for cloud robots is now generally available.
Added 10 January 2023
- A connected queue trigger was not marked as a missing requirement after you deleted the associated queue.
Test Suite entities are now included in the migration from classic to modern folders, along with the rest of the Orchestrator resources.
We are now automatically disabling Cloud Robot - VM machines that are not licensed. This can happen either when your licensing plan expires, or if you do not have sufficient robot units for all of your machines.
If you are in this situation, a notification banner is displayed and you enter a 14-day grace period (Enterprise), or a 3-day grace period (Pro) before machines are disabled.
Acquiring or renewing the necessary licenses (licensing plan and robot units) before the grace period ends prevents machines from being disabled.
If you find that you have disabled machines, see the Disabled machines FAQs.
Escape the burden of creating and managing virtual machines for your Automation Cloud robots. We introduced the automatic option that allows us to create and manage virtual machine pools on your behalf. Just input the maximum number of machines the pool should contain, and make sure you have enough robot units for the machines to run. For more details, see the relevant topics in this page.
Adjust your robot units consumption by selecting an availability profile for your machine. By choosing to automatically shut down your machines after an idle duration, you can recover and reuse their corresponding robot units. You also have the option to keep your machines always on. Selecting another machine availability profile than the default one, extra robot units are consumed.
You can now store your Orchestrator credentials in AWS Secrets Manager. For details about the newly added credential store, see AWS Secrets Manager integration.
Administrators can now configure fine-grained tenant or folder permissions for confidential apps by assigning them to folders or tenants in Orchestrator. An external app gets the permissions required to perform particular operations in a folder or tenant through one or more roles.
The app gets the union of all scopes defined for it in Automation Cloud and Orchestrator. Deleting either of these scopes leaves the app with access levels according to the remaining scope.
You can also use groups to simplify external app management, as groups allow you to manage objects with similar needs together.
Read more about configuring fine-grained permissions for external apps.
The date when a change is first announced in the release notes is the date when it first becomes available.
If you don't see the change yet, you can expect to see it soon, after we roll out changes to all the regions.
We recommend that you regularly check the deprecation timeline for any updates regarding features that will be deprecated and removed.
- 28 November 2022
- Improvements
- Bug Fixes
- 23 November 2022
- Test Suite Entities Migration
- 21 November 2022
- Disabling Cloud Robots - VM Machines
- Automatic VMs for Cloud Robots
- Automation Cloud Robots - VM Availability Profiles
- 18 November 2022
- New Credential Store
- 15 November 2022
- Fine-grained Permissions for External Apps
- 14 November 2022
- Bug Fixes
- When Can I See These Changes?
- Deprecation timeline
