This topic goes in-depth about the improvements in Robot & Assistant. To read about other products, please navigate to the main topic here.
Until now, if a process or isolated workflow would have been invoked, whenever it throws an error, no matter the type, in the parent process, the exception will be of type SystemException.
Starting with this release, the exception type will be passed from the child process to the parent one.
Example scenario: processA invokes processB, during execution processB throws a BusinessException,
Previous behavior: the invokeProcess activity would fail with a SystemException
New behavior: the invokeProcess activity fails with a BusinessException
Whenever your Robot or Assistant needs to pass through a proxy that requires basic authentication, in order to connect to the internet, you will be asked to input your proxy username and password.
This allows your Assistant and your automations to access resources outside their network, via basic authenticated proxies.
For processes published locally, you now have an easy way to move them to your Personal Workspace once you connect to Orchestrator, from Assistant. The first time when you use Assistant (connected to Orchestrator), you will be asked to choose if you want to migrate your processes to Personal Workspace or not. If you choose to skip this step, you will find this option in Preferences, in the Tools section.
We added new guided tours to help showcase and navigate the users through different features of Assistant. This can be accessed from Preferences, in the Help section.
We removed Angular support for custom widgets, so make sure to update them if you want to continue to use them in Assistant. More details here.
Marketplace Governance: we now give additional governance capability for the Marketplace Widget within the Automation Ops: now you can filter the content shown in Assistant by choosing if you want to see only ready-to-go automations developed by UiPath or not.
Policy Settings: We added new Automation Ops policy settings in the Feature Toggles tab (please also check the attached screenshot below):
Enable Task Capture: We added the option to show/hide the Task Capture button
Group processes by folders: We added the option to enable/disable the user’s ability to group processes by folder. Also, we added the option to allow users to change this option directly from Assistant by adding a checkbox setting in the policy.
Minimize Assistant while a process is running: We added the option to enable/disable the minimization of Assistant while running a process.
Automatically start Assistant with OS: We added the option to enable/disable the start at login; If checked, the Assistant starts at login time in tray mode.
Log Level changes: We added the option to enable/disable the Log Level picker from Assistant. By default, Log Level changes are enabled, but they can be disabled by switching to No.
Note: To use these new options, update your policy template to 2022.10 version.
With this release we bring a new feature that offers the users the ability to start the Diagnostic Tool directly from the Assistant. This will automatically run the Diagnostic Tool and offer the user the resulting .zip.
For macOS users, we offer the ability to collect log files and archive them so that users can have easy access to them.
In this release we did also some UX improvements in different areas of our product: a few labels were changed and the “Stay offline” option was moved to Orchestrator Settings section.
Starting with 2022.10, we created a PiP alternative that uses the virtual desktop. This option allows more people to benefit from the PiP feature, as it can be very useful for clients that are using the same Windows Server machine for their employees and connect remotely to it.
Thereby, there are now two different technologies of Picture-in-Picture (PiP) execution:
The session-based PiP: this is the one that is already available from 2020.4, from which you can run a process in a separate window that allows you to watch the robot executing → this option only supports one PiP user session per machine.
The virtual desktop PiP: this is the new PiP option that uses the virtual desktop, from which you run a process on a second desktop and can switch back and forth between desktops to observe the PiP execution → this option supports multiple PiP user sessions per machine (this can be helpful for people using the same Windows Server). Other benefits: Does not require re-authentication and the launch of startup apps on the second desktop.
Projects can be configured by developers to have the Virtual Desktop type of PiP from Studio. Access Project → Project Settings → General → PiP Type → New Desktop, as seen in the screenshot below:
Starting with 2022.10, you can see the number of pending, unassigned, or completed actions directly from the launchpad. Once pressed in any of the cards below, a window opens with the Action Center. The work you usually do from the Cloud Portal → Action Center can easily be done also from the Assistant.
Automation Ops Policies: Action Center can be enabled/disabled through the following policy setting from the Feature Toggle tab → Enable Action Center.
Now you can switch tenants more easily through a menu found next to the connection status, as seen in the screenshot below:
For quick access to the current Orchestrator tenant, go to Orchestrator Settings and click the button next to “Service URL”, as pointed out below:
Which features excite you the most and you are going to try right away? We want to hear what you think! Please use the button below