Release date: 9 May 2022
Processes created in Studio 2022.4 with Windows and cross-platform compatibility now start with up to 50% faster compared to the previous release.
To take advantage of this, remove all unused dependencies from your workflow.
Robot now uses the latest .NET release, .NET 6. Windows and cross-platform projects now also target .NET 6.
We are happy to announce that with the 2022.4 release, UiPath Assistant becomes available on macOS, enabling you to access automations right from your desktop. The Auto-Update functionality now also supports Assistant and Robot on macOS.
A guided tour is now available in Assistant to help new users quickly learn and discover its menus and functionalities. This tour is automatically launched when Assistant is opened for the first time and can be started at any later time from the Preferences menu.
The new Workflow Events activities pack contains a new activity, Send Interim Result, enabling communication between UiPath Apps and processes for attended robots. These activities enable you to send interim process results (IPR), reducing the time to display process results.
This pack is meant to be used when the time to start a process is a bottleneck in your automation and you need to wait for an entire automation to complete to obtain the process results.
Starting with 2022.4, UiPath Robot supports authenticating in a Windows session using Azure AD credentials (azuread/[email protected]). This helps you run unattended automations in environments where you only have cloud Azure AD implementations.
The Orchestrator URL used for Interactive Sign In can be changed from the command line interface.
In this release, we ship a new robot authentication mechanism that uses the OAuth 2.0 framework as the basis for its authentication protocol, meaning unattended robots can connect to Orchestrator using a client ID - client secret pair generated via machine template objects. The client ID - client secret pair generates a token that authorizes the connection and provides the robot with access to Orchestrator resources.
Client credentials allow the UiPath Robot to access resources by using its own credentials, instead of impersonating a user. When the robot requests resources from Orchestrator, Orchestrator enforces that the robot itself has authorization to perform an action since there is no user involved in the authentication.
Starting with 2022.4, you can view the execution history of each process in UiPath Assistant. This provides a way to track processes, see the status and any errors if available.
The following collectors have been added to the Diagnostic Tool:
- Registry Key Path
- “File Path” with the following filtering options:
- Time Range
- Error Level
- The robot could not change the resolution on the Windows 11 console session.
- In rare cases, an invalid token was used as a reference when the
LoginToConsoleparameter was set to
- The Send SMTP Mail Message activity would sometimes hang or not complete when used multiple times in a short time span.
Display Namewas missing from Assistant when a job was started from Orchestrator.
- UiPath Assistant would stay in a suspended state after an Interactive Sign In session expired.
- The authentication flow would break when multiple background processes were run without RobotJS consent.
- RobotJS would not work when the machine name was in Chinese.
- Starting with 2022.4, the PiP session timeout is uses the
UIPATH_PIP_SESSION_TIMEOUTenvironment variable instead of UIPATH_SESSION_TIMEOUT.
- Unattended background automations on service-mode robots run by default under the built-in "Local Service” Windows user. Prior to this, the username and password configured in Orchestrator were used.
To use credentials set in Orchestrator, you need to configure the
UIPATH_HEADLESS_WITH_USERenvironment variable on the robot machine and set the value to
- The 2022.4 Robot is not compatible with the 2019.10 Orchestrator.
Updated 16 days ago