UiPath Release Notes

UiPath Release Notes

2019 FastTrack (2019.4.2)

Release date: 24th April 2019

After a series of monthly rollouts validated by our brave Community, the hard work of our dev and product team has condensed into what we call 2019 Fast Track - the first UiPath Platform Enterprise release of this year.

Some of our components have seen major overhauls, while others were optimized and fine-tuned, making sure we bring top-of-the-line technology at your fingertips. For those of you that are curious about all the changes this release brings, we invite you to delve deep into the page below and feel free to click the documentation links for more information.

What’s New

AI Computer Vision

We proudly present the first stable version of the Computer Vision activities, which implement our UiPath in-house developed neural network into standard UI automation activities such as CV Click or CV Type Into, outfitting them with an AI that emulates the human visual system, capable of recognizing UI elements and mimicking human actions. For more information on the new activities, you can find the docs here.

Our proprietary Machine Learning model is packed for on-prem Enterprise-ready deployments, while our cloud server remains free for our Community users, furthering our RPA democratization efforts. For more information on deploying the on-prem server, you can find the docs here.


This new release addresses one of the most highly requested features and gives you real-time metrics to help you keep an eye on the health and state of your system. Be it in regards to Robots, Queues or Jobs, Orchestrator now provides you with a monitoring solution to ease keeping track of your deployment regardless of its size. Check it out here.

Extensibility and Performance

The highly anticipated GIT Integration with Studio is here. We’re bringing you all the goodies to help you clone a repository, create and manage branches, commit new project versions, and manage your work straight from Studio in a smooth way. For more details, check out the documentation.

Studio can now generate activities from SOAP and Swagger web services through the New Service wizard available for libraries. The service is added to the library’s dependency tree and from there on, you can add activities to your library from the Activities panel. Check out the documentation for more details.

For an enhanced all-around sync of activities and packages in multi-node environments, package metadata is now saved to your SQL database. On top of that, instead of the ordinary File System, you can set up your Orchestrator instance to store all these artifacts in one of the following blob storage solutions: Azure, Amazon, or Minio. More information on how you can set this up is available here. Lastly, rest assured - all setup artifacts can help you easily set this up, be it for a clean installation or an update.

File Management

Comparing changes between a process, library, project.json or .txt file in a local repository and the latest version from GIT, SVN or TFS is done using File Diff in Studio. It shows a side-by-side comparison between the two files, highlighting added or removed activities, packages, variables, arguments. Read more about File Diff here.

The Compare Files feature offers the possibility to compare two similar files in the same automation project. Simply use the context menu options in the Properties panel to select the two .xaml, project.json or .txt files for comparison. Read more about this here.

Additionally, the Show History feature displays the difference between the file currently versioned under source control and previous versions. Use Show History from the Properties panel context menu as revealed in the documentation

To improve interoperability and streamline project versioning, Studio now has Semantic Versioning. Versions of your projects can now be set in the major.minor.patch format, and you can set a Prerelease tag for intermediary versions. Read more about semantic versioning in the documentation.

To enhance your automation experience, we’ve added Global settings and Default Locations for projects. Learn more about this here.

On top of that, we’ve also incorporated Project settings for renaming a project and changing its description, as mentioned here. Last but not least, Library properties bring the option to add a tooltip and a help link to the new activity. Read more about this here.


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.

In addition, to further enhance the security of the Robot - Orchestrator communication protocol we added the possibility for the Robot to authenticate through a custom HTTP header. In this regard the web.config parameter, Scalability.SignalR.AuthenticationEnabled, is now at your disposal. Please note that if you enable this feature, also referred to as Robot SignalR authentication, you are no longer able to execute jobs on Robots with a version lower than 2018.4.3. More information is available on this page.

Bringing an even better segregation of sensitive information and an enhanced level of security between tenants, you can now use a unique encryption key per tenant, using Microsoft Azure's Key Vault. This has been made possible by adding a few more parameters to the already-popular web.config file. You can view more information on how you can configure these settings on this page.

In Orchestrator v2018.3 we introduced libraries to help you share reusable components at application level. In this release, we've turned our attention to segregating libraries at tenant level to ensure a more secure approach to your data. This means that in addition to the shared host feed, you may configure your libraries to use their own tenant feed.

Last but not least, the system administrator is now able to upload a library which gets propagated to all tenants which use the host feed. How cool is that? If you're interested in reading more about this feature and how to use it explicitly, visit our documentation.

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.


