Orchestrator release notes

Previously, when a user attempted to assign roles that included permissions that they themselves did not have, we would display a warning indicating that the operation might require higher privileges.

As of today, we no longer allow assigning roles in such a case, unless you have the Roles - Edit or Roles - Create permissions.

When trying to assign roles with permissions you don't have, the error message points out the roles that include the extra permissions and you must remove the indicated roles to proceed with role assignment.

This change applies when assigning roles from either the tenant or folder context.

Job priority can now be set at a more granular level, with a total of ten types of priority to choose from. These are available at the process, job, and trigger level, and allow you to be very precise when dealing with large numbers of folders, processes, and queues.

Jobs that had one of the previous three priorities are mapped to the new set as follows:

A new confirmation window is now displayed when deleting users. The window lists the users with busy robots and informs you that deleting them also deletes the ongoing jobs. Similarly, when editing a user with busy robot, the confirmation window informs you the jobs might fail.

Starting with 29th June, the alerting mechanism changed to provide separate alerts for Attended and Unattended robots. Therefore, the unattended robots alerts are prefixed with "Unattended". Likewise, attended robots alerts are prefixed with "Attended". In addition, the Fatal and Error severity levels for attended robots alerts are reduced to Info.

The following table summarizes the changes:

When automatically choosing the machine size, for processes that use UiPath Document Understanding activities, we now select the Standard machine size, instead of Large.

Orchestrator accommodates trigger-based automations from Studio Web (currently in Preview) via several personal workspace adjustments:

Additionally, there are specific adjustments depending on the trigger type used in the Studio Web project:

Time based trigger

Event based trigger

Known issue: If your Microsoft Outlook 365 connector has several connections (that is, multiple accounts), they are available for selection on Orchestrator's Process > Package Requirements page. Changing the original connection (the one present in the Studio Web project) causes the job execution to fail. To prevent the failure, edit the connection in the Studio Web project and republish it to Orchestrator.

Each individual folder now has its own contextual menu. It offers an at-a-glance view of all folder-scoped actions, aggregating the options that were previously included in the Quick Actions and Folder Selection menus.

What is more, the selected folder's name is now displayed in the breadcrumbs, and clicking it takes you back to the Home tab.