UiPath Release Notes

Release date: 22nd October 2018

What’s New

The third release of this year puts a great emphasis on a central component of UiPath Platform, Studio. Thus, Studio gets some very appealing UI changes, important features in terms of project control and component reusability, as well as various enhancements under the hood. The focus has been on redesigning the Studio architecture and setting the building blocks for a more appealing and reliable Studio, in a continuous effort to increase developer productivity and efficiency.

With this in mind, Studio now comes with a reduced start-up time and improved reliability, together with optimized resource consumption.

Another important announcement that we want to share with you is that UiPath Robot and Studio are now Ready for Citrix. This coupled with the scalability improvements we made in this release, we are sure you're gonna love it. To view all the Citrix environments that UiPath has proven compatibility with at a glance, visit this page.

Reliability & Change Management

In an effort to enhance agility in developing automations and process execution, Studio now brings dependencies per project. Compared to previous versions, activity packages can now be installed for each project specifically, making it easier to control the usage of your automation. Dependencies thus become highly contextual and specific to each project. As a result, upon creating a new project in Studio, the activity packages that are actually needed for workflows can be added from the Manage Packages window. Optionally, you can add any other pack.

Because activity packages have multiple versions, Runtime Rules were set in place, to select which version to use at design or execution time. For more information on these rules, please take a look at the documentation.

The Core Activities Package is now split into two distinct packs: UIAutomation and System. The first contains all the activities that mimic human interaction, such as Click or Type Into, while the latter sums up all the blocks required for building an automation, from invoking another workflow to logging a custom message in Orchestrator.

This change was made so that both in present and future versions, you can reference any version of the UIAutomation and System packages as dependencies for your projects, completely independent of Studio. This is a step forward for being able to update UiPath Platform components without worrying about how they affect your automations. For more information, check the documentation.

As part of the Studio UI and functionality upgrade, the Package Manager now shows the list of dependencies linked to the current project. The Package Manager window offers a seamless navigation among custom and UiPath official feeds. More details are available here.


To increase productivity and improve interoperability, Studio now allows for creating and publishing reusable components in the form of a library. Specifically, such projects can now be published as a .nupkg package, which can then be used as an activity in multiple processes. A Library has its own editable version number and Release Notes, and can be published to Orchestrator, a custom feed or the local machine. More details are available here.

In Orchestrator, this implies a centralized location where libraries are stored with the purpose of being further used and shared across tenants and teams effortlessly. Library management - upload and download - is done at host level from the Libraries page with the click of a button. For more information, click here.

Release notes added to better keep track of changes made in-between package versions are available in Orchestrator, both at library and package levels. For more information, click here.

We have exposed the input and output arguments you are already used to in Studio, as a way to seamlessly integrate the tools you use, such as various DCMs or BPMs. This means that any process you create can now receive input parameters through the Orchestrator API or interface, as well as return an output to all of the aforementioned. Last but not least, this is a stepping stone in linking processes together. This extensibility helps you better integrate UiPath in your company’s ecosystem. For more information, please see the documentation.

Being one of the most used programming languages, we have now integrated Java into our product in the form of some new activities. This new addition to our ever-growing pool of languages enables you to invoke your already existing Java code directly from UiPath. The Java Activities Pack features six new activities and a proprietary variable, JavaObject, that help you harness the full power of Java into your automation projects. You can find out more about this package here.


The feature you’ve all been waiting for has arrived - Attended Floating Robots support! Create and configure your own Attended Floating Robots and connect to them from any defined machine in the blink of an eye. Since the machine name is not relevant for the Floating Robots scenario, we created a type of entity that fits the new requirements, the Machine Template. A template enables an AD user to use any machine, as long as the Robot uses the key generated at the template level and the aforementioned username. This scenario goes hand in hand with Non-Persistent VDIs, thus ensuring overall better resource management. On top of that, templates do wonders for hotseat environments, so people working in shifts on the same computer have a smoother than ever experience.

To make things even better, a Floating Robot connects automatically to Orchestrator when you open the Robot tray. For more information, click here.

In order to make it easier for you to keep track of your Robots and Machines, the Robots’ versions are now displayed on the Machines page.

We’ve also made it possible to distribute and reallocate licenses to your tenants with just a few clicks and without the hassle of contacting our support team. The new process consists in uploading a single license file which aggregates multiple Robot licenses, which can then be allocated from a centralized location according to your requirements without any other additional steps or unnecessary delays. For more information, click here.

To facilitate license usage monitoring, we have brought to you the possibility to check historical licensing data. The historical graph in question is available on the License page, both at host and tenant level, and it shows the maximum number of licenses used concurrently by each type of Robot. This way, you can easily assess if there’s room for maximizing license efficiency or not. You can also filter out data or adjust the time interval as desired. Last but not least, you can now configure permissions per user for the License page. For more information on how to do that, click here.

As a way to maximize your results in terms of Robot utilization, we made it possible to add jobs to environments. This means that a job from the environment is automatically assigned to any available Robot instead of being placed into the queue of busy Robots. For more information on how to do that, click here.