If you always wondered what your Unattended Robot is up to and what exactly is going on with your unsuccessful jobs, you came to the right place. This release ships with a recording functionality that helps you troubleshoot faulted jobs. Simply configure your processes to allow recording and, whenever the corresponding jobs fail, the media files illustrating the last moments of a job are at your disposal. Keep in mind that this functionality comes with a new permissions set. Click here for more information.

Debugging involves lots of attention to details and tinkering to bring the workflow to its best shape. After inspecting or making changes during debugging, use the Focus button to return to the activity where debugging stopped and then click Continue to resume from where you left off. Check out the documentation for more info.

In addition, we’ve implemented a way to enable or disable all or just a single breakpoint in a workflow, and persist these settings when reopening the project in Studio. Find out more here.

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.


As you're probably used to by now, month after month we draw closer to our final goal of creating the ultimate document processing platform. Alongside the first enterprise release of this year, the IntelligentOCR activities pack has been imbued with some new activities, as follows:

The Taxonomy Manager is the next piece of the document processing puzzle, a wizard created to help you build custom taxonomy files which can then be reused across processes.

We have developed the Load Taxonomy activity, which grants you the ability to load the taxonomy created with the aid of the Taxonomy Manager wizard into a variable which can then be passed on to other activities.

The DegreeOfParallelism property has been added to the Digitize Document activity, enabling you to perform OCR analysis on multiple pages simultaneously. This is not a breaking change, so old workflows still function properly after updating to the latest version of the pack.

The Digitize Document activity has been improved performance-wise with some backend changes.

The IntelligentOCR pack is now upgraded to .NET Framework v4.6.1.

The MatchingDocumentDefinition property of the FCDocument variable has been exposed. Assigning it to a variable generates the same result as a Classify Document activity.

Document Processing Contracts

Our first iteration of the Document Processing Contracts pack enables you to integrate your own data extraction and classifier activities with the IntelligentOCR activities. This means that you can easily match our data extraction interface with your own custom-designed processes by signing them with the data contracts provided in this pack.


We have developed a RegEx Builder wizard which gives you the ability to harness the power of Regular Expressions with a simple and easy to use UI. This wizard can be accessed from the body of the IsMatch, Matches, and Replace activities.

Our goal is to simplify the way you interact with Orchestrator, so we've implemented the possibility of adding multiple queue items into a new activity, Bulk Add Queue Items.

Optimizing the way queue items are processed, the new Wait Queue Item can notify Orchestrator it is ready to receive a queue item, and then wait for Orchestrator to add an item to that queue, eliminating the need for multiple retries.


Variables can now be used when editing a selector in the Selector Editor, so now you can easily store parts of selectors in variables and reuse them without a hassle.

The newly developed Microsoft Azure Computer Vision OCR engine uses the new API from Microsoft, enabling you to keep up with the evolution of technology.

We've added the ability to automatically downsize images to the Google Cloud Vision OCR activity, adding a new property called ResizeToMaxLimitIfNeccesary. This has been done to make sure the size of your images does not break the maximum limit of the engine.

The Abbyy OCR activity can now be configured to use Abbyy FineReader Engine 12 via the FineReaderVersion drop-down property. Also, the PredefinedRecognitionProfile property can be used to use one of the official Abbyy recognition profiles and the CustomRecognitionProfilePath property can be used to load in your own recognition profile into the project.

The new Context Aware Anchor has been created by building upon the old Anchor Base activity. To increase precision, it now takes into account the pairs of anchors and targets, without requiring an anchor to be unique.

Edge (Experimental)

The v19.4.0 UIAutomation package now makes it possible to create automations in the Edge browser! Read all about it here! Oh, since this is an experimental feature, you might also want to check out the troubleshooting guide.


There’s always something more to automate! With this release, we make it possible to natively generate selectors for applications which rely on the JxBrowser library. No extensions required! There are, however, a few limitations, about which you can read on thispage.

RDP Extension

Creating automation projects over RDP connections just got a lot easier. With the help of the Windows Remote Desktop extension, selectors are natively generated. Find out how all of this is possible on this page.


We're proud to say we have added Lotus Notes to the list of email clients we support! This means we've developed four new activities which can handle your inbox with ease. These activities are:

Also, we understood the need to be able to reply to a mail in Outlook, so we have created the Reply To Outlook Mail Message activity, which helps you do just this.


This major release brings five new activities to the PDF activities pack, helping you manipulate more aspects of PDF documents, as follows:

