July 2022

29 July 2022

Permission Elevation Now Prohibited

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.

26 July 2022

Job Priorities

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:

Low > Low
Normal > Medium
High > High

Additionally, job priority can be set from the API, as a numeric value between 1 and 100, by using the new SpecificPriorityValue parameter available in the following endpoints:

POST /odata /Jobs /UiPath.Server.Configuration.OData.StartJobs
POST/odata /ProcessSchedules
PUT/odata /ProcessSchedules({key})

Confirmation Window When Deleting Users

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.

Separate Alerts for Attended and Unattended Robots

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:

Previous alert	New alert - Attended	New alert - Unattended
"Robot is disconnected." Severity level: Fatal	"Attended robot is disconnected." Severity level: Info	"Unattended robot is disconnected." Severity level: Fatal
"Robot is unresponsive." Severity level: Error	"Attended robot is unresponsive." Severity level: Info	"Unattended robot is unresponsive." Severity level: Error
"Robot is available." Severity level: Info	"Attended robot is available." Severity level: Info	"Unattended robot is available." Severity level: Info

Bug Fixes

Exploring packages of workflows with two or more consecutive flow switch activities resulted in an error.
When you deleted a process that was associated to a trigger, that particular trigger was still displayed on the Search page, instead of being deleted along with the process. If you tried to edit the trigger on the Search page, the "ProcessSchedule does not exist (#1002)" error was returned.

19 July 2022

Automation CloudTM Robots - Serverless

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

18 July 2022

Connected Triggers in Orchestrator - Part One

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

Publishing a project to Orchestrator makes the package available in your personal workspace. To make you execution-ready in a jiffy, Orchestrator automatically creates a process in the workspace. The process has the same name as the Studio Web project.
Republishing the automation project to Orchestrator overwrites any process, package, or trigger edits with the values present in the Studio Web workflow.
At publish time, Orchestrator chooses from the available personal workspace's runtimes to execute the job. The runtime precedence is the following:
1. Serverless
2. Production (Unattended)
3. Nonproduction
  
  For example, if no Serverless runtimes exist in your personal workspace, Orchestrator uses available Production runtime. If that doesn't exist either, Orchestrator uses an available NonProduction runtime. If none exists, the job fails.
  
  Note: If the selected runtime becomes unavailable between job executions, the upcoming job execution fails, since Orchestrator does not look for the next available one.

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

Time based trigger

Orchestrator automatically creates the time trigger, which can be found on your personal workspace > Automations > Triggers page.

Event based trigger

The event trigger is displayed in the Package Requirements section of the associated process in Orchestrator (Processes > More Actions > Edit > Package Requirements tab). Its value is the Microsoft Outlook 365 account address used in the workflow.

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.

Note: The only event option available is New email received, which belongs to the Microsoft Outlook 365 connector.

12 July 2022

Contextual Menu for Each Folder

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.