The moment is finally here - the entire UiPath Platform has been localized, so that you can have a truly immersive experience, from install to design and execution. Now, besides English, you can access everything, including our online documentation, in Japanese.

If you worry about your long-run schedules during public holidays, weekends or any other day on which normal business is not transacted, we’ve got you covered. You are now able to define a list of non-business days on which schedules do not run. For more information about this functionality and how to use it, click here.

On top of that, to further improve scheduling flexibility, you are able to set a date and time on which schedules get automatically disabled. For more information about this functionality and how to use it, click here.

The efficiency of workflow debugging has been improved! The debugger now stops before executing the activity, and the behavior of Step Into and Step Over has been improved. In addition to this, breakpoints can be toggled from the activity context menu. For more information, click here.

This release also brings a better user experience and more reliable integration with version control systems. The new Team tab in the Studio Backstage View hosts the tools for connecting to SVN and TFS version control systems, making it easier to add, check in and check out the latest project version from the repository. For more information on how to do that, check the documentation.

Office Integration

Excel is one of the most common data manipulation software, and one of our main focuses in this release is increasing the power you have upon it in UiPath. This brings a major update to the Excel Activities Package, which features 14 new activities. Below you can find some of the most requested ones:

  • Copy Paste Range - Copies an entire range, including values, formulas, table format, and cell format, and pastes it to a specified sheet.
  • Insert/Delete Rows - Adds or removes a specified number of rows at a certain position.
  • Auto Fill Range - Takes the formulas defined in the rule range and adapts them to the end range, mimicking the Autofill functionality in Excel.
  • Delete Range - Deletes a specified range in an Excel workbook. Can also be used to shift an entire row or column.
  • Copy Sheet - Copies a sheet from a specified workbook and pastes it to another workbook. If no other workbook is specified, it is copied to the source file.
  • Create Table - Creates a table from a specified range.
  • LookUp Range - Searches in a specified range for the coordinates of a cell with a certain value and returns them as String variables.

Also, the new PreserveFormat property check box enables the Read Cell, Read Column, Read Row, and Read Range activities keep the formatting of cells they work with, whether it's currency, date, or anything else.

The ReadOnly property has been added to the Excel Application Scope activity, enabling data extraction operations on workbooks that are locked for editing or have an edit password.

This release rounds off the edges of the Word Activities Package by adding two new activities:

  • Replace Picture - Identifies all the occurrences of a given picture according to its Alt Text in a Word document and replaces them with another specified image.
  • Insert DataTable - Inserts a table generated from a DataTable variable in a Word document. The table is created at a position relative to a specified text or bookmark.

Last but not least, the Send Outlook Mail Message activity now supports sending dynamic attachments.

Attended Automation

With attended automation in mind, the new Custom Input activity helps you gather data from a user through a custom HTML input form at any point in the execution of a workflow and then use it later on. For more info, check the docs.

As another addition to the suite of attended automation feats, we have created the Block User Input activity, which can disable your mouse and keyboard during the execution of a UI Automation process, making sure the Robot execution is not affected by the user that supervises the automation.

Processes are easier to find thanks to the newly added search function. Furthermore, the Robot Tray has become more flexible, literally. It's possible to resize and drag the Tray window as you see fit.

The Robot Agent (Tray) status bar displays clearer messages for connectivity and licensing. These are displayed and are as follows:

  • Connected, licensed - when the Robot is connected and licensed. Congrats, you have it all!
  • Connected, Unlicensed - when the Robot is connected, but there are no available licenses for it.
  • Robot unavailable - when there is no registered Robot, or you don't have an active license or a floating Robot is already in use on a different machine.

The UiPath Robot now makes it possible to switch between multiple Orchestrator instances upon connection. The Orchestrator URL and Machine Key fields save the info for more flexibility and faster connection to Orchestrator.


In this section, we refer to activities that specifically concern our community. Please refer to our GitHub repo and feel free to contribute at this link.

GDPR has been our favorite pastime lately, so we understand the importance of securing operational data. The new Cryptography Activities Package comes to meet this necessity, by offering some activities that feature state-of-the-art encryption algorithms:

  • Encrypt Text - Encrypts a string with a key, based on a specified key encoding and algorithm.
  • Decrypt Text - Decrypts a string, based on a specified key encoding and algorithm.
  • Encrypt File - Encrypts a file with a key, based on a specified key encoding and algorithm.
  • Decrypt File - Decrypts a file, based on a specified key encoding and algorithm.
  • Hash Text - Hashes a string using a specified algorithm and encoding format.
  • Hash File - Hashes a file using a specified algorithm.
  • Hash Text With Key - Hashes a string with a key, using a specified algorithm and encoding format.
  • Hash File With Key - Hashes a file with a key, using a specified algorithm and encoding format.

Compatibility Matrix

The following table lists what version of Robot and Studio works with what version of Orchestrator.

