UiPath Release Notes

UiPath Release Notes


Release date: 20th January 2020

What’s New

We’ve heard your voice and worked hard to bring a lot of bug fixes and to smoothen your automation experience with this latest patch for our LTS release.


With this release we are excited to introduce you to the newest member of the UiPath family, Insights. A powerful embedded analytics solution integrated within Orchestrator at the tenant level, Insights helps you measure, optimize and scale your RPA operations and its impact to your business.

Gain operational awareness with a library of out of the box dashboards, customizable with any combination of widgets and/or filters. Dashboards can be shared with any or all users of the Orchestrator tenant, enabling company-wide visibility while continuing to work from the same dataset and without impacting your original dashboards.

Using the Pulse feature in Insights, you can stay up-to-date with the current status of your RPA deployment’s most important metrics and receive alerts of any errors or anomalies.


Originally introduced as a Preview feature, Folders are officially here to stay! Learn all about the administration of modern folders and how you can use them to manage large deployments.



We’re introducing new Workflow Analyzer rules: Argument Length Exceeded, Empty Workflow, and SecureString Argument.

In addition, several existing rules have been updated with default values. The Undefined Output Properties rule now has a number of activities that are excluded by default. You can add your own to the list.

The Nested If Clauses rule now has an editable default threshold of 3, and the Hardcoded Activity Arguments rule now checks a number of activities by default and more can be added.

Workflow Analyzer rules also received the option to reset default values to default. Right-click a rule in the Project Settings window and click Reset to Default.

When validating or analyzing a process containing activities from unresolved dependencies, the Error List panel now displays a recommendation along with the error. A link to the documentation with more information is also provided. Learn more about the Error List panel here.

Information from Project Anatomy Rules can now be expanded in the Error List panel. This means that the list of activities gathered by the File Activities Stats rule can be expanded in the panel.

The default behavior of the Global Exception Handler has changed. By default, the template is triggered once per exception and is retried 3 times before aborting the execution. The Abort option now throws the initial exception. Learn more here.

Variables, Workflow Arguments, and Activity Properties used in a workflow are now displayed under the corresponding property of the errorInfo argument when the workflow is ran in debug mode using the Global Exception Handler.

Processes can be marked as Background or Orchestration by toggling the Background Process and Supports Persistence options in the Project Settings window. Learn more about this here.

The Shift + Enter adds a new line under the inputted value of an activity, while the Ctrl + Enter shortcut adds a new line above the inputted value both in the Designer and Properties panels. Use Enter shortcut to set the inputted value in the activity. Read more about this here.

Processes and queues are now ordered alphabetically in the Orchestrator Resources panel. Read more about this panel here.

Studio supports integration with both Azure DevOps Server and Azure DevOps Services. Learn more about this here.

Git integration in Studio now supports proxy server configuration. Read more about this here.

The layout of panels available during debugging is reset after upgrading Studio.

The values of complex objects lists of strings or dictionary variables can now be monitored during debugging from the Watch panel. Learn more about this panel here.

We’ve made some slight UI changes to items in the Locals panel which are now slimmer. In addition, editable resources are now marked with a specific icon. Learn more about the Locals panel here.

Studio is now compliant with Section 508 Accessibility Level A.


So as to better label Robots that do not rely on an Orchestrator license, all license source fields in Orchestrator that depict this concept have been renamed using the Stand-alone notion.

We added a new web.config parameter which allows you to read logs from targets that aren't necessarily used to write logs into, namely Logs.RobotLogs.ReadTarget. We did this for those of you who use different methods to push logs other than through the writeTo attribute.

In this release, a new web.config parameter has been added which enables you to convert local users that log in with AD credentials into directory users: WindowsAuth.ConvertUsersAtLogin. Details here. Since this parameter doesn’t make changes retroactively, we also put together a script to convert all local users that have ever logged in with AD credentials into directory users at once. See it here.

Changes made to AD group membership are now reflected in the Robot tray after each successful Robot connection or once every hour. This value can be changed using the WindowsAuth.GroupMembershipCacheExpireHours parameter in web.config.

Active Directory users and groups can now be assigned to folders without first having been added globally as Orchestrator users. See how here.

To make searching for an AD user or group quicker and easier, we made a couple of tweaks to the original recipe to boost the performance and improve the overall experience. The highlights you need to remember:

  • We added a User Type drop-down which enables you to refine the query by selecting the type of entity you're searching for (user, group, or both)
  • We added three web.config parameters which enable you to make finer adjustments based on your needs: one to control the maximum number of results returned for a query, one to define the minimum query size which triggers the search, and one which limits the search duration. Details about all three here.

