Release date: 28 October 2020
For a smoother experience integrating our products, a new way of deploying our products is here!
Using Interactive Sign In, the Robot and Studio are connected to Orchestrator and licensed based on user identity. This removes the need to manually connect via machine key, simply sign in from the UiPath Assistant or Studio. With Interactive Sign In, you no longer need to create individual machines or machine templates for each robot, as they are created seamlessly.
All of this takes place in the authentication process, reducing user friction to a minimum and removing the need for administrators to spend time creating a machine for each Robot.
The UiPath Assistant got a new design, introducing a second column where you can add your favorite processes and arrange them as you please based on groups or use it to configure a process. With a refreshed color scheme and user interface, it is now a more pleasant and intuitive experience.
Picture in Picture (PiP), the feature that allows you to run a process in a new session on your machine is now out of the experimental phase. Run your processes in PiP to continue your work without worrying about foreground automations getting in your way. If you want to set a process to use the Picture in Picture mode every time you run it, it can be configured from the Project Settings in Studio or directly from the UiPath Assistant. Starting with this release, processes that support Picture in Picture can now be marked as PiP Ready to indicate that they have been tested and confirmed to work in PiP. You also have the option to set a process to Start in PiP by default directly from Studio.
For more information, see our Picture in Picture documentation.
Invoke Activities such as Invoke Process, Invoke Workflow and Run Parallel Process have the option to choose whether to start the new process in Picture in Picture mode. This can be set from the Properties tab of the activity in the Misc > Target Session inside Studio.
You can now remove processes published in your Personal Workspace directly from the UiPath Assistant, without the need to access Orchestrator. This makes it easier to clean up any process that is no longer needed.
Find more information about a process by accessing the Process Details submenu in the UiPath Assistant with a simple click on the Process Title.
Here you can see the Process Name and Description based on details provided in Studio, add values for input arguments and set the process to start in the Picture in Picture mode directly from the UiPath Assistant.
Starting with v2020.10 UiPath integrates nShield Key Storage Provider, making it possible for Unattended Robots to log into Windows by using the nShield Key Storage Provider. nShield is a key storage which provider which allows enterprises, and not only, to provide an extra layer of security when logging into Windows by using the keys stored in the HSM.
You no longer need to restart the Robot service for changes to the following Orchestrator settings to take effect:
SignalR settings (including on/off)
Other changes not listed above still require a restart in order to take effect.
To ensure that a process runs continuously, and it cannot be stopped accidentally by users, Always Running Processes restricts the user from stopping a process from the UiPath Assistant. Learn how to manage processes in Orchestrator.
When executed on 20.10 Robots or newer, the Write Line activity only outputs logs at
tracelevel rather than
informationlevel. This change has been implemented to correct an issue that caused this activity to send logs to Orchestrator and other log stream destinations.
RegisterUserModeServiceparameter is not applicable anymore. To make sure install scripts continue to work, you would need to remove this parameter.
As Global Exception Handler uses WWF Tracking, when working with a large number of small iterations (1000-10000) in a project, enabling it decreases the performance as it adds an overhead to each activity.
Business Exceptions are not supported in an isolated workflow, all exceptions return as System Exceptions.
Errors generated by the Invoke Workflow File activity are no longer duplicated in the Output panel.
IWorkflowRuntime.RunningJobInformation.JobIdwas wrongly reported in workflows invoked using the Isolate option of Invoke Workflow File.
Updated about a month ago