Please note that by not upgrading to the latest available version you are not taking advantage of the newest features or bug fixes added in our releases.

Orchestrator v2018.3
Orchestrator v2018.2
Orchestrator v2018.1
Orchestrator v2017.1
Orchestrator v2016.2

Robot v2018.3






Robot v2018.2






Robot v2018.1






Robot v2017.1






Robot v2016.2








Several improvements are also implemented for selectors and the UI Explorer. Selector Editor and UI Explorer now have enhanced functionality regarding Partial Selectors, as the current validation state of the selector is displayed. Selector Editor also comes both with a feature for highlighting a selected element and a Repair functionality for building more reliable selectors. For more information on these rules, please take a look at the documentation.

Robot in User Mode

Robots use the same key on a machine, so it's important to know the status of each Robot, and not just as a whole. Checking whether or not your Robots are alive and when is a must. As a result, the heartbeat is sent from each Robot, individually, even in High-Density environments. This also applies to Robots that are installed in user mode - not as a service. More details can be found in the online documentation.


Because we know agility and security are key factors in providing a high-quality product, we have made it possible for you to set an external feed for packages and custom activities. The feed can be secured either by defining basic authentication credentials or by using an API key. Choose and configure the option that suits you on the Deployment tab. For more information, click here.

In our neverending quest of having the most secure RPA platform out there, we made it easier to enable SSL encrypted connections between Orchestrator nodes and Redis. We changed the server, port, and password settings required in the web.config file to LoadBalancer.Redis.ConnectionString. If you're updating your Orchestrator to v2018.3, rest assured, we're going to take care of the conversion automatically.


As we know that some of you work in offline and highly controlled environments, we have added several improvements on how to deal with your Chrome extension installation. You can choose to set it up directly through the UiPath installer and you no longer need Internet access for it. The extension can be installed per machine or per user, and it is possible to also uninstall it from the command line. Please note that this is now distributed with the Studio/Robot installer. For more information, be sure to check the online documentation.

Java driver installations are now kept track of, so that each automation process running on that machine uses its appropriate Java version. The ScreenScrapeJavaSupport tool might help you more with your Java installations.


This release features a new activity called Join Data Tables, which extends our datatable manipulation arsenal. It enables you to combine columns from two tables by using values common to each other.

The Build Data Table activity has been revamped, offering a better overall user experience. You can now edit and restructure columns while using the Build Data Table wizard.

For easier utilization, the For Each and For Each Row activities now have a new property, called Index, which automatically counts the number of iterations the activity has passed through.

We understood your need for supporting machine learning models, so we have improved the Python Activities pack, adding support for Python x64.

The Key property of the Send Hotkey activity can now receive variables as input. This enables you to create variables for frequently used commands and simply add them to this property field, instead of rewriting the hotkey combination as a string each time the activity was used in the process.

To help you maximize the utilization of queue item information, we now provide the possibility to use the .Output, .DueDate, .DeferDate, and .RetryNo properties with the UiPath.Core.QueueItem variable in Studio. Consequently, you can add this data to a project's logic, for example, or use it to add more verification steps. Please note that the .Output property works only for successful transactions.


For a better user experience and in order to help you prevent the potential cluttering of Orchestrator, several alerts having Success and Info severities are no longer generated. At the same time, you now have the possibility to choose whether or not to receive alerts for specific categories. For more information, click here.

Installation and Update

The minimum .NET Framework version required to install the Robot, Studio and Orchestrator has been increased to 4.6.1.

To help you streamline the automatic deployment of the UiPath ecosystem on as many machines as you want, the UiPath Platform Windows Installer has been split in two: the first (UiPathStudio.msi) enables you to install and update Studio and/or Robot, while the other (UiPathOrchestrator.msi) deals with Orchestrator.

For those that still prefer the all-in-one approach, we did not forget about you: an executable file, UiPathPlatformInstaller.exe, bundles Studio, Robot, and Orchestrator, with all the options of both setups. More info about these installers is available here.

The Orchestrator Windows installer now checks if URL Rewrite is installed or not on the machine, to ensure that you have everything you need from the get-go. In addition, the Orchestrator Windows installer now also stops the IIS website when you update your Orchestrator instance, to avoid any requests that might be made during the installation process.

Another important enhancement that was brought to the Orchestrator setup is that all your configurations are retained, including the custom ones, if you update your instance to v2018.3.0. This allows for an easy, fast, and seamless transition. To read about all these changes, check out the installation and update topics.

Last but not least, for a performance boost in regards to large-scale deployments, please note that in multi-node installations of Orchestrator, the script automatically sets the session state to the same Redis instance used for caching. More information is available here.

User Experience and Performance

As it was a widely well-received feature, we now further extend the offline support for Robots to all types. This means that any Robot can now retain its license for a custom number of hours, keeping any possible downtime to a minimum. For more information on how to use it, please check the online documentation.

Packing a project can be done from the Robot CLI. The -pack command bundles the target project inside a .nupkg file which enables you to easily share your automation across continuous integration pipelines.

