UiPath Release Notes

UiPath Release Notes

Release date: 24th April 2019

What’s New


Package integrity and authenticity are vital in terms of security, which is why we’re introducing Package Signing for signing libraries and processes with your own certificate. The feature is available both from Studio’s Publish window and command-line. Learn how to sign packages when publishing processes here.

Furthermore, in support of this feature, you should know it is possible to enforce your Robots to execute only signed packages at install-time, by using the newly added ENFORCE_SIGNED_EXECUTION parameter. More information about this is available here.

Process Keyboard Shortcuts

Start and stop processes at the press of a button. Literally! It’s now possible to assign global keyboard shortcuts to start, pause and stop processes from the Robot Agent (Tray). This allows you to easily cease and resume execution on Attended Robots without having to use the mouse. It comes in handy especially if the process uses plenty of Click activities. Global keyboard shortcuts can also be assigned to any of your processes in order to start them even faster. Read more about it on this page.


Automation processes developed in Studio now come with the option to prevent them from being paused. This means that when the process is running, the Pause button in the Robot Tray is disabled. This feature is useful when pausing an asynchronous execution might cause it to break. Find out how to use this option documentation.


We know you can’t get enough of the Robot so we decided to let you keep it pinned to the Taskbar. This makes it easier to invoke processes in attended automation scenarios. Check it out here.

If you feel that your Robot needs a change, then try it in the Dark Theme. It still executes your processes as before, but now in a fashionable manner. The theme can be changed from the User Preferences window.

It’s now easier to tell whether the Robot is installed as a Service or in User Mode. The UiPath.Service.Host.exe file is executed when the Robot is installed as a Service, while the UiPath.Service.UserHost.exe file is launched when in User Mode. Rest assured, the installers all accommodate this change. For more information, check out the installation, update, and CLI guides.

In an attempt to deliver more control over process execution, we have added a feature flag which can block execution of processes from the command line while the Robot is connected to Orchestrator. It is enabled from the UiPath.settings file. Here’s how it’s done.

We’re paving the way for full accessibility support. As a consequence, applications which provide visual and auditory feedback (such as Speech Viewer) can now interact with the Robot Agent buttons, labels, including the processes in the tray.

Orchestrator configuration options and Robot logging are now set from the Orchestrator Settings window, while the language, theme, and global keyboard shortcuts are configured from the User Preferences window.

From now on, Unattended Robots install packages before creating the Windows session.


For those that work offline, we have some good news: you can disable the default online feeds for Robot during the deployment process. This facilitates a seamless installation process even in restrictive environments without Internet access, from the command line. For more information, access this page.

You can now configure the download location of your automation processes and their dependencies, for Studio and Robot, through the command line of the UiPathStudio.msi installer. This feature provides a customizable architecture to suit both secure deployments and hotseat scenarios. To read more about the newly added PACKAGES_FOLDER parameter and how to use it in your mass-deployment of Robots, see this page.

Moreover, you can add your own activity feeds at install-time by using UiPathStudio.msi's command line. More information about the CUSTOM_NUGET_FEEDS argument and how to use it to set up your environment can be found here.

In our quest for continuous improvement, we collect usage and performance data to help diagnose problems and enhance our products. This feature now also comes with the possibility of turning off telemetry at install-time through the TELEMETRY_ENABLED command line parameter or later on using the dedicated configuration keys. More information is available here for UiPathStudio.msi and here for UiPathOrchestrator.msi.

To help you get a better handle on what happened during the setup process, UiPathStudio.msi now also logs licensing information (regutil.exe) while it is running, at a custom location.

Bug Fixes


  • Changing the system date or time during the process execution would interrupt and fail it. This happened because of the .NET functionality used to store time variables, which is also responsible for deciding the session idle time.
  • The Locals panel now properly displays variable information.
  • When in User Mode, the Robot would not disconnect after the user logged off.
  • Support for CAA components in the Fujitsu Java framework was introduced, while also fixing the functionality of the Extract Data activity on tables.
  • Fixed several Nexaweb Java framework related issues which were affecting combo boxes and the functionality of the Extract Data activity on tables.
  • Fixed an issue which was causing particular HTML elements to trigger an error when selected with UI Explorer.
  • The Robot Agent was inconsistent when Windows was set to High Contrast Mode.
  • The process status in the Robot Agent did not automatically update for processes started from Studio and which contain the Report Status activity.
  • Projects failed to be published from Studio Community Edition to Orchestrator.
  • The Pack command would return an error if the required dependencies were not available locally or in the NuGet download folder.
  • Executing a process through the -f command did not use the Orchestrator activity feed.
  • Stopping the Robot Service during a process execution initiated from Orchestrator would provide misleading job state information.

Updated 5 months ago


Suggested Edits are limited on API Reference Pages

You can only suggest edits to Markdown body content, but not to the API spec.