UiPath 2019 Fast Track Preview (Community Edition v2019.4.0)

UiPath 2019 Fast Track Preview (Community Edition v2019.4.0)

In our final Community Preview before the major upcoming enterprise release, we bring you a taste :tongue: of the UiPath Platform’s new features. :dancer:

Our community is a driving force :mage: in shaping the way our product works, and that’s why, this month, you get to use the improvements included in the major April release. We hope to get as much feedback as possible from you.

If Studio is your poison :skull_and_crossbones:, you can check out all of the crazy new features our devs have been working on this month, or, if being a Robot mastermind :brain: fancies you more, you can manage all your Robots in the new Orchestrator. All in all, remember that if any feature makes you sad, you always have our shoulder to cry on.

What’s New


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.


From the makers of File Diff and Compare Files now comes Show History for displaying 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.

We are one step closer to ensuring a seamless integration across all UiPath platforms and products by transforming the Community feed into Go!. The feed now includes packages that were previously published on Go!. Learn more about this here.

Debugging Enhancements

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. Find out more 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, libraries here or when using command-line 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.


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.



The Copy to GIT option also made its way to Studio’s GIT integration offerings, allowing you to copy your current project to an existing GIT repository. Find out more about this here.

The Disconnect from GIT option in the Team page removes the subversion tag for the entire local GIT repository, including parent and child projects. Read more about this here.

The library Project Settings window now includes the toggle for Include Sources at publish. Get more information from here.

As part of our efforts to enrich the variety of global settings, we’ve added Default Locations in the Settings page. Now you can set default paths for all of your projects at once. Check out more info here.

Improvements were also brought to the project’s Dependency Tree. It is now easier to differentiate between resolved, unused, not found and best match dependencies. Check out this page to see details about this.

When comparing two project.json files using File Diff or Compare Files, the dependencies are sorted alphabetically to make them easier to find and read. Find out more about this here and here.

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

Last but not least, we’re glad to announce that Dark theme is now a full-fledged feature in Studio. The Beta label from Settings > Theme> Dark has been removed, meaning that it has reached the high standard enforced for all our other features.


Get things done even faster by assigning Global Keyboard Shortcuts to any of your processes. This way, you can start any process at the press of a button, literally! You can easily configure them as explained on this page.

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.

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.

Building upon our previous release, the UiPathODataSvc.BulkAddQueueItems endpoint now has two new parameters, ProcessAllIndependently and AllOrNothing, which help you build an upload strategy. An example is available here.

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.

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

Known Issues


  • 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 package web services files. More details about this are available here.


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

Bug Fixes


  • From now on, the nasty licensing error Cannot use Community Edition on this machine after activating a trial or Enterprise is gone. So if you used a Trial key before and were unable to use Community Edition after it expired, go get your hands on the latest Studio 2019.4: https://www.uipath.com/developers/community-edition-download

  • Fixed an issue that prevented the Locals and Output panels from being expanded by default during debugging.

  • Fixed an issue that caused breakpoints set in an invoked workflow to be ignored at debugging, unless the invoked .xaml files were opened in the Designer panel.

  • Fixed an issue that caused user-defined feeds to be disabled when upgrading an Enterprise licensed Studio using a Windows installer (.exe).

  • Fixed an issue that prevented you from adding dependencies or making project changes after resuming connection to a project hosted on a network drive.

  • Studio no longer hangs when trying to checkout a GIT branch that contains an automation project with unresolved dependencies.

  • Breakpoints set on recursive sequences persist when the automation project is reopened.

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


  • Using the -pack command on a library with dependencies on a tenant’s private feed would prevent it from being downloaded on the Robot machine due to insufficient privileges.

  • Stopping the Robot Service during a process execution initiated from Orchestrator would provide misleading job state information.


  • Robots could not download packages if you updated the tenant name using a PATCH call to the /odata/Tenants(id) endpoint.

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

  • The Application Pool stopped if you uploaded multiple versions of the same package in environments that used the Azure, AWS, or Minio blob storage.

  • The performance of disabling a tenant has been optimized, especially when dealing with a large number of users.

  • We identified and fixed an issue that prevented schedules from triggering correctly.

  • Occasionally, due to a dynamic allocation issue, Robots stopped executing jobs assigned dynamically, and remained stuck in a pending state.

  • At host level, the Tenant drop-down on the License Usage section displayed the same tenant name multiple times and occasionally stopped loading all the entries.

  • An error message was displayed when you tried to configure and save email settings for new tenants.

  • Whenever you downloaded execution media, the corresponding Download action was displayed twice on the Audit page.

  • The Show release notes and Download library buttons were disabled for libraries, unless you had View permissions on Processes. This occurred despite having all permissions on Libraries granted.

  • The Enable Recording option got disabled if you edited input parameters for a process in Orchestrator.

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

  • Daily alert emails and periodic error emails were not sent if the email settings were configured at tenant level exclusively.

  • Notifications were not sent after an upgrade, unless you restarted your Orchestrator instance first.

  • An error message was displayed when you tried to create an asset of type Bool, if its name contained Japanese characters.

  • An error message was occasionally displayed when you clicked the Robots or Jobs chart on the Dashboard page.

  • The Administrator and Robot roles did not have the corresponding default permissions on Execution Media after an upgrade.

  • The User menu now correctly displays the username or name and surname, instead of the tenant name followed by the username.

  • The NuGetStorage folder was removed after updating an Orchestrator Azure instance that used the Composite repository type.

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

  • UiPath.Mail.Activities - v1.3.0

  • UiPath.System.Activities - v19.3.0

  • UiPath.UIAutomation.Activities - v19.3.0

See below for all release notes for UiPath 2019 Fast Track Preview:


A post was split to a new topic: Could not load type ‘UiPath.Vision.Core.NeuralNet.DetectControlsResponse’ from assembly 'UiPath.Vision.Core