An UnknownType variable is now added to replace variables or arguments that might become undefined as a result of package removal or upgrade. This way, workflows with variables of missing types can be opened and edited in Studio. You can read more about this in our online documentation.

For a better handle of large scale Robot deployments in Orchestrator, we made it possible for you to customize how often the Robot and Orchestrator communicate. To read more, you can access this documentation page. Please note that you can make use of this functionality only with v2018.2.6 or v2018.3.1 Robots.

In order to have a better, ready to hand overview of your Orchestrator statistics, we made it possible for you to see the data behind each pie-chart component on the Dashboard by displaying their corresponding pages filtered accordingly. For example, if on the Robots chart, you click the slice corresponding to Disconnected Robots, the displayed Robots page has the Disconnected State filter automatically applied.

By using Connection String, you are now able to connect Robots provisioned on machines from any domain or subdomain to Orchestrator 2018.3. For more information, click here.

As a host administrator, you are now able to add custom HTML content to the Login page. The content is displayed right above the Login section. For more information, click here.

The Type column has been removed from the Environments page in order to avoid unnecessary ambiguity.

For the detail-oriented you, we made sure that exporting transaction items now also includes the Output and Exception Reason of each item.

In order to increase usability and ensure an easier management of existing users, the Units column is now displayed on the Users page if Organization Units are enabled.

To prevent confusion, the Runtime tab on the Add Robot window has been renamed to Settings.

The manner in which audit data is displayed has been improved to help you get all the info you need at a glance. Moreover, unnecessary details can be collapsed.

For an enhanced debugging experience and a more relevant categorization of logs, all error messages regarding business and validation rules are now displayed under a new event source, in Event Viewer, BusinessException, at Info level. For more information, check out the documentation.

Whenever a user is assigned to review an item, he receives an Info severity alert.

Server exceptions from Orchestrator, and the stack trace on the Job Details window, are logged and displayed in English, regardless of what language was chosen by the user.

To help you prevent potential cluttering of Orchestrator, you are now able to disable execution or debugging logs sent from Studio during development processes.

To keep things simple and avoid eventual confusion, the concept of environment type has been removed and is no longer displayed in the user interface. Rest assured, backward compatibility is still maintained as this option was not removed from the Orchestrator API. More information can be found here.

To avoid issues related to publishing processes, project names can no longer contain special characters.


Error handling is an important part in RPA, and as a result, we added error codes to each custom exception returned by the Orchestrator API.

Performance has been improved by implementing a bulk deletion feature which helps you remove a large number of robots without unnecessary delays. This has been implemented by adding a new endpoint, /Robots/UiPath.Server.Configuration.OData.DeleteBulk, in the Orchestrator API. You can find an example here.

To help you easily identify which Robots can execute a specific process, a new endpoint, /odata/Robots/UiPath.Server.Configuration.OData.GetRobotsForProcess, has been added to the Orchestrator API. An example of how you can make such a request is provided in the API guide.

Furthermore, it is now simpler to retrieve Per Robot assets, by using the new GetRobotAssetByRobotId endpoint. You can see an example request here.

Updating your password is now also possible through the /odata/Users/UiPath.Server.Configuration.OData.UpdatePassword endpoint, if you provide your credentials, as described in this example.

The GetRobotMappings and GetAssociatedProcesses endpoints have been deprecated. In their place, you can now use /api/RobotsService/StartService, and respectively /api/RobotsService/GetProcesses.

Breaking Changes


  • Activities packages UiPath.V7.Activities, UiPath.Platform.Activities, UiPath.Framework.Activities have been deprecated. UiPath.V7.Activities cannot be migrated, unlike the other two packages. Read more about this here.
  • The keyboardmappings.xml file has been removed. Rest assured, the keyboard shortcuts remain the same, but they are no longer customizable.


  • The following endpoints have been updated to accept OData query options:
    • /odata/Robots/UiPath.Server.Configuration.OData.GetUsernames();
    • /odata/Releases;
    • /odata/QueueProcessingRecords/UiPathODataSvc.RetrieveQueuesProcessingStatus();
    • /odata/Processes - Published is not filterable;
    • /odata/Processes/UiPath.Server.Configuration.OData.GetProcessVersions(processId='{processId}') - Published and IsActive are not filterable.
      Please note that these changes might affect any filters you have in place. For example, this is now the correct method of filtering packages according to their key - https://platform.uipath.com/odata/Processes?$filter=contains(Key, 'ItemsToQueue:1.0.6827.31677').
  • Leaving the NuGet.Activities.ApiKey parameter empty in web.config causes an error message to be displayed as the Activities feed stops working.
  • In order to use special characters in the SpecificContent parameter of POST requests to the odata/Queues/UiPathODataSvc.AddQueueItem and odata/Queues/UiPathODataSvc.AddTransactionItem endpoints, you need to first declare the concerned parameter as string, using the following format: "Parameter@odata.type": "#String". Please note that the corresponding activities handle special characters inherently.


  • When forwarding mails with the Send SMTP Mail Message activity, mails were not sent to the target recipient.