Making an authenticated API request using an Active Directory identity that belongs to a group which has been added in Orchestrator beforehand auto-provisions the user in your instance. Be aware of the fact that you cannot choose the tenant the user is auto-provisioned on, so if he belongs to multiple tenants, auto-provisioning takes place on one of them only.

We made some tweaks to the logic behind the job ordering mechanism in Orchestrator so as to optimize the execution in some corner cases. More precisely, jobs are now added to the workload and then executed based on their creation time. This is valid regardless of the execution target. Since we’re here, you should also know that we improved the performance when using dynamic allocation.

The User Permissions window has been enhanced to make it easier to assess what permissions your user has been granted on a per folder basis, and whether they have been explicitly assigned or inherited from the tenant.

The Include Subfolders option is now also available for the SLA page as well, such that you can select if the contents of any existing subfolders are included or not when monitoring your queues.

Managing your organization and deployment using modern folders is made easier as you can now automatically create roles for each type of user. See the corresponding permissions for each available role here.

Having in mind to offer you a more intuitive user experience, we've revamped the Non-Working Days tab in the Settings page. As a result, now the calendars are alphabetically ordered, the selected calendar is clearly marked, and the buttons have tooltips.

All alert messages now contain the full folder path to help you easily identify where the error occurred.


As part of our further development of the Workflow Analyzer, we have implemented specific Rules for the UIAutomation activities package in this release. You can find out more by viewing the documentation here.

Known Issues


Libraries containing .xaml files invoked from parent folders cannot be published. There are two workarounds available, either move both files to the same folder or level, or switch to the legacy libraries compiler. More about this is available here.

The Open a Local Project and Open Recent options in Studio Backstage view are greyed out when closing an unsaved project with modifications to several xamlfiles.

The Select and Deselect All options work improperly when applying a filter in the Add new service wizard.



  • If using a self-signed certificate, Insights is inaccessible from Firefox unless you explicitly select to continue to the site. See here for details.
  • When performing a new installation of Insights and Orchestrator with Insights feature enabled against a SQL database where Insights was previously installed and configured, the Orchestrator will display an error when the Insights page is accessed. This is corrected by running the UiPath.InsightsTenantAdminTool.exe as detailed here.
  • When performing a modify/repair installation to your existing Insights deployment, entering the wrong credentials for the Insights admin user will lock the account and render it inaccessible for 10 minutes.
  • When configuring a Pivot widget, if a large set of row values is set as columns this can result in both Orchestrator and Insights freezing, which can only be corrected by restarting the browser.
  • Changes in the Orchestrator localization settings are not propagated to the Insights Portal until you logout and back in to Orchestrator.
  • Some modifications to the processes and/or queues whose data is displayed on any dashboard may result in that dashboard’s temporary unavailability. See here for details.
  • Creating and editing of dashboards on a low-resolution display does not display the full range of controls unless you zoom out.
  • Process workflows where all custom log fields are removed during execution are not ingested into the Insights database. See here to read about considerations when designing workflows for Insights.
  • Insights users with the same email address used across multiple Orchestrator tenants have access to data from across all of those tenants.

