Release date: 27 October 2022
A new type of Picture in Picture based on virtual desktops is available. This allows you to run automations on a virtual desktop, supports multiple PiP user sessions per machine, and it does not require re-authentication or launching startup apps.
When using a basic authentication proxy, you can set the credentials directly from the UiPath Assistant.
Two new guided tours are now available for new UiPath Assistant users to quickly learn how to run automations and use reminders. The tours are automatically launched when the UiPath Assistant is opened for the first time and can be started at any time from the Preferences menu. Find more information in the Help menu documentation.
When the Robot connects to Orchestrator, UiPath Assistant now prompts you to migrate locally stored automations to your personal workspace folder in Orchestrator. You can migrate your local automations from the Preferences menu as well.
Automation Ops policies now provide more options to manage how users interact with the UiPath Assistant.
Besides widgets, you can now set the following:
- Automatically start Assistant with Windows.
- Allow/disallow users to change the logging level.
- Minimize Assistant while an automation is running.
- Enable/disable Task Capture.
- Allow/disallow users to run automations outside the Personal Workspace.
- Group automations by folders.
For more information, see the Automation Ops governance documentation.
Starting with 2022.10, you can do more without leaving the UiPath Assistant, as you can now run Apps and manage your actions from Action Center directly in the UiPath Assistant, without having to rely on a browser.
You are now able to define trusted IP ranges from which users can connect their robot and Assistant to Orchestrator. If a user tries to connect from an IP outside of the allowed ones, an error message is displayed in the UiPath Assistant. Read more about Restricting Access by IP.
If you have access to multiple tenants, you can now switch between them directly from a drop-down list next to your name, in UiPath Assistant, without having to sign out and sign back in.
Environments using policies that enforce Kerberos authentication for RDP are now supported. You must set the
UIPATH_DNS_MACHINENAME environment variable on the machine with the value
True. This toggles the use of DNS host name for localhost when creating RDP sessions.
You are now able to connect your Robot and Studio to Orchestrator using Client Credentials at install time. This is available for both the user interface and command line interface installations.
More details can be found in the installing Studio documentation
Information logs are now written to a file instead of event log:
To avoid creating a large amount of log files consuming disk space on the machine, you can choose to archive log files once a specific number of files has been reached. For more details see the Robot Logs Documentation.
IRunningJobInformationproperty now has additional properties. See the Building Activities documentation for more information.
Fallback packages folders can be configured by adding the
NUGET_FALLBACK_PACKAGESenvironment variable on the robot machine. More information can be found in the fallback folders documentation.
- The session would time out due to registry entry cache after a successful RDP connection.
- The Robots Windows Session would disconnect unexpectedly and the user would be presented with an error message that the Windows screen is locked or a UI timeout occurred.
- Invalid log messages were sent to the Event Viewer when the Robot was installed in user mode. Logs are now sent as expected in per-machine installations. The issue still occurs for the user-mode Robot in per-user installations.
- If Assistant is opened with Studio, Diagnostic Tool cannot be started from Assistant. To resolve this, quit and restart the Assistant.
- Some default log fields can no longer be overwritten. More information here.
- The process list is refreshed in parallel with the process execution, prior to this, the process list was refreshed before the process started. This means that when running a process via RobotJs or CMD for which an update is available, the job might run with the older version of the process.
- The actual exception type is now logged when using Invoke activities.
- Custom widgets created with Angular are no longer supported.
- Starting with the 2023.4 Enterprise release, the 32-bit installer will be discontinued, and you will only be able to install Studio, Robot, and Assistant on 64-bit operating systems.
- Starting with the 2023.4 Enterprise release, the default Linux robot image will be discontinued and replaced with the image used to run Chrome Automations on Linux.
We recommend that you regularly check the deprecation timeline for any updates regarding features that will be deprecated and removed.
Updated 21 days ago