Known Issues


  • Libraries created in Studio cannot be published to Orchestrator versions prior to 2018.3.
  • If you connect multiple times to a remote desktop machine where Studio is running, some controls might not be properly displayed in Studio and the focus is lost, in rare cases.
  • In rare cases, if you connect to a remote desktop machine where Studio is running, Studio might crash after being left idle for a while.
  • If you manually update your Community Edition Studio using UiPathStudio.exe, the existing UiPath Chrome extension is removed from your browser. Please note that this does not occur if you enable the auto-update feature, as recommended.
  • Manually updating your Community Edition Studio might fail and cause the content of the current UiPath folder from %localappdata%\UiPath installation folder to be removed if you previously performed selections with UI Explorer in a Java application. This does not occur if you enable the auto-update feature, as recommended.
  • The Robot's connection to Orchestrator is lost if it is installed with the UiPathStudio.exe installer and during the update process you close Studio. This issue does not reproduce on installations that are licensed.
  • If you check out only the .xamlfile of a library project from the TFS repository, the .screenshots folder does not update. Use Get Latest Version on the screenshots folder to get the files.
  • Dependency cycles can occur if you name your project UiPath or any name of an existing package that you intend to add as a dependency. The same happens if you open a .xaml file from a folder named UiPath and it doesn’t have a project.json file.
  • The Start Menu shortcut for UiPathStudio.exe loses functionality after updating to v2018.3 with .NET version 4.5.2, and choosing not to install the minimum required 4.6.1 .NET version.
  • Indicate on Screen does not function if you open UI Explorer from the Studio install location in Windows 7 and 8.1.
  • The Workflow designer becomes invalid if the project contains a Flow Switch activity with a case whose value is "(empty)" and is not set to default. It is recommended to use a Flow Decision activity before the Flow Switch to check for empty strings, instead of using Flow Case for this.
  • Automation projects cannot be published if the project.json file is marked as read-only or if it’s located in a read-only location.
  • Release notes for activity packages and libraries are not visible in the Package Manager in Studio anymore. We are currently working with our technology partners to overcome this limitation in future Studio versions.
  • Shortcuts to commands can no longer be added to the Quick Access Toolbar in Studio. The functionality is scheduled to be reintroduced in future versions.


  • If you provision a Robot after the UiPath Robot service is already connected to Orchestrator, its version is displayed as unknown. For more information, please see this documentation page.
  • If you provide values for integer input parameters when making start job API calls which are also valid ASCII values, please note that they are changed. For example, 0065 becomes 53.
  • It is possible to create a schedule from the API which has both specific Robots and dynamic allocation parameters. However, please note that the ExecutorRobots parameter is ignored when the dynamic allocation one is used (StartStrategy).
  • The Robot fails to install packages if one of their dependencies is found in the Orchestrator cache bin but not physically on disk. This issue occurs if NuGet.EnableFileSystemMonitoring is set to false and you manually delete the dependency from the disk. Please note that it is recommended to make changes to such files through UiPath Platform.
  • The fields on the Security tab in the Settings page are not validated unless you firstly save a change on the tab. This occurs both at tenant and host levels.
  • Switching from an API key to basic authentication credentials when securing your external feed prevents processes from being displayed. This occurred when you used the same deployment URL. Restart your Orchestrator instance as a workaround.
  • A drop in performance is encountered when deploying more than 500 Attended Floating Robots on a single machine template.
  • Package synchronization in multi-node environments is not done properly and as such, some package versions are not displayed and found in every node of an environment. This might also lead to performance issues or error message displayed for package-related activities. To prevent this from happening enable Redis node coordination by setting the NuGet.EnableRedisNodeCoordination parameter in web.config to true.
  • You can connect to your Floating Robots from a machine template using a connection string if the name of the template is the same with the one of the machine from which you provisioned it.
  • When a very large number of schedules are defined, the scheduling functionality might be occasionally impaired by unsuccessful quartz triggers. As a consequence schedules cannot be created. The following workarounds are available, and they must be applied while Orchestrator is closed on each node of the environment:
    1. Set the quartz.jobStore.misfireThreshold parameter in web.config to 259200000. This helps the most in overcoming the issue, but please keep in mind that it might delay the next schedule trigger after the application has been restarted.
    2. Set quartz.threadPool.threadCount to 20.
    3. Set quartz.jobStore.clusterCheckinInterval to 30000.
    4. Set quartz.scheduler.batchTriggerAcquisitionMaxCount to 20.
  • Please take into account that "Robot is unresponsive" alerts are received despite having Robot alerts disabled (Profile page > Alerts section > Robots).
  • Time zones, as well as several fields on the Audit Data window, cannot be localized due to technical limitations.
  • Schedules with non-working days restrictions do not trigger correctly if the timezone defined at tenant level is modified after creating the schedule. This happens both for timezone changes made locally or inherited from the host.


  • Web page UI elements which are not in view are improperly targeted by the Click activity in Internet Explorer.