The change to v2.0.0 is also due to the fact that the engine of the PDF activities has been overhauled, and now uses a more efficient method of retrieving text from .pdf and.xps files. This change is reflected in the old activities of this pack, as well, meaning that the Read PDF With OCR and Read XPS With OCR activities have some new properties, as well as some upgraded old ones.

Orchestrator Mobile Apps

This month the Orchestrator Mobile app also received a pretty important update that you might want to check out - you can now start jobs directly from your Android or iOS device. Other improvements have also been made available, about which you can read here.



The Package Manager now integrates support for activity packages with license agreements. Make sure to read and accept the license terms before installing the package to your automation project. To find out more check the documentation.

Studio introduces High Contrast mode, which adapts to the Windows setting and switches with a simple restart. To find out more check the documentation.

Renaming an argument from the Argument panel updates all its occurrences across the file.

Select one or multiple variables or arguments from the panel and copy them to another workflow. The name, type, and default value is also copied.

One or multiple variables can now be converted to arguments and the other way around from the panel context menu.

We’ve added keyboard shortcuts for creating both In and Out arguments. Check this page for an extended list of keyboard shortcuts in Studio.

Variable and argument types part of assemblies proprietary to Studio or Robot are now hidden. This was done to ensure forward compatibility in the event of any internal changes that we may bring to these assemblies. Workflows that reference types from such assemblies should not be affected at runtime. For more details, check the documentation.

Feeds for Activities Packages are now available in Studio Backstage view too, not just from the Package Manager. This way, you can adjust activity feeds even before you open a project. Find out more about this here.

Favorite activities can now be marked in the Activities panel. Simply use the new Pin Favorites context menu option and have all of your most used activities always visible in the panel. Check the documentation for additional info.

The project’s Full Dependency Tree is now visible in the Project panel. All you need to do is expand the dependency to view sub packages and their versions. In addition, it is now easier to differentiate between resolved, unused, not found and best match dependencies. Find more information about this here.

Info on Studio version, type of installer, device ID, license expiration and more is now available in Studio Backstage view as well. Hover over the details and get the exact date when the current Studio was released.

The Robotic Enterprise Framework template from Studio now includes a project.json and UiPath.Credentials.Activities as part of its dependencies.

Studio also brings improvements in terms of usability and accessibility. As such, tooltips now remain persistent on hover, and a Restart button when changing the interface language and theme. Learn how to access it in the 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.


If you regularly need to add items into your Orchestrator queues, you'll be pleased to know that we've come up with a feature which allows you to add queue items directly from a CSV or Excel file. Check it out here.

To enable you to add multiple queue items at the same time from the Orchestrator API, we added a new endpoint - UiPathODataSvc.BulkAddQueueItems. Two different upload strategies, ProcessAllIndependently and AllOrNothing, help you keep control. If you want to see an example of such a request, please see this page.

Orchestrator ships with multiple improvements regarding permissions, thus making role management easier than ever. You are no longer required to select permissions one by one. With the click of a button, you can now select each set that interests you either by category or by permission type, in case that serves you better. In addition to that, the Libraries page now has its very own set of permissions, separate from packages. Details here and here.

Furthermore, we look after power-users as well, as we provide a new web.config parameter which gives you the utmost control over roles and allows you to disable permissions from both the user interface and API. Click here for more details.

Performing GET calls to the /api/Status/VerifyHostAvailibility endpoint now requires authentication.

As you might have noticed, we've always tried to help as many people as possible to learn how to use UiPath Platform. As another piece of the democratization puzzle, we are happy to announce that, in terms of accessibility in Orchestrator, we now have achieved a Level A conformance.

To aid you in efficiently managing the manual upload of automation packages through the user interface, Orchestrator now enables you to select and transfer multiple archives at a time.

Several enhancements have been made to the /odata/Tenants endpoint. The DisplayName and Key properties have been exposed to help you pin-point your tenants in an easier fashion, with just a simple GET call. Secondly, you can now perform PATCH requests at the /odata/Tenants(Id) endpoint, to modify the DisplayName and AcceptedDomainsList properties.

It is now possible to perform PATCH requests on the /odata/Robots(Id) endpoint, so that you can easily change certain details about a specific Robot without needing to know its password and username.

Stacktrace information is no longer displayed in responses when making invalid requests to the Orchestrator API.

Package version management is now a breeze with our new bulk update feature. Yes, you heard that right. As of now you can update multiple processes at once in Orchestrator and it only takes a minute. Click here for more information.

Worried you won't be notified in time that your license is about to expire? On the contrary, you consider email alerts to be a nightmare? We've got you all covered as we added a new parameter in the web.config file which allows you to set your preferred checkpoints in terms of license expiry notification emails. By default, the parameter is configured such that emails are sent 180, 90, 30, 14, 7 and 1 day before the expiry date. See here how to configure your own values.

