Release date: 14th August 2017
In the first major release of the year, codenamed Moonlight, we concentrated our efforts on scalability and stability of the UiPath Platform, enabling you to build all those automation projects you have been planning all along.
The democratization of the RPA industry has always been a focus for UiPath, helping more and more people learn and easily automate an increased amount of processes over time. We directed our attention at making your experience easier, thus improving your performance, and reducing implementation time, using the most secure RPA platform on the market.
Documentation for the UiPath Platform was moved to an online environment, for an easier access to all available resources. Everything is available here: Orchestrator, Robot, Studio, and activities. Please feel free to suggest edits where you think they might be needed.
Scroll down to see the goodies we have in store for you.
An Orchestrator Host Admin concept has been implemented. The user with this role can create new tenants and tenant admins, directly from the user interface, thus giving you an enhanced control over the tenant creation flow.
As multi-tenancy is no longer experimental, and to easily support your ever-growing automation teams, this functionality is now enabled by default.
To further separate data between your automation teams, the automation packages published to Orchestrator are now also isolated per tenant. This adds a level of security and privacy for different teams, while also maintaining self-governance. For more information, see About Tenants.
As we know you like using queues a lot, we improved their performance. You can now manage millions of transactions without making Orchestrator or your Robots sweat.
Finding specific queue items is now possible through custom references. They can be added through the Add Transaction Item and Add Queue Item activities, and they can be keywords or specific terms. The reference can be used to link your transactions to other applications used within an automation project. Additionally, this feature enables you to search for certain transactions, in Orchestrator, according to the provided custom reference.
If you identify transactions that do not need to be processed anymore, you can now delete them. They are still displayed in the Transactions page, but their status is Deleted and they are no longer assigned to Robots.
Human input is a must-have in many key places in your automation. To enable this in retesting important data stored in transactions, it is possible to manually retry all queue items that have failed or have been abandoned. Lastly, you can also mark them as in review or verified.
For a better control over your queue processing procedures, you can create custom progress statuses for your In Progress transactions. To support this, a new field, Progress, has been added in the Item Details window in Orchestrator and a new activity, Set Transaction Progress, in the Core pack, which enable you to add the information. For more details on queues and transactions, please see our user guide.
To provide you with a contained environment and ease the automation process, the activities used to build your automation projects are also stored in a feed hosted on Orchestrator. The Robot can access this feed and simply download the activities it needs to execute a certain automation project. This ensures control over the activity package updates for all your Robots and even Studio, from a centralized point. Additionally, black-boxed machines can download the activities from Orchestrator when in a closed network. More details about how the feature works can be found here.
In addition to the security benefits implemented through all the other functionalities, Robot credential management is integrated with a third-party enterprise grade credential store. It is possible to store your Robot login credentials in CyberArk® Enterprise Password Vault®, through CyberArk®’s Application Identity Manager. For more information, see About Robots.
If you have a particular affinity for complicated pa$$w0rd$, we have some good news for you. You can customize the complexity of your login password requirements, from the Settings page. More details can be found here.
Support for global automation teams is added to the scheduling process. When you create or edit a schedule, you can select the timezone according to which the execution should start, independent of the tenant timezone.
Additionally, you can view the jobs started by your scheduled processes, directly from the Schedules page. This makes troubleshooting more straightforward, as it offers on-point details about each and every execution started by a schedule. Further information on these features can be found here.
This release focuses on the user experience, for an easier approach to daily tasks.
Troubleshooting complex automations can be quite a pain in some cases, therefore we came to the rescue and improved it. Logged messages have been moved: they are displayed per robot and per job, from the Robots and Jobs pages, with just a click of the button.
The Settings page has been reorganized and categorized, thus changing your tenant preferences has been simplified.
Queue item management has also been enhanced, as transactions are filtered and displayed per queue, providing spot-on information.
While we were tweaking and prodding through our code, for convenience, we also renamed the action of soft stopping a job to Stop, and that of forcefully stopping a job to Kill 💀.
As it also happens with the people operating them, the user interface gets better over time. A sleeker, more awesome looking interface based on Google’s Material Design has been implemented.
The grids that display component information, the right sidebar, filters and search functionalities were redesigned, the item’s status icons act as check boxes too (where applicable), and cosmetic changes have been done to most of the pages.
Interactive breadcrumbs and tabs were added to easily navigate through pages of related resources, such as the Robots and Environments pages.
As we always thrive to be up to date with the latest developments in technology, support for the 5th version of the Elastic stack has been added.
As an experimental feature, and to accommodate larger and larger automation teams, we introduced the concept of organization units. They add a deeper level of separation to Orchestrator resources (queues, processes, schedules, jobs, logs, assets, environments, and Robots) within tenants. Keep in mind that breaking changes may be added to this functionality in future releases. If you want to learn more about them, check out this user guide chapter.
Streamlining the deployment of multiple Robots to Orchestrator is possible as an automatic enrollment system has been implemented. Orchestrator generates a connection string that can be used with Robots to automatically connect them to Orchestrator, if you are using the Active Directory.
This feature enables you to use automatic deployment tools for the Robot installation process, and as you may have gotten used to, automate more! To view how this can be done, please take a look at this page.
To fast-track your deployment time and easily manage activation from a centralized location, Robot licensing has been added in Orchestrator, on a per tenant basis. You can see the remaining available licenses, per Robot type, and when you are due for a renewal, in the Settings page.
For Robots, this means that all you need to do to activate their license is to connect them to Orchestrator. For more information, see this topic.
To better convey the relationship between Robots, humans and Orchestrator, the following changes have occurred to them:
- The Front Office Robot has been renamed to Attended. It cannot run under a locked screen and it cannot be started from Orchestrator. This type of Robot is triggered by a user and runs only under human supervision.
- The Back Office Robot has been renamed to Unattended. It can be started from Orchestrator and can run under a locked screen without human supervision.
- The DevTest Robot has been renamed to Free. It has all the features of the Unattended Robot, but it cannot be used in production environments.
If you’re updating Robot information in Orchestrator, you no longer need to restart the UiPath Robot service. It’s all done automagically!
For more information about the differences between Robots, please see this article.
The UiPath Robot system tray has been redesigned to improve user experience. Visual feedback for the Robot’s connection status to Orchestrator is provided throughout the user interface.
The UiPath Robot Settings window presents a more intuitive way of connecting to Orchestrator.
As it was rarely used, enabling and disabling low level tracing for troubleshooting has been moved from the UiPath Robot Settings window to the command line.
You can automate the Studio activation process, alongside your installation, by using the code command. This further eases the deployment process of the project designer on multiple machines. A guaranteed IT department favorite. For more information on installing and licensing Studio, check out our user guide chapter.
To help RPA developers create and edit automations faster, a new Universal Search feature has been implemented, facilitating searching for activities, variables, arguments, imports and Library snippets all in one place. The Universal Search enables the user to find anything contained in the Activities, Libraries, Project and Designer panels of Studio.
Since one of the main goals of automation is better time management, the start-up loading time has been reduced by optimizing the way features load when the application is started.
The new Generate Table feature in the Screen Scraping wizard enables the user to generate a DataTable variable containing the previously scraped data.
By selecting separators for columns and newlines, unstructured data can also be extracted and stored in a DataTable variable by using the Generate Table wizard. If you want to find out more, see our user guide chapter.
To better control the activities you use, an activities packs feed is now hosted in Orchestrator. This enables machines that are in a closed environment to easily access activity packs if they are connected to Orchestrator. For a better understanding of our package manager functionality, see Managing Packages.
To ensure Studio maintains a fresh look, the UI has been slightly improved, featuring a more modern design.
The Screen Scraping window is redesigned, now having a friendlier, more intuitive interface.
The UiPath Studio, Orchestrator and Robot Windows installers are now bundled together, in one single package, called UiPath Platform. As we know most of you like to have control over things, this installer facilitates putting in place the entire UiPath suite, as well as all of its adjacent components by using advanced options, such as choosing which components of the UiPath suite are to be installed.
To insert custom VB.NET code functions, a new activity, Invoke Code, has been added to the Core activities pack. This activity can directly run a piece of VB.NET code as part of a project, enabling you to do things that we (maybe) haven’t thought of yet. You can find the activity documentation here.
A more complex version of the Select Item activity has been created, called Select Multiple Items, that can be used on HTML lists that support multiple selection. This activity also enables the retrieving of multiple items from a HTML list, if used alongside the Get Attribute activity with the selectedItems attribute. You can find the activity documentation here.
For an improved monitoring of transactions within an automation project, the Set Transaction Progress activity has been added to the Core activities pack. This activity changes the Progress field for a transaction item, informing you about the progress of transactions within the automation project, every step of the way. More details about this activity can be found here, and here.
For a more rigorous naming and increased clarity, the DeferDate property is renamed to Postpone and DueDate to Deadline for the Add Queue Item and Postpone Transaction Item activities. The changes are documented here, and here.
Add Queue Item and Add Transaction Item now have the Reference property, which can be used to tag items. By using these tags, identifying items in Orchestrator becomes a whole lot easier. You can see the documentation for the new property here, and here.
If using WebEx is your thing, we’ve got some great news - selection support now works while running WebEx!
- Fixed an error that prevented you from provisioning a Robot that had japanese characters in its name.
- In rare situations, disabling a schedule locked the database, and an error message was displayed in the Schedules page.
- If you delete a Robot from an environment, it is also deleted from schedules that were associated with the indicated schedule.
- It is now possible to create usernames with special characters, in the Users page.
- When using an environment with a Network Load Balancer, all server instances sent email alerts. Now, they are sent only once.
- Statistic updates for the Dashboard page are now limited to one per second, which improves its performance.
- In rare cases, if the Robot was not connected to Orchestrator and you ran a workflow from the tray, logs were always registered at the Verbose level. Now, the logging level selected from the UiPath Robot Settings window is taken into account.
- Scraping an application with no text with the Native technology on a 64-bit machine no longer crashes, working just like it should.
- If a selector contained one of the
colnameattributes, the UiPath Explorer crashed.
- The Chrome and Firefox extensions no longer crash when used in two parallel user sessions on the same machine.
- Fixed an issue that prevented you from selecting or identifying certain elements in PDF files, which were opened in Adobe Acrobat Reader.
- Although goodbyes are usually sad, we’re happy to announce that the Version field from the project.json file has been deprecated. Two fields have been added instead: ProjectVersion, which indicates the version of the published project, and ToolVersion, which specifies the version of UiPath Studio used to create the project.
- Studio no longer throws an exception when trying to record an automation with no project opened. The issue is also fixed for recording in a State Machine project.
- The Private property of the Open Browser activity is fixed, now working properly and opening Chrome in incognito mode.
- Type Into now supports non-ASCII Unicode characters.
- The Anchor Base activity can now be used to select UI elements inside Java applets.
- Keystrokes are now returned by the Get Event Info activity when used with Monitor Events.
- The Extract Structured Data activity can now extract empty columns, solving the issue of inconsistent table structures generated when scraping.
- If the servers you are working with have depleted their memory or if the database is overloaded, the Robots might not report their statuses correctly on the Robots and Jobs pages.
- If you edit the Robot name, the messages logged with the previous Robot name are no longer displayed in the Logs page. However, they are still displayed in Kibana and the database. Editing the name back to its previous state, displayed the logs once again in Orchestrator.
- If you are using a case-sensitive database and the tenant name contains at least one uppercase, publishing packages to a local NuGet feed fails with an Internal Server Error. If the NuGet feed is not local, publishing packages works correctly.
- If you group Robots from the same machine in different environments, and deploy them to different versions of the same package, some errors are displayed. We recommend using Robots from the same machine in the same environments.
- If you deploy processes that use different versions of the same activity on a Robot, the last available version of the activity is actually used when you start a job.
- Unattended Robots that are not licensed locally but are connected to Orchestrator cannot execute UI automation projects under a locked screen, if they are started from the Robot tray.
- Changes made to the UiPath.settings file are reset to their default state if you change the log level from the UiPath Robot Settings window or if the UiPath Robot service is running. For your configurations to be saved, ensure that both the Robot and its service are not running.
- If you start a job on a Robot that surpasses the RDP session limit on a machine, it remains stuck, waiting for the execution to start.
- The location of the activity packs has changed from
%LocalAppData%. This means that when you upgrade from the 2016.2 version to the 2017.1 one, the activity packs need to be installed again.
- In rare cases, after the workflow execution is finished, the following error can be displayed: "Workflow Designer encountered problems with your document.” Close and reopen the automation project to avoid this issue.
- The UiPathPlatform.msi does not support the Change, Repair or Update functionality for the Orchestrator component. In case you need them, please contact our support team and request the upgrade scripts.
- In rare situations, when making changes to the UiPath suite, the features that were installed are not correctly modified in the Product Features step of the wizard.
Support for the UiPath v2016.1 or lower has ended. UiPath will no longer provide updates and technical support for these versions. However, v2016.2 of the UiPath Platform is now on a Long Time Support track.