UI Automation

  • Selectors are generated for the entire page rather than individual UI elements when using UI Explorer to inspect a PDF file, which is poorly or not tagged, opened with Adobe Reader or Adobe Reader DC 19 which has Accessibility options enabled. You can find more details and workarounds for this issue on this page.


  • The Excel Copy Sheet activity does not function properly with Office 2010 and 2013 versions.
  • When sending mails with the Send Outlook Mail Message activity, inline attachments are sent as normal attachments.
  • The Send Outlook Mail Message activity can only save messages as drafts in the first Drafts folder found in Microsoft Outlook, when the IsDraft check box is selected.
  • The Get Outlook Mail Messages activity's ability to retrieve mails depends on how often Microsoft Outlook is configured to synchronize.
  • The Block User Input activity cannot block some of the specific commands sent by certain input devices such as touchpads, trackpads or touchscreens, because they are software events, which are essential for UI Automation.
  • The Excel Read Range activity can only retrieve a maximum of 4 decimal places from cells formatted as currency, due to a software limitation.
  • Due to a software limitation, the Run Python Script and the Load Python Script activities use, by default, the installation location of the Python activities pack as the run directory for the script. For a workaround, see the documentation for Load Python Script and Run Python Script.
  • When running a process that uses the Block User Input activity from Orchestrator, user input is not always blocked due to a lack of privileges of the Robot Executor. For more details and a workaround, visit the documentation.
  • The Go Home activity navigates to the Home page that was set by the user only in the case of Internet Explorer. For other browsers, it navigates to https://www.google.com.
  • The CurrentWorkbook and CurrentWorksheet property fields are no longer displayed in the Excel Application Scope activity.
  • Opening password protected files created with Microsoft Excel 2010 throws an error when using the Workbook Activities from the Excel Activities package. As a workaround, we recommend using the Excel Application Scope activities.


  • If your machine runs Windows OS in Japanese, make sure to install the Japanese language pack for the .NET framework version you are using. This is required for running Studio in Japanese.
  • Property names are not localized in error tooltips.
  • The properties in the body of Microsoft activities (**System.Activities.Statements**) cannot be localized due to code limitations.
  • The Expression Editor window is not completely localizable.
  • The UI Explorer from the Studio backstage view isn’t completely localized in Japanese on machines running Windows 7 OS.
  • The property names of Variables and Arguments are not localized.
  • The TypeArgument property name of the For Each activity is not localized.


  • If the entire UiPath suite is installed on a single machine, and you want to update from an older version to v2018.3, you are required to first do so on Orchestrator and then Studio and Robot. If you first update your Studio to v2018.3, your Orchestrator instance is removed. This is due to a change in the installers' Upgrade Code and is not going to be necessary for other subsequent updates.