We know it can take a little bit for your system to get back on track after an upgrade, so in order to prevent unnecessary alerts and updates, we made it possible for you to delay the first check on your Robots' status. Add the NotRespondingRobotsJobStartDelay parameter in web.config and configure exactly for how long you want to delay the check on your robots. Details here.

Our dev team has been really preoccupied with improving Orchestrator's capabilities in this release. The overall performance has been improved a great deal, especially in highly dynamic environments. Apart from that, we took care of some specific areas as well, to give you the best experience ever. See for yourself what we handled specifically:

  • To make sure there are no performance penalties in terms of license removal, we made a few changes here and there and improved the mechanism to run smoothly.
  • We've identified an issue that was slowing down the startup performance of Orchestrator so we made sure to optimize it even in the context of complex environments with large numbers of users.
  • We were on a mission to optimize Redis cache usage and we did it. We made a series of improvements, all aimed at reducing the number of Redis calls.
  • Alert distribution has been optimized, thus ensuring a faster performing alert mechanism even in the context of many subscribers.

Coinciding with this release, there are some new additions to Orchestrator's logging solution. As of now, you may connect to databases that support the MongoDB wire protocol using the same NLog target. This means that Orchestrator Robot logs can be stored and viewed using the Cosmos DB service as well. See here details about the logging configuration in Orchestrator.

The sessionState mode parameter is deprecated and as of now defaults to Off in clean installs.

Orchestrator drop-downs have been upgraded. We now have scroll bars to help you browse through all existing entries. Happy scrolling!

The Value field for both global and per-robot text assets now allows for up to 1.000.000 characters.

To ease the management of large deployments, the Robots page can now be filtered by an environment with just a click.

The Webhooks page can now be filtered according to a webhooks' state - enabled or disabled.


The Taxonomy Manager displays the Document Type ID of the document type that is being edited.

The Reference and FilterStrategy properties have been added to the Get Transaction Item activity, enabling you to filter the Transaction Item you want to retrieve by its Reference.

The Orchestrator HTTP Request activity has been improved, and is now able to retrieve the headers of the requests it performs.

The Google OCR, Google Cloud OCR, and Microsoft Cloud OCR engine activities have been renamed to Tesseract OCR, Google Cloud Vision OCR, and Microsoft Project Oxford Online OCR, respectively. Don’t worry, as this does not cause a breaking change to your already existing workflows!

The Extract Structured Data has two new properties that enable you to choose what kind of click you want to use when changing pages if the data you want to extract spans multiple pages.

The HTTP Request and Soap Request activities have been improved, and are now able to retrieve the headers of the requests they perform.

The IBM Watson NLU Text Analysis activity has a new property field, Key, which enables compatibility with Identity and Access Management authentication.


You’ll be happy to hear that you can now create browser automations with native selectors for web applications exposed through Citrix Virtual Apps and Desktops.

Since we’re constantly working on new updates for you, we made it possible for the UiPath Remote Runtime component to support multiple versions.

The UIA_IsEnabledPropertyId attribute is now exposed in selectors. This enhances UI element detection in applications which rely on the UIAutomation framework.

User events monitoring faced an overhaul to address different issues when detecting trigger events, while also improving performance.

To ensure backward compatibility, the UiPath Remote Runtime component is compatible with the 18.4.5 and 19.4.1 UIAutomation versions.


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.

As security has always been one of our biggest concerns, we have now added an extra layer. You can specify the tenant and host admin passwords directly when you install your Orchestrator instance, from the command line or the setup wizard of the UiPathOrchestrator.msi installer. If you want to find out more on this topic, access this pageor this page.

To aid you in silently updating your Orchestrator instance and using the previous database, the APP_ENCRYPTION_KEY parameter of the UiPathOrchestrator.msi installer has been enhanced. More details are available in the guide.

To ensure an even better integration between Azure and Orchestrator, it is now possible to include the local activity feed in your Azure environment directly at install-time, using the newly added activitiesPackagePath parameter. To support this feature, you should also know that we added an archive, UiPathActivities.zip, with all the activities in UiPathOrchestrator.zip. To view more information on how to use this parameter, see this page.

Furthermore, to help you control where to store Robot logs in Azure deployments, a new parameter, -robotsElasticSearchTargets, had been added to the Publish-Orchestrator.ps1 artifact. More information is available here.

UiPathPlatformInstaller.exe now also verifies if you have IIS 7.5+ and URL Rewrite installed on the machine, enabling a smooth set up process.

Breaking Changes


  • The Username parameter is now mandatory for PUT requests on the /odata/Robots(Id) endpoint.


  • While migrating to the public UiPath.DocumentProcessing.Contracts, the IntelligentOCR v2.0.0 activity pack introduces breaking changes for the Classify Document Scope and Train Classifiers And Extractors activities.
  • The v2.0.0 PDF activities pack is no longer compatible with Studio versions below v2018.3.
  • The Read PDF Text and Read PDF With OCR activities have been optimized, and now use a different, better method of retrieving and organizing text. This may cause breaking changes in already existing workflows, as the output text might be different.
  • Fixed an issue which caused the Excel Read Row activity to retrieve incomplete information from workbooks. As a result, retrieved rows now include the empty cells they contain.

Known Issues


  • GIT Integration with Studio does not currently support two-factor authentication. As a workaround, use SSO authentication method with a personal token, or the basic access authentication method.
  • To merge a branch into the master of a GIT remote repository, you need to have the master branch checked out in Studio and then merge the modified branch into master.
  • When trying to push a project to a GIT remote repository that has two-factor authentication, the Output panel shows a success message even though the operation failed, as two-factor authentication for GIT is not yet supported in Studio.
  • Publishing libraries from the command-line user interface does not publish previously generated web service references. More details about this are available here.
  • The uipath.config file is not properly populated if you upgrade your Studio instance to v2019 Fast Track without specifying the telemetry parameter. To rectify this, please read this page.


  • The per tenant encryption key feature can only be used in clean installations.
  • In Orchestrator installations of v2019 FastTrack that use an existing database, although you provide the admin passwords at host and default tenant level, they are not taken into account.
  • The hostAdminPassword and defaultTenantAdminPassword parameters of the Publish-Orchestrator.ps1 script do not properly enforce password complexity rules.
  • You cannot disable telemetry at deployment-time using the Publish-Orchestrator.ps1 script. However, please note that you can manually set it up as explained here.
  • Default activities cannot be uploaded by the Publish-Orchestrator.ps1 script when installing or updating your Orchestrator instance if the NuGet.Repository.Type is set to Composite.
  • If you have invalid cron schedules and you upgrade your Orchestrator instance from v2018.1.x or v2018.2.x to either v2018.4.x or v2019.x, they are not going to work anymore. This occurs due to a change in the Quartz.NET validation code. Please make sure your cron expressions are valid before updating your environment. See here details on how to proceed.
  • Deleting all versions of a library in bulk does not remove them all, as one version always remains in the database and is displayed in the user interface.
  • A user without View permissions on Schedules is able to see schedule-related alerts.


  • The Tesseract OCR engine fails to properly read some images with black borders.
  • The Windows Remote Desktop extension works only with RDP clients that use mstsc.exe.
  • Executing a process which scrapes a large text file with the Get Full Text activity over a RDP session throws an exception.
  • The RDP extension can only be installed per user. This is done either from Studio or the Command Prompt.
  • Jobs started from Orchestrator on a RDP machine throw an exception after many executions. It occurs after the RDP connection is left in a disconnected state multiple times.


  • After you change DPI scaling levels, it is mandatory to restart your Citrix session for selectors to be accurately generated. Find out more on this page
  • Using multiple displays with different DPI can cause inaccurate detection of UI elements when the target window is moved across the displays. Find out more on this page


  • The UiPath Edge extension needs to be installed on Windows 10 build 1803 or above. Find out more on this page.
  • The UiPath Edge extension does not work for a user on a machine if it has been already installed by a different user. Find out more on this page.
  • Processes which use the UiPath Edge extension can not be started from Orchestrator on a machine on which Edge is the default browser. Find out more on this page.
  • In Edge, web page elements are not detected if the web pages are loaded from the local machine. Find out more on this page.
  • When automating the Edge browser, selectors containing the htmlWindowName attribute are not validated. Find out more on this page.
  • The Type Into, Type Secure Text, and Send Hotkey activities need to have the ClickBeforeTyping property enabled. Find out more on this page. In general, for browser automations, it is also recommended to enable the SimulateClick property for activities which perform click operations.
  • On some occasions, element highlighting becomes offset or imprecise.