Bug Fixes


  • Upgrades from v19.4.5 or earlier would fail during license migration on machines where the language was set to Japanese.
  • The CHROME_POLICY_INSTALL_TYPE parameters were not validated during command-line installations.
  • Fixed an issue that prevented the Intellisense prompt in Expression Editor from closing after pressing the Esc keyboard shortcut.
  • If during debugging, an activity triggers an error after the execution had exited a container, the Continue button was not visible after clicking it once.
  • The Prefix Datatable Arguments and Arguments Naming Convention rules have been updated to better check for DataTable arguments with the dt abbreviation as part of their names.
  • Fixed an issue that caused the Unused Variables rule to display a false positive warning when a variable was actually used in a Flow Decision activity part of a flowchart.
  • If a custom feed contained an invalid package, all other packages in the feed were not visible. Now, an error message is displayed in the Manage Packages window. It is recommended to fix or remove the corrupted .nupkg package and reopen the Manage Packages window to view all packages in the feed.
  • Fixed an issue that prevented some projects from being opened in Studio on environments with certain OS configurations.
  • Fixed an issue that prevented libraries with the same name as the imported web service from being published in Studio.
  • Fixed an issue that triggered an error when copying a flowchart into another flowchart.
  • Studio no longer throws an exception when trying to open an invoked workflow that was previously removed from the project.
  • We’ve fixed some performance issues to make Studio more stable and reduce the loading time of processes and libraries.
  • Files from the .screenshots folder were not added to source control when using the Copy to Git option.
  • Dictionary Key and Value types were not evaluated, but the value of the dictionary object itself was when used with Create Test Bench action.
  • If the Orchestrator URL is changed in the Robot tray, Studio automatically refreshes the assets from Orchestrator.
  • If the user has no access rights or read-only access rights to a GIT repository, they are now prompted to add new credentials in order to correctly push to the remote repository.
  • When trying to commit a file with the same name as one that exists in the remote repository, Studio now opens the Solve Conflicts window, notifying the user to select the desired version of the file.
  • In the Orchestrator Resources panel, both the dropdown for selecting the folder and the status bar display long folder names as truncated. If the user hovers over the name, the tooltip reveals the full length/subfolders of the selected Orchestrator Folder.
  • Fixed an issue that caused activities from the UiPath.Persistence.Activities package to incorrectly execute when used with the Create Test Bench feature.
  • Fixed an issue that prevented the Watch panel from evaluating arguments during the execution if Step Into was used.
  • Fixed an issue that prevented Studio from importing a process from a previously checked out TFS project.
  • Clicking the Taxonomy Manager button now opens the Taxonomy Manager screen, when no .xaml file is opened in the Designer.


  • Fixed an issue which rendered the Platform Installer unable to be removed via Windows’ Apps & features nor the UiPathPlatformInstaller.exe wizard if a localized Studio or Remote Runtime component (other than English) was installed or updated via the UiPathPlatformInstaller.exe on that machine.
  • The UiPathPlatformInstaller.exe did not properly check that prerequisites are met prior to beginning installation.
  • The UiPathPlatformInstaller.exe failed if a SQL database name greater than 123 characters was entered. A character limit is now imposed to prevent this error.


  • Upon upgrading your existing Orchestrator instance to v2019.10, certain scenarios occurred in which organization units were not properly displayed as the equivalent classic folders, thus rendering Orchestrator unusable. Specifically, if you had multiple OU's in a previous Orchestrator version, and deleted at least one which had a user assigned to it, the folder correspondents of the remaining units were not visible to the respective user after migrating.
  • Users assigned to non-sequential folders in a hierarchy (e.g. Root and Subfolder 6) were unable to access the intermediate folders.
  • Fixed an issue where the folder structure (i.e. root and subfolders) was not taken into consideration for the alphabetical ordering of the Folders list. For example, with root folders Accounting and Accounting & Finance, where Accounting has subfolders Payroll and Reports, Accounting & Finance was displayed directly under Accounting rather than it's subfolders.
  • The Robot column was not populated for transaction items processed by Robots in modern folders. As of now, the column displays the user associated to Robot which processed the items.
  • Users with Create permissions on Subfolders were unable to create any subfolders unless they were also granted Create permission on Folders.
  • Having a large number of Robots (in the order of thousands) in a single environment caused a significant performance degradation when dealing with processes. We improved the logic around process handling to prevent that from happening.
  • We identified and fixed an issue related to the permissions required to configure automatic robot creation, and to receive alerts on robot status changes.
  • The roles and folders inherited by a directory user at login time were not audited.
  • Alerts concerning automatically provisioned Robots in classic folders did not contain the Robot name.
  • Exceptions were thrown in Event Viewer when you tried to open the Alert Details window for alerts on transactions not contained in the currently active folder. As a result, the Show Details button has been disabled for transaction alerts in this scenario. Switch to the containing folder to see the alerts that have been generated.
  • On the Logs page, filtering by User did not allow for local users and incorrectly enforced case-sensitive searching.
  • We identified an issue with the disabling time of a queue trigger when also having a time trigger associated to that same queue. This only occurred if the latter had been configured to get disabled 15 minutes earlier than the first one. Say I defined a time trigger for a queue to get disabled at 10:00 o'clock, and a queue trigger for the same queue which should get disabled at 10:15. What happened is that the queue trigger got disabled at 10:00 instead of 10:15.
  • The values of input and output parameters defined when creating a queue trigger were reset to their defaults when editing the trigger.
  • Output and Analytics schema validation interfered with the retry mechanism of failed transactions.
  • For Queues with schemas enforced for Output and/or Analytics data, queue items that contained no Output and/or Analytics parameters were nonetheless processed successfully.
  • Schemas using the root definition rather than draft-07 were detected as invalid.
  • When editing or cloning queue items, the new item postpone or due date was entered in UTC rather than the time zone configured for the tenant.
  • The job.started webhook event was not sent to an external system for jobs started from the Robot tray.
  • Various error messages where displayed when you searched for a directory group or user on the Add Directory User or Group window using special characters such as &, #, (, ).
  • If the Orchestrator to Redis connection was down, an error loop would occur where Orchestrator was inaccessible.
  • The Connection String was not properly displayed in the Settings page, as it contained two slashes (/).
  • Fixed an issue that prevented you from downloading the Orchestrator offline activation request file if you were using Internet Explorer.
  • Occasionally, a blank page was displayed when trying to authenticate via Windows Authentication on Google Chrome.
  • It is now possible to remove a license at tenant level if it was initially uploaded at host level.
  • The Interval filter for the Jobs page did not work properly if you used a time zone different than UTC.
  • It was not possible to update a host license a second time if you upgraded your Orchestrator instance to 2019.10.x from an unsupported version such as 2018.3.x.
  • Auto-provisioned users could not be assigned to tasks in a folder despite belonging to an AD group which had access to it, unless they had been explicitly granted permissions to the respective folder. See here details about assigning a task to a user.
  • The ProvisionType parameter was required when making POST requests to the /odata/Robots endpoint. We fixed it so that’s no longer the case.
  • You could not use Orchestrator if Active Directory was unreachable, even if it was deployed on a machine that was not an Active Directory member.
  • When deactivating the license of your offline Orchestrator instance, Orchestrator would remain licensed until an internet connection was enabled.