Bug Fixes


  • The performance of adding or editing a user on an Orchestrator instance with many organization units has been improved.
  • The /Permissions endpoint has been repaired, to only return the permissions that the currently authenticated user has.
  • Fixed an issue that caused Orchestrator to fail, if you performed POST requests to the /odata/Settings/UiPath.Server.Configuration.OData.UpdateBulk endpoint with a time zone which could not be converted to IANA standard.
  • The Swagger documentation did not display the /api/account/authenticate and /api/RobotsService/GetAssociatedProcess endpoints correctly. Please note that the functionality was not altered in any way.
  • The /odata/Users/UiPath.Server.Configuration.OData.GetCurrentUser() endpoint now returns 204 No Content if the user making the request is not authenticated. Previously, it returned a 200 OK response.
  • It was possible to make a GET request to the /odata/QueueDefinitions(Id)/UiPathODataSvc.Reports endpoint although the user you authenticated with did not have the Transactions.View permission. Now, this permission is mandatory.
  • In some cases, Orchestrator stopped responding if you created multiple Per Robot assets from the API, then tried to edit them from the UI.
  • The GetCurrentUser endpoint did not return the tenant name.
  • GET requests on the Tenants({Id}) endpoint did not return the last login time.
  • The account change password endpoints, such as ChangePassword, ForgotPassword, and RegisterTenant now return 400 Bad Request messages if they are not used properly.
  • If you created a new user, with the Orchestrator API, which is not part of the specified Active Directory, the incorrect HTTP status was returned. Now the call returns 400 Bad Request.
  • The expand and select OData options were not working properly with the /odata/QueueItems(Id) endpoint.
  • PUT request to the /odata/QueueDefinitions(Id) endpoint which modified other parameters than the description, returned 200 OK although you cannot modify those properties. Such calls now return a 409 HTTP status code.
  • If you installed Orchestrator on port 80, you could not start the site. As this is an IIS limitation, a verification step was added in the Windows installer, not allowing you to provide this value anymore.
  • The -package and -publishSettingsPath parameters of the Azure installation script (Publish-Orchestrator.ps1) did not accept relative paths.
  • Silently (/Q) installing Orchestrator on secondary nodes is now supported.
  • It was not possible to add Elasticsearch credentials through the parameters of the Publish-Orchestrator.ps1 script. Now, new parameters have been added. For more information, you check out the documentation.
  • Elasticsearch was added as a log target in the web.config file, although you did not provide Elasticsearch details during the installation process. As a result, it was not possible to view logged messages in the Logs page.
  • If you deleted a package in Orchestrator, the Audit Data Details window did not display the exact package version.
  • If you had the same package on two different organization units, it was possible to delete it although it was active. This occurred only if the package was inactive in a unit and you deleted it.
  • Processes were no longer visible in the Robot Tray, if the user logged off and then logged on again. This occurred only on Attended Robots that were connected to Orchestrator.
  • Fixed an issue that caused packages in Orchestrator multi-node environments to only be displayed on the nodes where they had been uploaded from.
  • You could not download and further use packages if you switched from an external feed to a secure internal one.
  • Deleting inactive versions of a package when using an external MyGet feed secured with an API key was not always possible.
  • Fixed an issue that prevented you from saving changes made to the Default From Address and Default From Display Name fields. This happened despite having the confirmation message displayed after saving.
  • After making changes on the Settings page at host level, the user was prompted to save the changes despite already saving them on the tab itself.
  • Fixed an issue that caused two alerts to be generated in the database for the same event. This resulted in multiple alert emails being triggered and implicitly sent.
  • The Default from Display Name field was not taken into account when configuring email alerts and as such, received emails did not display the name.
  • In some cases, length validation of the Confirm Password field on the Become a Tenant page was not properly performed.
  • Fixed an issue that prevented an authenticated Orchestrator session from being correctly terminated at log out. Therefore, next time authenticating you could log in using the previously used user account. This happened despite clearing the browser's cookies beforehand.
  • The Job Details window now displays information messages when there are no more available runtimes for a Robot, as well as for machines that are not licensed and have a job in a pending state.
  • You can no longer upload an expired license and an error message is now displayed whenever you try to do so.
  • Permissions on Settings no longer influence the License page. A new set of permission has been added in this respect. Fore more information on this, click here.
  • Fixed an issue that caused an error message to be displayed and the page to stop responding when you inserted a custom title longer than 2000 characters on the Application tab in the Settings page. The message was only displayed at host level and only after you clicked Save.
  • If email settings are not configured properly, the failure to send email confirmations for creating or updating a user is no longer logged in Event Viewer.
  • You can connect to your Floating Robots from a machine template using a connection string if the name of the template is the same with the one of the machine from which you provisioned it.
  • In some situations, the Robot status was not updated accordingly unless you firstly refreshed the Robots page.
  • The NuGet server has been upgraded to v3.1.2 such that exception handling is done better, and thus preventing network connectivity issues.
  • Fixed an issue that caused the Access Forbidden error page to be displayed instead of the Login page if you previously logged in using your AD account, then logged out and tried to access the page again.
  • The following drop-downs are now populated with alphabetically ordered values:
    • The User filter on the Audit page.
    • The Robot and the Reviewer filters on the Transactions page.
    • The Robot filter on the Review Requests page.
    • The Reviewer filter on the Assign Reviewer window.
  • The number of Robots defined for a schedule is now correctly updated after changing the type to Attended for one of them.
  • Fixed an issue that prevented the Shift-key multiselect from working correctly.
  • An error message was displayed when you filled in the Username field on the Add User page and then navigated to the Roles drop-down using the Tab key. The error message was only displayed after pressing the Enter key.


  • Cancelling a running job from Orchestrator that invokes a workflow which is isolated would seldom return an error. Additionally, the job was marked as faulted, instead of successful.
  • On a machine with low disk space, packages were incompletely downloaded and triggered an error when a job was started from Orchestrator. This would persist even after freeing up enough space. The Robot now properly checks for corrupt or incomplete packages and installs the right packages before starting a job.
  • Execution would sometimes erroneously end if the process was stopped from the either Studio, Robot Tray, or Orchestrator on a scheduled job that runs on multiple High-Density Robots.
  • The Click activity did not interact with web page elements which were out of view in Chrome or Firefox.
  • On some occasions, the HtmlWindowName selector was not taken into account when automating pop-up windows in Internet Explorer. This resulted in erroneous actions being performed by activities.


  • The Data Scraping wizard threw an error if you tried to scrape nested tables in Internet Explorer.
  • Workflows were not displayed in the Project panel if their extension was written in uppercase (.XAML).
  • Studio had to be restarted to properly identify the connection between Robot and Orchestrator, if you installed and deployed the Robot to Orchestrator while having Studio opened.
  • Fixed an issue that prevented projects with names containing special characters in Japanese, Chinese and Russian from being published to Orchestrator.
  • Adding an additional active accessibility name (aaname) attribute in UI Explorer invalidated the selector inside an Attach Browser activity.
  • Adding a text attribute in UI Explorer invalidated the selector for a check box.
  • Fixed an issue that invalidated the selector in UI Explorer after indicating a relative element from a particular web page.
  • Selecting buttons using Web Recording in web pages triggered the Type Into activity instead of Click. This occured only in Firefox version 54.
  • Fixed an issue that caused Studio to become unresponsive after re-indicating a UI element inside a browser using an activity contained in Anchor Base.
  • The .svn subdirectories of working copies are excluded from the .nupkg package when publishing to Orchestrator.
  • Creating a variable after the workflow execution reached a breakpoint caused Studio to crash. Now, all panels in Studio are in read-only mode during debugging.
  • If you enabled the Firefox extension using cmd and then uninstalled your instance of UiPathStudio.exe, the reinstallation of Studio would fail.
  • Validation of a partial selector with Relative Target truncated one node from the selector, and caused UI Explorer and Selector Editor to crash.
  • Fixed an issue that caused searching by node attributes or selectors in the UI Explorer visual tree to sometimes return invalid results.
  • The creation of a variable failed if you switched to another field in the Properties panel of an activity after creating the variable in a different field with the Ctrl + K hotkey without pressing Enter.
  • Refreshing the Project panel and then using the Get Latest Version option when connected to a TFS repository did not restore the files that were previously deleted from the local directory.
  • Fixed an issue that prevented you from adding a local feed in the Package Manager if the machine didn’t have Internet connection.
  • When using Type Password with the Recording wizard, two password variables were created instead of one after saving the workflow.
  • When using the Type Into activity inside the Web Recording wizard, the focus was not moved to the input field.
  • In often cases, the Designer panel would jump to the top view when debugging is stopped while in the Execute tab.
  • The Locals panel would remain empty when using Step Into on an invoked workflow during debugging.
  • UIExplorer would sometimes stop responding if you attempted to detect UI elements in Windows Explorer with Active Accessibility enabled.
  • Debugging would sometimes remain stuck while using Step Into or Step Over on an invoked workflow which is isolated.
  • Using the Universal Search bar would sometimes change the layout of the Activities, Library, and Project panels.
  • When recording a Type action, special keys were not displayed in the input field during the recording process.
  • If you used Extract as Workflow, the Invoke Workflow File activity did not automatically map the local variables to invoke arguments for the extracted workflow.
  • Fixed an issue that caused Studio to crash after switching between users multiple times while connected to a remote desktop machine.

