2019.10.3 LTS Patch Release

2019.10.3 LTS Patch Release

The latest 2019.10.3 Platform patch is out. We’ve heard your voice and worked hard to bring a lot of bug fixes and to smoothen your automation experience. The patch is available both for Enterprise and Community users. If you’re a Community user, simply go to UiPath Cloud Platform to download the Stable Community version.

Without further ado, here’s what’s cooking in the 2019.10.3 patch.



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.

Please use the new Insights category for any questions or suggestions regarding the new product.

(Not available for Community Edition)


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.

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.

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

AD Integration Improvements

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.

Making an authenticated API request using an Active Directory identity that belongs to a group which exists in Orchestrator 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.

(Not available for Community Edition)


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.

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.

The User Permissions window has been subtly 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.

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.


Workflow Analyzer

Workflow Analyzer now comes with a number of built-in Studio rules, together with rules integrated directly in the UIAutomation.Activities package.

We’ve also introduced the option to Reset to Default for rules that have default values or thresholds. Simply right-click a rule in the Project Settings window and click Reset to Default.

New Workflow Analyzer rules in Studio:

  • Argument Length Exceeded: This rule checks whether the name of each argument defined in the workflow exceeds a certain number of characters.

  • Empty Workflow: Checks whether the project contains empty workflow files, including empty sequences, flowcharts, or state machines.

  • SecureString Argument: Checks whether the SecureString type is misused in the workflow. This string type is used when avoiding to store potentially sensitive strings as plain text.

Improvements to existing Studio rules:

Now, when Workflow Analyzer validates or analyzes a process containing activities from unresolved dependencies, it also displays a recommendation and a link to documentation for more info.

Info gathered 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.

UIAutomation Rules

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.

Debugging Improvements

Aside from these, we’re also bringing a slimmer UI for the Locals panel, and editable items are marked with a specific icon. When debugging is paused, certain values may be edited.

The behavior of the Global Exception Handler has been improved and the template now retries the exception 3 times before the execution is aborted. Moreover, variables, workflow arguments, and activity properties are displayed under the errorInfo argument.

Speaking of debugging enhancements, values of complex objects lists of strings or dictionary variables can now be monitored during debugging from the Watch panel.

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

Proxy Server Configuration for Git

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

Orchestrator Resources Panel

Processes and queues are now ordered alphabetically in the Orchestrator Resources panel.

Keyboard Shortcuts

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 both in the Designer and Properties panels. Use Enter shortcut to set the inputted value in the activity. Read more about this here.

Mark Processes as Background or Orchestration

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.


Whatever is cooking , looks Delicious :yum::yum::yum:


Good job… :clap: :clap:


Awesome work guys!!! Keep being awesome!!

We as the community, will do everything possible from our end to support UiPath to be awesome!! :smiley:


Great work UiPath Team :ok_hand: :ok_hand: :ok_hand:


Awesome Patch update!!!

Loved the features updates added :slight_smile:


finally has toggle for background process


awesome … :heart_eyes: :heart_eyes: :heart_eyes:

1 Like

The plus icon that you can click on to add an activity between two activities has disappeared when my version updated to 2019.10.3. Anyone know if there is a way to bring it back?

1 Like

what a impressing mind blowing! :innocent: :heart_eyes: :smiling_face_with_three_hearts:
This will be a never ending loop :star_struck:

We will always with you , Lets bring UIPTH to World Top :revolving_hearts: :two_hearts: :gift_heart: :+1:

1 Like

After updating to 2019.10.3 I am not able to publish one specific library to Orchestartor: ArgumentNullException is raised (Parameter name: node). Though simply running the workflow from Studio gives no errors.

Switching back to previous release allowed me to publish the library flawlessly.

1 Like

Hi @KamKam, could you show us a screenshot? :slight_smile:

1 Like

@AmiD_FLice can you help us debbuging this issue ? If you can DM your project would be very helpful but also a print screen of the project panel to see your structure will also help.


new features are adorable :heart_eyes:


@loginerror @alexandra.vaidos Is it mandatory to use different server for orchestrator and Insights or is it recommended?


Hello @Shubhi, they must be on different servers. This is mentioned in the documentation here “Orchestrator and Insights must be installed on separate servers.”


Good work UiPath. Keep rocking :slight_smile:

1 Like

Hi there, it seems to have fixed itself when I booted up my pc this morning. Thnaks.

Good work. Does anyone has the git proxy thing running?
I did all like explained on https://docs.uipath.com/studio/docs/managing-projects-git
but this does not work.