JxBrowser Applications

  • For JxBrowser applications, the Recording wizard is not yet supported. Find out more on this page.
  • When you use the Type Into activity, be sure to enable the ClickBeforeTyping property. Find out more on this page.


  • Opening the Data Extraction Wizard throws an error when the Data Extraction Scope activity or a parent activity are commented out.
  • Studio crashes when using Computer Vision Recording on a machine running Windows 7 without the KB 2533623 update. For a list of software requirements, please go here.

Monitor Events

  • When the Monitor Events activity is used inside a browser window or browser context, user events triggered with partial selectors are not detected.
  • Click Trigger and Key Press Trigger user events are not detected if the target selectors have anchors.
  • If the idx attribute is in the selector of a web page element, the Click Trigger user event is not detected. This happens on all web browsers.
  • User Events are not supported for Java Applets.
  • The Key Press Trigger user event is not supported for PDF files, and JavaFX.
  • The Click Image Trigger activity does not detect events on web browsers, Java Apps, and Windows 10 Apps.
  • The Click Trigger user event is not supported on Windows 10 Apps, 4k resolutions, and 150% scaling.
  • The Key Press Trigger event is not properly blocked if it uses different keys and modifiers.
  • The BlockEvent option is ignored if there are multiple Click Image Trigger activities in parallel in the same Monitor Events container.

Bug Fixes


  • If you used the Extract as Workflow feature for an activity with two referenced variables, only one of them was extracted as an argument.
  • If you placed a breakpoint on an invoked workflow and then used Step Over, the debugging did not return to the parent workflow.
  • Fixed an issue that prevented variables in a Flowchart from being renamed across activities that contain Expression and Condition properties.
  • The properties of the last executed activity were not displayed in the Locals panel after using Step Over while debugging.
  • Fixed an issue that caused certain hotkeys to be improperly enabled while the Publish Project window was opened.
  • Fixed an issue that made it possible for Studio v2018.3.3 and v2018.4.4 to publish .xaml files in project subfolders with validation errors.
  • When connecting Studio to Orchestrator Community Edition, the label Community Edition is displayed in Studio Backstage view, the Help tab. It is recommended to disconnect Studio from Orchestrator in order to update to v2019.4.
  • Added a notification when trying to close the Manage Packages window although there are unsaved changes, like activities packages marked for installation, changed runtime rules and so on.
  • Fixed an issue that caused Studio to hang in some scenarios after saving or installing activities packages to a large .xaml file of about 10MB.
  • Fixed an issue that resulted in validation errors for certain types of variables after using Extract as Workflow.
  • An error message is now shown if you add a non-supported value for the Key Modifier property when using Dark theme.
  • Fixed an issue that prevented you from adding dependencies or making project changes after resuming connection to a project hosted on a network drive.
  • All items in the Activities and Project panel are arranged alphabetically.
  • Fixed an issue that caused the focus to remain stuck on a versioned file in the Project panel, even though the file was closed in the Designer panel.
  • During the migration of projects in Studio, the UiPath.UIAutomation.Activities and UiPath.System.Activities packages received the highest applicable version in the local feed instead of the UiPath.Core.Activities pack version.
  • Fixed an issue that prevented Studio from logging exceptions generated by copying a large flowchart from one .xaml file to another.


  • 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.



  • The performance of making POST calls to the /odata/Tenants endpoint has been improved, especially when dealing with large deployments.
  • The performance of disabling a tenant has been optimized, especially when dealing with a large number of users.
  • The performance of adding a large amount of Attended Floating Robots through POST requests to the /odata/Robots endpoint has been improved.
  • The performance of executing GET requests on the /odata/Environments(id) endpoint has been improved, especially in environments with a large amount of Robots.
  • Occasionally, due to a dynamic allocation issue, Robots stopped executing jobs assigned dynamically, and remained stuck in a pending state.
  • We've identified and remedied a drop in performance when deploying more than 500 Attended Floating Robots on a single machine template.
  • Multiple quartz triggers were generated in the database for non-existing jobs. This had a detrimental effect on the performance of the scheduling functionality.
  • Occasionally, in poorly performing networks or Orchestrator instances, the user was not logged out of the application after clicking Log Out.
  • The performance of the database notification distribution process was impaired in the context of thousands of alerts being generated at once. For this reason, a timeout exception was occasionally logged as well. Click here for a maintenance solution which may prevent further performance issues and can improve the SQL database response times.
  • Occasionally, due to deadlocks in the database, Robots stopped executing jobs, despite being available.
  • The mechanism behind background jobs has been optimized.
  • An error message was displayed when you tried to create a Robot on a previously defined machine. This only occurred in the context of a poorly performing internet connection.
  • Alerts were displayed with a delay of several minutes after being generated.
  • An error message was displayed when you tried to search for a value on the Robots page. This only occurred in the context of a large Robot deployment.
  • The Application Pool stopped if you uploaded multiple versions of the same package in environments that used the Azure, AWS, or Minio blob storage.


  • Refreshing twice the Manage Users or Manage Environment window cleared all selected entries while still displaying the row count according to the previous selection.
  • Sorting by name or surname did not work on the Users page if at least one user on the list had neither a name nor a surname, respectively.
  • Several synchronization issues were taking place when importing AD users, thus causing incorrect user-role association.


  • Searching for a process on the Start Job window did not return all the results containing the searched string. Furthermore, processes matching exactly the used query were not displayed first.
  • If you started a job on a Robot with no configured execution settings, Orchestrator automatically configured them to false.
  • The Latest button on the View Process window did not work correctly for semantic package versions if you used an external feed. Under the exact same conditions, for processes set to use older versions, the corresponding icon was not updated accordingly.
  • Any changes made to the Logging Level and Allow Development Logging options on the Settings tab were not taken into account when starting processes from the Robot tray. This occurred only if the processes were started before the Robot had sent a heartbeat.
  • An error message was displayed when you tried to edit the parameters of a process immediately after changing its version.
  • Uploading a package larger than the IIS size limit now returns the following error message: "The file you're trying to upload is too big. Please contact your administrator." Take into account that the limit is by default set to 28.6 MB.
  • The StopStrategy parameter on the Audit Data window was set to Kill for a newly created schedule without a stop strategy defined.
  • An error message was displayed when you tried to display the audit details for an action which was performed in a different organization unit.
  • An error message was displayed when you tried to create an asset of type Bool, if its name contained Japanese characters.


  • A user with the Robot role was prevented from accessing the Settings page, even if the role has View permissions on Settings by default.
  • The Upload, Renew and Delete buttons on the License page were not displayed unless having Edit permissions on Settings.
  • The Delete button was disabled whenever adding or removing the Administrator role from the current user.
  • Errors generated by the /odata/Permissions endpoint were logged with both Orchestrator and Orchestrator.BusinessException sources. Now, they are properly logged only under the Orchestrator source.


  • The RolesList parameter was not populated if you made GET requests to the /odata/Users(Id) endpoint.
  • POST calls to the /odata/HostLicenses/UiPath.Server.Configuration.OData.DeleteTenantLicense endpoint did not return 400 Bad Request, although the provided tenant Id did not exist.
  • Fixed an issue that prevented the 404 Not Found error message from being returned if you performed a POST request to the /odata/HostLicenses/UiPath.Server.Configuration.OData.SetTenantLicense endpoint and provided an invalid tenant Id.
  • The body of GET requests to the /odata/Robots/UiPath.Server.Configuration.OData.GetUsernames() endpoint did not include the @odata.count annotation in the response.
  • Robots could not download packages if you updated the tenant name using a PATCH call to the /odata/Tenants(id) endpoint.

