May 2024

May 29, 2024

Discontinuing the Robot role for new tenants

As part of our ongoing endeavor to modernize our access control infrastructure, we have made the decision to discontinue the mixed Robot role for new tenants. It will, however, continue to be available for all existing tenants.

This is the role combination you can use to replicate the same permissions:

• Allow to be Automation User at the tenant level
• Automation User at the folder level

Please also check out the Recommended role-to-group mapping page for further suggestions.

Unattended setup improvements

We have improved the experience of creating a new unattended setup. The changes are the following:

• We have replaced the ACR VMs reference with ERO VMs under the Self hosted (Unattended Robot) section.
• We have renamed the Unattended Robot option to Unattended setup when creating a new unattended setup.
• We have renamed the Add machine button to Create a new machine template when configuring the unattended infrastructure.
• You can now proceed to completing the setup without choosing a folder.
• On the last step of the setup, in the Machine status section, we no longer display the number of machines associated to the selected template.

Retrieving jobs from the read-only replica

Jobs data is now retrieved from the Orchestrator read-only replica, which is used for ensuring uninterrupted performance.

Displaying queue transaction details as a side panel

Queue transaction details are now displayed in a side panel, adjacent to the transactions list. This means that you can now benefit from:

• A better outlook - All the details of a transaction are available in a side-by-side view.
• More screen space - The side panel can be resized or expanded to a full-sized window for enhanced visibility.
• Efficient navigation - Navigation between the details corresponding to several transactions happens by simply clicking anywhere on a transaction row. This allows you to easily move through the list while also maintaining focus.

Transaction details side panel

Reverting name fields prepopulation

A week ago, we announced that the name fields for processes and triggers would be prepopulated with the name of the package and of the process, respectively.

We have since discovered a small hiccup, so we are rolling back this feature while we work on fixing the issue. We'll keep you posted on the reenablement as soon as it happens.

Removal of API parameters

The AcceptedDomainsList and HasConnectionString parameters have been removed from the GET/odata/Tenants endpoint.

Bug fixes

• When using triggers configured with a Non-Working Days calendar and deleting the calendar from the tenant, the calendar would keep working until the next scheduled time.
• The Monitoring page mistakenly displayed the status of Automation Cloud Robot - Serverless machines.