- Release notes
December 2021
From now on, you can keep Orchestrator free from clutter by removing disconnected or unresponsive unattended sessions. This operation allows cleaning up unused sessions and helps provide relevant insights to administrators by only showing connected sessions.
To remove the unattended sessions one by one, navigate to Tenant > Robots > Unattended sessions and for the disconnected session you wish to remove, click More actions > Remove. To remove multiple sessions simultaneously, select the sessions and then click the Remove icon.
To help with cleaning up, we also implemented a background job that deletes old disconnected and unresponsive sessions as follows:
- Automation Cloud Community users - the background job removes 3-month old disconnected and unresponsive unattended sessions;
- Automation Cloud Enterprise users - the background job removes 6-month old disconnected and unresponsive unattended sessions.
This feature is only available to Enterprise and Enterprise Trial customers and requires an Automation Cloud Robots license.
For the duration of the preview, all customers who have an Enterprise license receive a free Automation Cloud Robots license, which is required to use this feature. Happy automating!
Automation Cloud robots make it easy to set up the necessary infrastructure to run automation.
We handle all the work behind the scenes and give you a virtual machine on which to run automations. The only thing you have to do is configure the virtual machine and run jobs.
Similar to elastic robot orchestration, this is a solution to help reduce the effort for getting your robots up and running, except you do not need a subscription to a cloud services provider (CSP).
For instructions, see Automation Cloud robots.
To learn more about feature, also see the related forum post.
Orchestrator is now also available in the Singapore region. If you create a tenant in this region, the data for the Orchestrator service is hosted in Singapore.
For more information, see Data residency (cloud) .
From now on, you can give a custom name to the Central Credential Provider web service. To this end, a new field is available when configuring a CyberArk CCP credential store that allows you to set the service name, Web Service Name. Leaving this field empty means the default name is used: AIMWebService.
The RPA Developer Pro, RPA Developer, and Test Developer Pro user licenses are now consolidated as the new Automation Developer license.
Here are the 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.