UI Automation

  • UI elements in tabbed Java applications were not always properly identified by UIExplorer.
  • The Select Item activity threw an exception if used on drop-down menus in Internet Explorer.
  • UIExplorer would become unresponsive when selecting UI elements inside web pages if Chrome or Firefox were running in multiple windows (not tabs).
  • The Microsoft Dynamics AX application would become unresponsive while corresponding selectors were generated.
  • Chrome and Firefox extensions could not properly generate selectors for some UI elements on particular web pages.
  • Selecting UI controls in Notepad x64 on a machine using Windows 10 Pro would return an error.
  • In seldom cases, the SLBroker window would appear twice on the taskbar while retrieving selectors with UIExplorer from Silverlight applications.


  • An error message was displayed if you tried to execute a workflow that had a dependency reference to Newtonsoft 10.0.3 and certain expressions in the given workflow used types from this assembly.
  • Fixed an issue which caused the Read Range activity to improperly read worksheets that had the first row empty.
  • The Workbook Read Range activity returned incorrect values when reading cells that contained hyperlinks.
  • Fixed an issue which prevented Python script errors from being correctly displayed in Studio.
  • When forwarding mails with the Send SMTP Mail Message activity, they were not sent to the target recipient.
  • If Microsoft Outlook stopped responding during the execution of a process, the Get Outlook Mail Messages, Move Outlook Mail Message, and Send Outlook Mail Message activities caused the Robot to freeze.
  • In some cases, the Send SMTP Mail Message activity failed to authenticate and threw an error.
  • Fixed an issue which did not allow users to send mails with the address of other users in their domain by filling in the From and Name properties in the Send Exchange Mail Message activity.
  • Get Exchange Mail Messages was unable to retrieve emails from a shared account from a folder different than Inbox.
  • Fixed an issue which caused the Excel Write Range activity to throw an error when processing a DataTable variable containing GenericValue values.
  • When creating a data table with the Build Data Table activity which contained GenericValue columns, an error was thrown.
  • The Read Column activity only read the first row in a spreadsheet which contained the maximum number of rows - 1,048,576.
  • In some cases, the Open Browser activity failed to open web pages with Internet Explorer.
  • Fixed an issue which caused the HTTP Request activity to remove header parameters in some cases.
  • When running a process that contained the Set Asset activity on a machine connected to Orchestrator, and network connectivity was lost, the process remained in a running state.
  • At runtime, the Input Dialog window appeared minimized.
  • The Generate Data Table activity did not correctly display separators (Space, Tab, NewLine) in the resulting table.
  • Setting a file in the FileName property field of the Append Line activity generated a message inquiring the user if they wanted to replace the file.

Updated 4 months ago


Suggested Edits are limited on API Reference Pages

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