User Experience

  • It is no longer possible to delete organization units if they have at least one user associated with it.
  • An error message is now displayed if you create a webhook with a target URL whose SSL certificate cannot be verified.
  • Columns on the Schedules page disappeared when you resized the browser window.
  • The left-hand menu disappeared from the screen if you pressed the Escape key.
  • Switching between organization units on the Robots page caused the Machine filter to be removed.
  • Occasionally, when creating a duplicate Robot using the Create Another feature, no radio options on the Settings tab were saved from the first configuration.
  • An error message was seldom displayed when you refreshed the License page for both the Attended and Unattended scenarios.
  • Changing the tenant timezone caused a one-day discrepancy between the dates on the License Usage graph.
  • Fixed an issue that obstructed incoming traffic to an Orchestrator instance, if the URL contained a custom suffix. Instead, the user was redirected to the original Orchestrator URL.
  • The Open Alerts Preferences icon for the Alerts drop-down was not displayed if you opened your Orchestrator instance in Internet Explorer.
  • You were not able to navigate through the search results in a drop-down list by using the arrow keys. This only occurred in Internet Explorer.


  • Fixed an issue which caused certain UI elements to flicker in the Validation Station wizard.
  • The OperatorConfirmed flag in the ExtractionResults JSON file remained False regardless of whether a user had confirmed the extraction results or not.
  • In certain cases, the Prepare Validation Station Data activity could not read document information from FCDocument variables.
  • Numeric values could not be found if their decimal values were not supplied when using the Filter Data Table activity.
  • The proper exception is now thrown when using the Activate activity with an invalid selector.
  • The NPOI and SharpLibZip dependencies have been updated to versions 2.4.1 and 1.0 respectively, thus ensuring we use the latest versions of the Excel activity package.
  • Fixed an issue which caused the Click Trigger, Click Image Trigger, and Key Press Trigger activities to crash when using certain applications.
  • When importing arguments in the Invoke Workflow File activity, the names of the values were imported but the values were left empty.
  • Using the Read PDF With OCR activity with the Google OCR engine threw an error.
  • In certain situations, Excel Workbooks were closed during the execution of an automation project.
  • Fixed an issue which caused the Process Document activity to crash when processing documents that contained check boxes.
  • Certain types of .pdf files caused the Digitize Document activity to throw errors.
  • Certain types of .jpg files caused the Digitize Document activity to throw errors.
  • In certain circumstances, editing a table with confidence below 100% and making no changes to it modified the confidence to 100%.
  • Fixed an issue which caused the Extract manual token as reference for this field button to remain disabled.
  • Google Cloud OCR crashed when receiving an image larger than its maximum limit.
  • Google OCR was not renamed to Tesseract OCR when used in certain activities.
  • Fixed an issue which caused headers with certain names to be wrongly identified by the HTTP Request activity.
  • The HTTP Request activity did not display parameters edited with the wizard in the Properties panel.
  • Fixed an issue which caused the Get Transaction Item activity to return an error at runtime.
  • The DeferDate and DueDate properties were not logged in the Output panel at runtime.
  • Fixed an issue which caused headers with certain names to be wrongly identified by the HTTP Request activity.
  • The HTTP Request activity did not display parameters edited with the wizard in the Properties panel.
  • Fixed an issue which caused the Present Validation Station activity to throw an exception when processing certain .pdf files.
  • Digitize Document was unable to detect check boxes in certain documents.


  • In Java applications, the Click activity used with hardware events would fail to perform on UI elements from a different tab than the current one.
  • The Chrome extension would fail to install after upgrading Google Chrome to version 73.
  • In a Citrix environment, the running process would throw an error if it contained the Anchor Base activity.
  • The Take Screenshot activity did not return any output if the Windows session was not fully initialized.
  • In a Citrix environment, selectors were not generated for windowed mode Apps.
  • Fixed an issue which was causing selectors for the Comarch ERP Optima application to not generate.
  • The Data Scraping wizard threw an error if you tried to scrape nested tables in Internet Explorer.
  • The Click activity with the SimulateClick property enabled would improperly interact with particular web page elements in Internet Explorer.
  • Selectors were erroneously generated when using the SAP Business Client (NetWeaver).
  • The Type Into activity with the SimulateType property enabled would not always properly type inside fields on the Orchestrator login page.
  • Fixed an issue which caused Click Image to throw an exception when used after a Find Image activity.
  • In some cases, the Click activity would not accurately identify web page elements which were not in view.
  • Particular keyboard input events were erroneously flagged by the Type Into with the SimulateType property enabled.
  • In Java apps, selectors were improperly built for contextual menu items.
  • Selecting CSS elements from a web page in Internet Explorer would return an error.
  • Selectors could not be properly generated by UI Explorer for particular Java apps. In some situations, this would cause the Java app to stop working.
  • When throwing an exception, the Send Hotkey activity caused the CTRL key to remain stuck.
  • Studio froze when using UiExplorer with an instance of Internet Explorer that had Enhanced Protected Mode enabled.
  • Hovering or Indicating on Screen in a PowerShell console window caused Studio to crash.


  • Uninstalling Orchestrator now removes the entire contents of the Activities folder, even if it contains custom files.
  • To ensure a smooth experience in offline environments, the list of activity dependencies has been updated in all our installers. Please note that as a result, the size of the artifacts has increased.
  • An error message was displayed if you closed the UiPathPlatformInstaller.exe wizard while the installation process was being executed.
  • Fixes an issue that prevented UiPathOrchestrator.msi from preserving your custom location, website and application pool names. Starting with v2019 Fast Track, all future updates of Orchestrator keep your previous custom values.

Activities Versions

The following activity packages and versions are included in the installers and are added as dependencies, by default, to a newly created project in Studio:

  • UiPath.Excel.Activities - v2.5.3
  • UiPath.Mail.Activities - v1.4.0
  • UiPath.System.Activities - v19.4.0
  • UiPath.UIAutomation.Activities - v19.4.1

Updated 4 months ago

2019 FastTrack (2019.4.2)

Suggested Edits are limited on API Reference Pages

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