Non-Working Days

  • If a trigger had a calendar attached to it and the tenant's timezone was changed after calendar creation, then you couldn't edit the trigger unless you first changed its timezone to match that of the tenant.
  • The calendars are displayed correctly now in Firefox.
  • While using Internet Explorer, you couldn't add new calendars within tenants that had no previously defined ones.
  • There were two Save and Delete buttons for each calendar. To avoid confusion, we've reworked the UI, leaving only one of each type. Now the Save button enables you to update both the name and the dates of any selected calendar, while the Delete button removes the calendar entirely.
  • Switching between calendars or adding new ones didn't default the view to the current month when the previously selected calendar had dates in another month.
  • You couldn't save a calendar if you've previously entered more than the maximum limit of characters allowed for its name, even after shortening the name.
  • For tenants with a timezone different than the default (UTC) Coordinated Universal Time, the dates uploaded to a calendar via .csv files were incorrectly displayed with a difference of minus one day.
  • The dates uploaded into calendars through .csv files were not saved.


  • Fixed an issue that was causing the Validation Station wizard to display incorrectly the table preferences, when using the Extract new table option.
  • Fixed an issue that was returning an error when Validation Station wizard was run with Callout activity chained before or after it. Now, the activity runs as expected.
  • Fixed an issue that was causing the Data Extraction Scope activity to throw an error when it was run with a customized machine culture and the FormatValuesIfPossible option selected. Now, the activity runs as expected.
  • Fixed an issue that was causing some performance issues when large amounts of text were selected in the Text View option of the Validation Station wizard. Now, the Text View option displays the text as expected.
  • Fixed an issue that was causing the Data Extraction Scope activity to throw an error when it was run with an extractor without an internal taxonomy set and a new field was added in the project’s taxonomy. Now, the activity runs as expected.
  • On certain machines, rotated documents were not displayed properly when using the Validation Station.


  • Text was not written in Chrome by the Type Into activity used with the SimulateType property enabled.
  • Fixed an issue which caused inconsistent interactive selection behavior because of high latency over a RFP connection.

Bundling Details

The following patch versions are bundled in the UiPathPlatform.exe installer:

  • Studio & Robot - 2019.10.3
  • Orchestrator - 2019.10.16
  • Remote Runtime – 19.10.7312.25504

The following activity packages and versions are included in the .msi installer and can be found in the local feed. Packs marked with an asterisk (*) are added as dependencies, by default, to a newly created project in Studio:

Activity Pack













Updated 24 days ago


Suggested Edits are limited on API Reference Pages

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