Release date: 11th November 2019
Five months, at least 5 Community Edition iterations, roughly 900 new features and improvements, 3000 bug fixes, countless tasks and subtasks, blood, sweat, tears, drama – 2019 is now ready to be released into the world as our latest long term support Enterprise Edition.
This release continues to advance scalability and flexibility, with significant progress on multiple fronts. We bring to you hierarchical folder support, attended robots auto-provisioning, long-running workflows support, a workflow analyzer, an enhanced debugging experience, more out of the box solutions for digitizing documents or automating IT processes, new ways to interact with browsers via the Webdriver protocol, automatic download and start of processes by the Robot, more methods of tweaking selectors, and scores of other improvements.
Making UiPath your trusted automation companion has been the focus in the past few months. This is only half the battle. Let’s take you on a tour:
This release graduates key features in handling end to end business processes, introducing support for processes that require logical fragmentation or human intervention. With this new functionality, workflow execution can now be suspended and resumed at a later time – not necessarily on the same machine. Among other things, this paves the way for intuitive and easy invoice processing, exception handling and performance reviews. We set the stage for automating complex processes that either rely on the completion of other processes, or require approval or validation, all this with no waste in terms of resources while waiting for process resumption. Learn more about it here.
Don't worry, we've introduced a new project template in Studio called Orchestration Process, and a brand new set of activities that allow the smooth fragmentation of your workflows. Read more about how to build an Orchestration Process and best practices here.
In this scenario, Orchestrator introduces the human in the loop and ensures a smooth management of your fragmented jobs.
The human aspect is handled through tasks which can be managed and completed without obstructing process unfolding. After human intervention is made and task completion takes place, resources are allocated for job resumption, thus ensuring no waste in terms of consumption. Details here.
To facilitate support for long-running workflows, we introduced two new job states which properly illustrate the job progress: suspended and resumed. More about job states here.
A new webhook event is also available for suspended jobs. Learn here all there is to know about this event.
Also, this would all mean nothing without the introduction of the Persistence activities, which enable you to create workflows that use the Long-Running Workflows feature. To find out more about these activities, you can check the documentation.
As part of this initiative, we have also created the Form activities pack, which contains several new activities, centered around helping you generate custom forms and callouts that can be used to gather human input throughout the execution of a long running workflow.
The first iteration of the Form activity pack contains a new activity that enables you to create and display custom form fields, which can be used to collect data from human users, and then be reused in your automation processes. The pack also contains activities that help you create customizable callouts, interactive information bubbles, which can be targeted on UI elements in the apps you are automating. To find out more about this pack, you can check out the docs.
Workflow Analyzer checks your current workflow or project against a number of configured rules to determine if best practices are met. For simplicity, we merged project Validation into the Analyze function, so you can check for errors and best practices at the same time.
Validation issues and rule violations are both displayed in the Error List panel, the latter come with recommendations of fixes to be made to the file or project.
Workflow Analyzer comes with command line support for integrating its validation and analysis features in CI/CD processes as well. Read about Workflow Analyzer here.
We’ve created a guide on how to write your own custom rules and add them directly to the Workflow Analyzer Settings window by using the UiPath.Activities.Api package. Read about this here.
Aimed at keeping your RPA deployment manageable and organized no matter the scale, the latest UiPath Orchestrator release introduces the Folders feature. There are now two organizational paradigms available in Orchestrator: Classic Folders and Modern Folders. Through classic folders, full backwards compatibility is maintained for your existing deployment and integrations while enabling you to segregate at the tenant level those divisions of your business that are wholly separate. Moving beyond the classic model, modern folders enable you to easily manage resources, and access to them, through support for hierarchical structuring of your Orchestrator instance combined with the new ability of fine-grained role assignment - your Orchestrator instance can now be structured inline with your corporate structure with each level, or employee, only having access to those resources needed for their role.
The previous experimental Organization Units feature is now fully supported as part of Orchestrator's Folders functionality. You can organize your instance using any number of classic and/or modern folders. Like Organization Units, classic folders are separate, flat structures with no shared Orchestrator entities between them. Modern folders enable you to create hierarchical structures, with users inheriting access to any subfolders of a folder to which they are assigned. User access in modern folders can be managed with greater granularity by creating custom roles and setting the desired permissions on a per folder, per user basis.
Just so you don’t get confused, the Robot Tray displays the corresponding process folder in a tooltip on mouseover.
User management challenges brought by large deployments and employee dynamics have been addressed in this release by integrating Orchestrator with Active Directory. Broadly, you no longer need to go through the hassle of directory duplication in your instance, as added AD identities are checked directly against the directory database.
The feature enables you to either grant or restrict access to Orchestrator according to the configured group policies and based on your AD group membership. Manual intervention is limited to adding your groups and configuring access rights for them in Orchestrator; the rest of the process is, you guessed it, automated.
To better fit our new AD integration tool, we revisited user types in Orchestrator. As of 2019.10 we have: local users, directory users, directory groups and robot users. They are all described here.
Remember Floating Robots? In the context of modern folders, they come with no strings attached, and possibly the smallest deployment effort so far. Their execution capabilities can be put to use across folders, unrestricted by any form of organization. This brings great value especially alongside hierarchical folders, as you may structure your organization as you desire, and make the execution force fit it perfectly as is.
Don't blink too fast. These Robots can be automatically created for whatever type of user identities you have in your instance (local users, directory users, and even directory groups), and license-wise, they are configured directly at creation according to your plan. Might seem a lot, but this can actually be achieved with roughly 5 clicks. Details here.
Scheduling in Orchestrator has been treated to a major overhaul to make everything easier and more intuitive to use. The functionality is now called Triggers and comes along with a couple of new features and improvements. The highlight is that you no longer need to make arrangements to optimize the processing of your queue items. Orchestrator gives you the possibility to trigger a process whenever new queue items are available in your queues. Be reminded, since scheduling is not possible for attended use cases, and modern folders only work for those, this goodie is available for classic folders only. For now. Details here.
This is not all. We implemented a Queue SLA tool which gives you better control over the processing time of your queue items, and helps you assess what resources you need to allocate such that the items are processed in time. Whenever the SLA is in danger of not being met, you are properly notified such that you can make adjustments accordingly.
Individual transaction items from your Queues can now be edited or cloned, enabling you to change the priority or deadline to suit business needs. This feature also enables you to download a JSON file of the transaction data to review and upload it if any changes were needed. More details here.
You now have greater control of the data flowing through your queue items, making further processing and analytics that much easier. When creating a new queue, or editing an existing one, you can upload custom
.json schemas for the Specific Data, Output Data, and Analytics Data generated by all future transactions to be validated against, ensuring any successfully processed queue item has a reliable form of data.
A much-improved licensing experience awaits, making starting and growing your Orchestrator deployments easier than ever. For internet connected Orchestrators, activating and updating is an instant, one button process. Your offline Orchestrators weren’t ignored in this upgrade, with a simplified offline activation included as well.
More good news is afoot - if Studio is licensed locally, no additional license is consumed in Orchestrator. Furthermore, each time you create a Studio or StudioX Robot, you can specify if it uses an external license or not. Oh yeah, and while we were here we also renamed the Development type of license to Studio, to avoid confusion.
Lastly, we updated the command line tool used for licensing. Actually, we’re giving up on the old Regutil to bring you the new LicenseTool, about which you can read on this page.
Lots of good news to report here as we’ve not only expanded and improved the integration of CyberArk with Orchestrator but also added support for Azure Key Vault and a pluggable architecture that enables you to develop your own plugins and use any desired secure store.
Where before you were limited to only one CyberArk vault per Orchestrator instance, and forced to choose using either that or the native database, now vaults are created at tenant level where you can have as many as you need to store different credentials and assets. Additionally, CyberArk vaults can be used together with the native Orchestrator database, giving you control over how and where you store all credentials and assets in your Orchestrator instance.
Azure Key Vault integration is now supported as well, giving you three out-of-the-box options for credential stores with your new Orchestrator. Read more about it here.
Not wanting to limit your options, Orchestrator is ready to accept your custom plugins for any credential store that you want to use. For more details about developing and loading your custom plugin, see here.
Orchestrator has a new look and feel, giving it an intuitive design with resources organized to provide a smooth, easy-to-use experience. Have a look at our new look here.
Studio also sports a cleaner look and feel, with new icons for buttons in the ribbon, additional options in the Backstage Settings tab, and a new color for highlighting activities. In addition, you can find Help links easier using the new shortcut in the Studio ribbon. As a whole this ensures a more comprehensive user experience. Read about the user interface here.
A revamped and redesigned UiPath Platform Installer is here to get you up and running with all the new features of UiPath Orchestrator, Studio, and Robot quickly and easily. Along with the new interface is simplified installation of your multi-node Orchestrator and an easily customizable installation of Studio and Robot.
Finding certain elements part of your project is now easier with the Command Palette feature, which can be opened using the F3 or Ctrl + Shift + P keyboard shortcuts.
In one single place, you can search in all project files and add an activity to your workflow, jump to a certain file or activity, and use fuzzy search to find files, activities, variables, arguments, imports, dependencies and more. These functionalities are available with Command Palette and its Add activity, Universal search, Go to file, and Jump to activity options. The Command Palette and all of its options are detailed here.
To add activities to workflow use the Plus sign in the Designer panel, or navigate through items in the Activities panel and press Enter. Check the documentation for more info.
Use the Send Feedback feature to let us know what you think about Studio, suggest new features or report a bug. Your feedback reaches our product team directly and may be integrated in future versions. However, please keep in mind that the Send Feedback feature should not be used in cases where you require assistance from our support team. Learn more about this here.
We’re giving you the chance to use the Robot in more ways than before. By exposing several API commands, you are able to integrate more functionality in your applications, such as acquiring the processes list, run and pause, monitor, or terminate them. Read more about its capabilities, what it means, and how it can be used.
The debug-first approach in Studio bundles the Debug File or Debug Project and Run File or Run Project options under one button in the ribbon, encouraging continuous debugging of workflows.
The Locals panel now shows the values for arguments, the properties of the current and previously executed activity all in a cleaner design. The values of variables and arguments can be modified from this panel when debugging is paused. Right-click a variable or argument in the Locals panel and add it to the Watch panel to continuously monitor its value throughout the debugging process.
The Immediate panel inspects data by evaluating expressions you define during the debugging process. At the same time, you can monitor the execution of activities, containers and project files from the Call Stack panel and double-click to jump to the activity which threw an exception. Read more about debugging here.
Breakpoints have been enriched with the possibility to add conditions, a hit count and to log a message when hit. In this way, you can set a condition for when the debugging process to be paused if the defined expression is evaluated to true. The hit count specifies the number of times the condition must be met before the execution breaks. Simply hover over a conditional breakpoint or tracepoint in the Breakpoints panel to view its condition. Read more about breakpoints, tracepoints and the Breakpoints panel here.
Activities can now be tested either inside the workflow using the Test Activity context menu option, or from the Activities panel by creating a test bench.
Run to this Activity and Run from this Activity context menu options start debugging the workflow to and from a certain activity. Read more about these actions here.
Use the Restart ribbon option to restart the debugging process from the first activity in the process or the activity from which the Run from this Activity option was triggered.
The new Step Out action finishes the execution of the current activity and returns to the level of the container, pausing the debugging process.
Whenever an exception is encountered during debugging, you can Break, Ignore the error and Continue. The Retry option re-executes the previous activity, and throws the exception if it's encountered again. These actions are now available in the Debug tab, and detailed here.
Details about the thrown exception are displayed in the Locals panel. The activity which threw the exception is highlighted in red, in the Designer panel. Read more about the Locals panel here.
Use the Activities Project Settings window to change activity default properties at a project level. You can configure a set of values for debugging, and another set of values for when the project is run from Studio, the Robot Tray or Orchestrator.
The Activities Settings are available for UIAutomation and System activities. Read more about Activities Project Settings here.
Attended automation reaches new limits with this release. As of now, an Attended Robot can simultaneously run multiple background processes you create in Studio, allowing you to have actions monitored in the background. Besides those, a single foreground process can also be executed in the meantime. This is called Parallel Execution for Attended Robots, no special license is required to enable it, and we’re sure it enriches your relationship with Attended Robots.
The new Background Process template accompanies the Parallel Execution for Attended Robots. Processes that can run in the background should not have activities which require user interaction. Read more about this type of template here.
A new panel in Studio, Orchestrator Resources can be used for loading assets, queues and available processes from Orchestrator, provided that the Robot is connected to Orchestrator. The Orchestrator Resources panel loads items from both Classic and Modern Folders, and brings the possibility to switch between multiple folders and subfolders.
Although the Validation Station Wizard is only an improvement, we are so proud of it that we want to present it as a new feature! The upgraded version lets you interact with a new user-friendly interface, navigate through the document while using only the keyboard keys, select one word or multiple words at a time or a specific, custom area. You can easily mark a field as missing, extract new data, edit a table or extract a new table. All these marvelous things can be done with the Validation Station wizard while using a dark theme.
Two new packages, UiPath.Azure.Activities and UiPath.Citrix.Activities, are now available for easing your automation process. The IT Automation spectrum is getting wider and wider, now being represented by five packages, the two previously mentioned and the following three: UiPath.ExchangeServer.Activities, UiPath.VMWare.Activities, and UiPath.ActiveDirectoryDomainServices.Activities.
We’re proud to present the support for Webdriver processes. What this means for you is that headless browser automation is now a thing, and you don’t necessarily have to rely on extensions anymore. Get informed about the Webdriver protocol, how to configure it, and what you should keep an eye out for.
Tweaking selectors in the right way allows activities to know exactly what to look for. In this regard, we added more capabilities to selectors, as follows:
- Fuzzy Search makes it possible to identify certain elements even if they are targeted incorrectly, or misspelled.
- RegEx Search returns elements based on complex search patterns.
- Non-Greedy Search helps you locate just that element you need from a pool of similar elements, based on particular attributes.
The Computer Vision activities have now moved to the UIAutomation activities pack, as the newer technology offered by them is more and more becoming essential for automating various environments that are hard to target by other means. As a result, the documentation for these activities has also moved to the UIAutomation section in the docs.
Native selectors can now be generated for applications running on JRE and JDK 9 and above.
A new activity meant to help you better organize and manage your trainable classifiers is available: Keyword Based Classifier Trainer. This activity can be used only together with the Train Classifiers Scope activity.
As of this release, the Project Settings feature has been implemented in the System activities pack, enabling you to set project-wide configurations for the activities in this package.
Most of the Orchestrator activities have a new property, FolderPath, which, paired with the Folders feature in Orchestrator, enables you to specify if the Transaction Item you want to process is located in a folder different than the default one.
A new activity, called Run Parallel Process has been added to the System package, enabling you to run a specified process in Orchestrator, with the ability to pass it a list of input arguments.
For a better collaboration between RPA developers and Orchestrator managers, you can now view the graphical representation of any package version uploaded to Orchestrator, just as you do in Studio's Designer panel. You can see which
.xaml file is marked as Main for a project, deep dive into any workflow, view a project's dependencies, and look up any activity property and its value. For a better picture of the entire feature, click here.
In case you were yearning for a different feature configuration for each of your teams, you’ll be pleased to know that in this release we've come up with a feature flags functionality. We made this happen such that you can easily turn features on and off for each of your tenants. For now the following features can be enabled or disabled through this functionality: Monitoring, Queue SLA Monitoring, Tasks.
And while we're at it, you should know we've exposed the
odata/Features/UiPath.Server.Configuration.OData.UpdateFeaturesBulk endpoint which allows you to enable or disable features from the API. Please keep in mind that you can only make these changes at host level. Click here to see how to use the functionality in the user interface, and here for the corresponding API request.
As a continuation of our efforts to reach out to the entire world and make automation a language everyone can speak, the entire platform is now available also in Simplified Chinese, Korean, German, German, Spanish (Spain), Spanish (Latin America), Portuguese (Brazil), Portuguese (Portugal), and Turkish.
UiPath StudioX is now available for public preview, getting us one step closer to making automation accessible to everyone! Based on UiPath Studio's tried and tested, intuitive design interface, StudioX simplifies the experience even further, enabling every business user to automate their tasks. You don't need any programming skills to take full advantage of StudioX, if you know your way around Microsoft Excel, you have every chance to excel in StudioX.
No more wasting time following the same old routines involving Excel workbooks, Outlook emails, or moving files around your hard drive. With StudioX, you can build simple automations for repetitive tasks and send them to be executed by the UiPath Robot. The business user is involved in every step of the process: identifying the tasks, building the automation, executing it, and analyzing the results.
StudioX is now available as a separate profile in Studio. See how you can switch to this profile here.
- Straightforward automation for business tasks - StudioX is designed for simple, linear task automation. The only workflow type available is sequence and automation projects are single file.
- Simplified automation design - An intuitive way to configure activities by selecting the data to use from a drop-down menu with options that are relevant in the context of each property and activity. The menu includes editors for text, numbers, conditions, and an easy way to save the output of one activity for use as input in another activity. No variables, arguments, or complex debugging features.
- Seamless integration with Microsoft Office - Select the Excel and Outlook data to use in activities you add to your automations straight from StudioX. You can select individual cells, ranges, and sheets from Excel files, or folders and mail messages from Outlook. The Excel and Mail activities packages now contain multiple activities which are especially designed for use in StudioX. To find out more, see Excel Automation, Outlook Automation.
- Activities focused on the business user - A reduced number of activities that are tailor-made for business users, together with a new Activities Panel that allows you to filter activities based on their type.
- Click-and-forget automation for interactions with applications - Automate interactions with desktop applications and web pages in an easy-to-use and reliable way. An improved mechanism for identifying UI elements means that you can indicate the element to interact with using a simple mouse click, and then know that the element will be identified every time you execute the automation. StudioX UI Automation activities combine the selector, image, and text methods, along with an automatically generated anchor to identify target elements better than ever. Read more about UI automation here.
- File system integration - Manage your files efficiently with a host of activities that let you automate tasks like creating, copying, moving, or deleting files and folders. Read more about system automation here.
- Common Scenarios - Get suggestions for what activities to add to your project based on the activities you already added. Select from the predefined scenarios for common processes to add multiple activities in one go.
- Cards - Define the scope of your automation by adding the Excel files, Outlook accounts, desktop applications, and web pages to work with to cards. The data in Excel files and Outlook accounts you add to cards in your project can be accessed by all the activities in your automation.
- Excel Workspace - An Excel workbook available by default for every project. Preloaded with useful formulas for dates, text, numbers, and files, it's there to act as a scratchpad for your projects.
- Attended Automation - Collaborate with your Robot on your machine and trigger automations as needed.
For more information, see this page.
The Output panel has been enriched with the Export Logs button, which exports all or a certain batch of logs into a
.txt file, together with timestamps and error message details. Read more about this here.
We made improvements to GIT integration and added SSH support for cloning a repository. Check the documentation for more details.
The Add to Source Control shortcuts part of the status bar are now available in the project’s context menu as well.
The Copy to GIT shortcut is now available in the Studio status bar. In addition, the bar comes with the additional option of switching branches, together with shortcuts for committing and pushing changes. Check it out here.
Studio now remembers previous preferences in terms of checking out versioned files by simply selecting a checkbox in the source control prompt window. This is detailed in the documentation here and here.
The Activities Root Category is now memorized in the Publish window for libraries.
Activities from read-only files can now be copied to another workflow or a
Within the Project panel, you can now drag files from one folder and drop them to another project folder.
The Auto Arrange context menu option for flowcharts allows you to automatically arrange activities following the logic of each connector.
The Project panel now shows all project files by default and after publishing, the Info window displays the files that were packaged.
The Open File Location context menu option in the Project panel opens the local folder containing the selected file.
Hover over an activity in the Activities panel to view the package it belongs to in the tooltip, or group activities by packages. Find out how to do this from here.
Annotations for arguments used in a library are now displayed as tooltips in the activity's Properties panel. Read more about this here.
Studio now exposes additional data to activities: the authentication token and theme settings. This allows for more capability when building custom activities.
Continuing our never-ending efforts on extensibility, Studio has been enriched with the possibility of opening
.txt and other types of files directly from the Project panel, with the default program. Learn how to use this from here.
The Rename context menu option can be used for folders and files, including those captured in Invoke Workflow File activity. Read more about this documentation.
New sequences, flowcharts, state machines, exception handler templates, and folders can be added directly from the Project panel context menu. Check the documentation for more info.
We’ve added several keyboard shortcuts to make Studio and its panels more accessible. Find out all about these keyboard shortcuts here.
Use Shift + Enter to add a new line in an activity input text field or Expression Editor. The Enter key saves the text that you inputted.
The Reset Settings button can now reset the list of favorites from the Activities panel.
When creating variables or arguments directly from the properties of an activity, the custom namespaces containing the type used as generic are automatically imported. Previously, the namespaces needed to be imported from the Imports panel.
Dock or float annotations by default using the new toggle in the Design settings tab of the user interface.
Studio can be configured to Keep Last Opened Tabs or Open Main Entry Point when reopening a project so you can continue from where you left off. Find out how from here.
System.Data.DataTable is now a default type of variable or argument. This means that the namespace is available by default in the Variables and Arguments panels. Read more about the Variables and the Arguments panels.
The Edge Extension is now a full-fledged feature in Studio, meaning that it no longer is marked as Experimental. Read all about the Edge Extension and how to install it here.
The Agent Process Improvement template has been renamed to Trigger Based Attended Automation. Read about this template here.
We’ve updated our
project.json schema to a newer version. See here what this means.
If you fancy managing and running your processes from the command line like a true coder, then we’ve got some good news for you. We’ve completely rewritten the Robot Command Line Interface parser to make it verb-based. New commands were included, obsolete ones got removed, thus generating an easier experience when working with the Robot CLI.
The Robot has gone through some changes. Since it’s not the looks that matter, we focused on improving the way information is displayed. For instance, both background and foreground processes that are running can be seen and managed, unused Orchestrator connections removed at the press of a button, and more. Just head over to the documentation portal for more information.
On top of that, if configured from Orchestrator, Robots automatically download and start processes whenever the Tray is started. This makes for a flawless, continuous automation experience.
The default communication channel between the Robot Executor and the Robot Service has changed from WCF to IPC.
Starting with this release, the server that hosts Orchestrator requires .NET Framework 4.7.2. More details about software requirements can be found here.
To better support long-running workflows, you can now edit processes while having associated running or pending jobs by default. As a result, the
Processes.AllowUpdateWithRunningJobs parameter now only controls whether or not you can remove such processes. More information is available here and here.
Thanks to multiple changes made by our dev team, it is now possible to use 7.x versions of Elasticsearch in conjunction with your on-prem deployment of Orchestrator. Please note that this is possible only starting with 2019.8, and all previous versions of Orchestrator work only with versions up to 6.x.
Creating and managing Assets is now simpler, no more creating single value or robot specific value assets. When creating an asset you now have the ability to add a global value. This global value serves as the default provided to any robot which does not have a specific value assigned to it. Read more about it here.
We all like to have things organized our own certain way. To help you keep your customizations just as you wish, all Orchestrator filters, including the number of items which are displayed per page, are now persisted throughout the app. Moreover, a handy Reset to default button was added for your convenience.
Individual transaction items from your Queues can now be edited or cloned, enabling you to change the priority or deadline to suit business needs. This feature also enables you to download a
.json file of the transaction data to review and upload it if any changes were needed. More details here.
To ensure all of your processes are using the latest package version, you can now see all eligible processes when uploading a new package and upgrade any or all of them instantly. See here more details.
To make organizing and finding resources easier in your growing automation deployments, we have now added an editable Description field for Asset and Machine entities.
When performing a command-line installation using the
UiPathOrchestrator.msi installer, the bulk of the available parameters can now be passed in a file. See here to learn more.
When deploying a process you can now configure it to start automatically when the user launches their robot agent.
You can now configure your Robot to automatically download processes so that it’s ready to execute whenever you are.
To enable you to easily customize the maximum upload file size in Orchestrator when using Azure blob storage, a new
web.config parameter -
requestLimits maxAllowedContentLength - has been added. You can view more information on it here.
The first ever version of the Non-Working Days feature allowed you to define one set of non-business days in which your schedules were not triggered. We made it better. You can now create multiple calendars per tenant, each with its own set of dates, such that whatever restrictions you want to impose, they can be granularly controlled. To get one more thing off your chest, we also added the possibility to upload a CSV file containing the dates to Orchestrator, no extra manual intervention required. Find out more. To support the improved Non-Working Days feature, we added new endpoints for Calendars requests. Note that the
SetCalendar endpoints have been deprecated.
The newly added Restart Job feature saves you valuable time by enabling you to quickly run a job from the jobs list. You’ll be glad to know that you can restart any job with a final state – Stopped, Faulted or Successful. The decision to modify the previous settings of the job lies in your hands. Please keep in mind that you can change the job’s input parameters and robots, and that you can’t restart jobs triggered by an agent.
Orchestrator emails have been groomed up and you can now identify your tenant directly from the subject of the email.
We've added support for auto theme in Chrome 76 and above.
We now support Firefox. 69.0.1 and above.
The Keyword Based Classifier activity received a new parameter named LearningData. Besides specifying where the learning file data are located, you can now also use the string containing the serialized classifier data. The activity was enriched with a wizard named Manage Keyword Based Classifier Learning created for configuring and managing the keywords used for identifying specific document types. A new activity meant to help you better organize and manage your trainable classifiers is available: Keyword Based Classifier Trainer. This activity can be used only together with the Train Classifiers Scope activity. Both Keyword Based Classifier Trainer and Keyword Based Classifier activities are now able to manage multiple keywords. After the keyword sets are selected, the extraction is based on a full match of the selected words.
The DocumentObjectModel output, included in the Digitize Document activity, can now support word polygons, besides word horizontal boxes. Same feature was included in the UiPath.DocumentProcessing.Contracts pack by improving the public class Word. This improvement also impacted the UiPath.OmniPageOCR.Activities pack.
The Taxonomy Manager wizard received a new scrolling bar that incorporates all UI elements and it provides a better user experience.
The Validation Station wizard received an important upgrade and it is now available for you to explore its maximum potential. This wizard becomes available only when the Present Validation Station activity is used in a workflow.
Data Extraction Scope, Train Extractors Scope, Train Classifier Scope and Classify Document Scope activities are now arranging their extractors and classifiers in horizontal order, replacing the previous vertical order.
The Regex Based Extractor activity has been improved and can now process and return multi-values. The output is visible only when the activity is used together with the Present Validation Station activity.
A new property is available in the UiPath.DocumentProcessing.Contracts pack under the name of OperatorConfirmed. This comes as a support for the newly improved Validation Station wizard.
A new input option, PreserveFormatting, is now available for the Read PDF Text activity, allowing you to maintain the formatting of the file throughout the extraction process.
Added support for the Hitachi Automatic Job Management System 3 application.
The Microsoft Azure ComputerVision OCR activity now has a new option named UseReadAPI that enables you to handle handwritten documents.
The Callout activity has changed its name to Tooltip, to better reflect the actual use case of the activity. This is only a cosmetic modification, so you don't have to worry about any old workflows breaking.
The Microsoft Project Oxford Online OCR activity has been deprecated.
The Computer Vision Recorder now supports the
Shift + Click command for editing anchors at design time.
The hotkey for opening the Computer Vision Recorder has been changed to
Alt + Ctrl + V in Studio. Also, the Recorder can now be found alongside the rest of the recorders, in the Recorders drop-down.
- Interactive selection now properly generates selectors for SAP popup windows.
- The SAP grid technical header attribute is now supported by the Extract Structured Data activity.
- The Click and Check activities are able to interact with SAP gridtable controls.
- Selectors can now be generated for SAP Menubar controls.
- Silverlight popup windows now generate valid selectors.
- UI Automation activities cannot be used in Orchestration processes, unless they are isolated in a sequence that does not use Persistence activities.
- Remove Unused Variables does not work for variables with the same name, but in different namespaces.
- Projects containing a variable of a type declared in more than one namespace cannot be published.
- If you reverse the connector between two activities in a Flowchart and then use Toggle Breakpoint action, the breakpoint is visible only in the Breakpoints panel.
- The Workflow Analyzer rule ST-DBP-020 Undefined Output Properties is improperly triggered for variable combinations.
- Dictionary Key and Value types are not evaluated, but the value of the dictionary object itself is when used with Create Test Bench action.
- When upgrading from Studio v2018.2 or earlier where a custom installation directory was used, any changes in your
nuget.configfile will not persist through the upgrade.
- If the connection to Orchestrator is lost, the license status and processes list are updated only after you interact with the Robot Tray.
- If the
UiPath.Executor.exeis configured to Run as Administrator, processes which contain the Invoke Workflow File with the Isolated property enabled throw an exception at runtime.
- A User-Mode Robot is only able to download and install project dependencies if they are found locally or on the Orchestrator instance it is connected to. As such, it is unable to run processes which have dependencies on the Official or Go! Feeds. You can find out more in the Troubleshooting Guide.
- Process execution experiences a slight increase in duration on Community Edition versions 2018.4 and above. You can find out more details in our troubleshooting guide.
- Packages cannot be concurrently installed by the Robot Service if the configured location is the same for all users on that machine. More details can be found here.
- The Robot does not download a new package version if the
%UserProfile%\.nuget\Packagesfolder already contains a package version with the corresponding project
.nupkgfile in it and one without it. This is covered in our troubleshooting guide.
- The Robot cannot start a process on a Windows Server 2019 machine which is already running several background processes. This occurs if the Robot is configured to automatically download and start processes from Orchestrator.
We dove in head first when announcing the latest logging improvements related to the MongoDB NLog target. In this release, we identified some flaws in the way this target interacts with the current Orchestrator solution, hence we've come up with the following errata and clarifications on the 2019.4.2 release note and documentation on the subject:
- We support both read and write operations only when logging to Elasticsearch and the database.
- The MongoDB NLog target is still compatible with Orchestrator when performing write operations. Read operations do not work. However, due to the large spectrum of potential corner cases, UiPath cannot provide assistance in configuring and troubleshooting the custom targets for write operations.
Beginning with this release, logging using the MongoDB NLog target is not recommended and has been removed entirely from the documentation.
- Due to various networking or configuration issues, there is a chance that not all domains displayed in the Domain Name drop-down are accessible.
- It can take up to an hour to update the domain list with newly added two-way trusted domains.
- Removing a directory group does not remove the license of an associated directory user, even if the group removal unassigns the user from any folder. The only way to release the license is to close the Robot tray.
- Changes made to AD user/group names are not propagated to Orchestrator.
GetRoles(Id)requests only return folders and roles explicitly set for an auto-provisioned user. The ones inherited from the group configuration can be retrieved through the
- Same goes for the user interface, where only explicitly-set folders and roles are displayed on the Users page, while inherited ones have a new dedicated location, the User Permissions window.
- Auto-provisioned users do not inherit alert subscription settings from the parent group, nor do they receive any alerts. In order to have access to alerts you are required to explicitly grant the corresponding permissions to the user.
- On certain browsers, logging in to Orchestrator using your AD credentials only requires your username, there is no need to also specify the domain. Hence, if the domain\username syntax does not work, try filling in the username only.
- Workflows that do not follow UiPath Studio standards are not supported.
- Packages with UTF-16 encoding are not fully supported. As a result, package dependencies are not displayed for such archives.
- Opening an empty package in Package Explorer does not throw an error and does not render any display.
- The performance might degrade if you use the Expand All option with considerably large
- Upon upgrading your existing Orchestrator instance to v2019.10, certain scenarios occur in which organization units are 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 are not visible to the respective user after migrating.
Say I have defined five OUs in my v2018.3 Orchestrator instance. I assign John to one of them, and then delete the unit entirely. After fully migrating to v2019.10, John does not see any of the other 4 equivalent classic folders in his Orchestrator instance, hence won't be able to use it.
- You cannot download the Orchestrator offline activation request file if you are using Internet Explorer. As a workaround please use another browser.
- Removing a license at tenant level is not possible if was initially uploaded at host level.
- Upgrading a multi-node Orchestrator to v2019 must be performed with the application stopped. If performed with the application running, any schedules triggered during that time will fail and not resume.
- Performance degradation and possible errors occur when loading the Folder Selection menu for a user assigned to more than 1,000 folders.
- Where you have set schemas in a Queue for Output Data and/or Analytics Data, queue items that do not contain any output and/or analytics parameters are nonetheless processed successfully.
- Packages that contain files without an extension and special characters or a blank space cannot be uploaded to Orchestrator.
- A suspended job is not resumed if a Delay activity is used in the workflow before the job reaches the Suspended state.
- A 400 Empty or invalid anti forgery header token response is received when trying to make a POST request using cookie authentication.
- Taxonomy Manager can be accessed only if you previously opened a
.xamlfile. If no files are opened when you access the Taxonomy Manager, a recording window is shown and Taxonomy Manager is displayed only after closing the recording window.
- As the PDF standard contains some functionalities which are not FIPS compliant (related to document signing and password protection), exceptions might occur. The exception is thrown by the activities at run-time, when files with non-FIPS compliant content are processed.
- Enabling the Simulate Click or Simulate Type properties of an activity ignores the Clipping Region and Cursor Offset parameters of that activity.
- Drop-down menus are not clickable with the Computer Vision activities in SAP. A workaround for this is using the CV Type Into activity with the first few characters of the specified item followed by
- If the target Windows session is not fully initialized, the Take Screenshot activity does not return any output.
- Interactive selection does not work for Edge until all corresponding processes are terminated from the Task Manager. It is recommended to close the browser and terminate its process right after you install the extension. You can find more details on this page.
- Headless browser automation does not use a visual browser window, making events monitoring an unsupported action.
- Activities which trigger hardware events (such as Click or Type Into), need to be configured to use the SimulateClick, SimulateType, or SimulateHover properties.
- The Output panel no longer expands to half of the width of Studio while in debug, on machines where a fresh install was performed and the layout size was not previously defined.
- Deleting the
.localfolder while the project is opened in Studio resulted in an error when attempting to close Studio.
- The New Service ribbon button was unresponsive if the local copy of the SVN or TFS-versioned project was opened in Studio, and the
project.jsonfile was checked out.
- Fixed an issue that allowed incomplete or invalid project paths to be validated at process creation if a project directory already existed in that location.
- Checking out a remote branch with the same name as the local branch resulted in a detached branch state.
- Fixed an issue that prevented Studio from displaying the default value of an argument in the Show Changes window.
- Fixed an issue that prevented icons in the Project panel from updating when setting a Global Handler in a newly created project.
- The order of a sequence of activities is now properly kept if you copy them to another sequence.
- Fixed an issue that caused the project to enter an infinite loop at runtime if the Global Handler file contained an activity that threw an exception and the result argument was set to Continue.
- An error was thrown if you copied a sequence with an array of custom classes to another file, although the variables were properly displayed in the Variables panel.
- Search terms added in the Project or Snippets panels were improperly persisted when opening new projects in the same Studio instance.
- Fixed an issue that prevented the
project.jsonfile from updating with some arguments, and thus they were missed when publishing with UiPath.Studio.CommandLine.exe.
- Fixed an issue that allowed the user to create a variable using double-type characters and then convert it into an argument.
- When the user selected and deleted several activities in a Try Catch block, some activities from another expanded block would be removed as well
- Libraries that contained
Cas first segments were invalid. This was due to the fact that the generated namespace - abbreviated as
mc- is a namespace already in use by Microsoft.
- Fixed an issue that caused the Locals panel to be emptied out when Set Web Attribute, Get Attribute, Get Position, and Get Text activities hit an exception, and Slow Step was used.
- Fixed an issue that caused an error when moving a new file to a new folder part of a library in a SVN or TFS repository.
- Users are now able to perform copy actions from inside the designer on read-only documents.
- Fixed an issue that prevented GIT credentials from being persisted when pushing a project from a local repository to a remote one.
- We’ve made several fixes related to libraries. It is recommended to republish your libraries to benefit from them.
- Fixed an issue that caused the processes execution to fail if connection state errors were thrown beforehand.
UPath.settingsfile was not properly updated if you disconnected a robot while it was connecting to an Orchestrator instance.
- In rare circumstances, local processes were not displayed in the Robot Tray unless you clicked the Refresh button.
- The Robot was unable to connect via Proxy to the target machine over RDP. This happened when the Login to Console option was set to false.
- The Robot did not always lock the console if it was executed on a user that was already logged in but had its screen locked.
- The Robot Tray was not updated correctly if you started the execution of a process and closed it from Studio, and had the Keep in taskbar option enabled.
- Fixed an issue that caused the processes execution to fail if connection state errors were thrown beforehand.
- Workflow files (
.xaml) which contained multibyte characters in the name could not be published to Orchestrator.
- A validation method to ensure the LiteDB file is accessible at all times and not become corrupt was introduced. Read more on this page.
- Fixed an issue which caused the Custom Input activity URI to be ignored by the Global Exception Handler.
- The Robot would sometimes fail to connect to console on the user session after a job was executed on a previous session.
License Statusis now properly displayed for NonProduction and Unattended machines, in the
defaultTenantAdminPasswordparameters of the
Publish-Orchestrator.ps1script did not properly enforce password complexity rules.
- We identified and fixed an issue that caused the heartbeat to malfunction if the connection to Redis was lost. Now, the heartbeat is being sent regardless of the Redis-Orchestrator connection status.
- The logging configuration of the
web.configfile produced the Elasticsearch index
logflow-yyyy.MMwhere previously it was
default-yyyy.MM. This would impact any existing dashboards and visualization based on that index.
Telemetry.Enabledkey appeared twice in the
web.configfile if you updated your v2018.4.6 Orchestrator instance to v2019.4 or higher.
Migrate_Deployment_Settingsquery used incorrect column names, resulting in potential failure of the migration.
- Occasional deadlocks in the Orchestrator database would occur when: detecting unresponsive robots, simultaneously updating machines and deleting robots, or connecting multiple robots, with different users, on the same machine.
- When selecting authentication settings during a
Reset at first loginoption for the
Defaulttenant password would not work unless also checked for the
- If there was not enough free disk space, the
UiPathPlatformInstaller.exeinstaller previously would not start nor provide any error message. Now the installer performs a check of available disk space prior to starting.
- After a bulk update to enable or disable Tenants, only a single name would appear when reviewing the action on the Audit page.
- Alerts were not generated if a job was started on a process with missing input parameter values.
- Renaming a Robot, and then creating a second one with the name of the first, caused the errors on the Monitoring page to be misassociated. The errors of the first Robot were displayed for the second one instead.
- The tooltip for schedules defined with CRON expressions was incorrectly rendered if you used numbers instead of day names in the expression. For example,
0 0/30 19-20 ? * 1-5was displayed as
Every 30 minutes, between 07:00 PM and 08:59 PM, Monday through Fridayinstead of
Every 30 minutes, between 07:00 PM and 08:59 PM, Sunday through Thursday. Note that the job execution was performed correctly.
- Processes could not be executed on Robots which were installed in user-mode if they were defined in Orchestrator only using the username. This issue did not occur if you defined your Robot using the machine username format.
- Changes made to the input and output parameters of a process did not propagate to the existing associated schedules. Additionally, on the Edit Schedule window, parameters inherited from the process had their actual values displayed instead of the appropriate label.
- The CreationTime field in the Audit Data window for start job actions was not correctly populated.
- In some cases, language preferences were not persisted between login sessions.
- Performance issues were encountered when editing schedules (now called triggers) where a process was linked to an environment with a large number of robots.
- No error message was displayed when jobs associated to a schedule (now called trigger) could not be created due to having no robots defined.
- The Create Robot window was not properly displayed in Internet Explorer.
- When using the Invoke Power Shell activity, the
Microsoft.PowerShellnamespace is automatically imported in Studio.
- An exception was thrown when using the Data Extraction Scope activity together with a Try Catch activity. The issue was fixed and now the activity is executed as expected.
- When using multiple Validation Stations, the order of the derived parts was not respected in the validated results. The issue was fixed and now the results are displaying the derived parts in the same order they were introduced.
- Fixed an issue that was throwing an error when trying to train the Keyword Based Classifier activity in the training scope and the extraction was run without a classification reference. The issue was fixed and now the fact that there is no learning information is only logged, not thrown as an error.
- An error was thrown when using the FlexiCapture Extractor activity and the same name was given to both a table column and a field. The issue was fixed and the
.fcdotfile is now processed as expected.
- Fixed an issue occurring within the Update Object Properties activity. Now you can clear a property value by leaving SinglePropertyValue empty or setting it to Nothing.
- Fixed an issue which caused the Key Press Trigger activity to crash when it was set to monitor modifier keys.
- Users could create variables that contained invalid characters.
- The Anchor Base activity's body was erroneously drawn at design time.
- On 2K and 4K resolutions, Anchor/Target pairs valid at design time were valid at runtime.
- The Postpone Transaction Item activity did not properly function with older versions of Orchestrator.
- Fixed an issue which caused a memory leak when passing a
UiElementvariable as an input argument to an Invoke Workflow File activity.
- Attributes obtained from the IAccessible2 accessibility API were not validated.
- Particular elements were identified even if they had ancestor elements with the
- Using Data Scraping on an Excel table would return also return all empty cells.
- In some cases, child elements inside a popup window were not detected.
- Improved the behavior of the WaitVisible property to better identify elements inside the target window.
- Rarely, interactive selection on the first column of a CJSpread table would appear offset.
- Data could not be extracted from customized JTable cells, resulting in a thrown exception.
- An exception was thrown when trying to extract data from a JTable cell which contained invalid XML characters.
- Improved the selection of elements inside the Eclipse application.
- Element detection inside CAA Tables has been improved.
- Selectors were not generated for Java SWT apps.
- Adding an anchor from the Selector Editor window would cause the selector to become invalid.
The following patch versions are bundled in the
- Studio & Robot - 2019.10.1
- Orchestrator - 2019.10.14
- Remote Runtime – 19.10.7243.31457
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: