UiPath Release Notes

UiPath Release Notes

March 2020

25th March 2020

Cloud Portal

What's New

We're preparing Cloud Portal to undergo some exciting changes. While doing so, we've restricted the use of the underscore _ at the end of account names, both during signing up for Cloud Platform or editing your organization settings.

24th March 2020

Orchestrator

Scalability in Unattended Deployments

In 2018.3 we introduced the concepts of attended floating robot and machine template.
Used together, the two became the ideal mechanism for handling deployments based on non-persistent VDIs, long shifts with hotseat change-overs, and generally environments with arbitrary machine/user combinations.

Machine templates took over the necessity of defining a Cartesian product between the sets of users and machines, in the sense that an environment with 8 users and 8 VDIs needs a configuration with one machine template and 8 floating robots, whereas before you would've had to define all 64 robot combinations between the two 8-sets.

In 2019.10, in an effort to decrease the deployment effort even more, we introduced attended robot auto-provisioning and management. It then became possible to automatically create an attended robot for whatever type of user identities you have in your instance. This, alongside robot settings and licensing needs can be configured directly at user level.

:dart+: If up until now you could only take advantage of these goodies through our attended plan, in this release we fully bring our solution to maturity, by turning our attention to our unattended offering. To this end, every behavior described above is now valid for unattended and non-production robots as well.

To sum up, the new main capabilities are focused on easy management of large deployments, regardless the robot type. They consist in efficient robot use via dynamic allocation, auto-provisioning, and non-persistent VDI support, if that your thing. Let's wrap up and call it a day with an article describing robots in modern folders.

Processes Display Name

This release ships with a feature allowing users to conveniently change the display name of a process. This is for all of you out-there republishing packages and recreating the processes because of a typo. We finally did it! 10/10 improved usability.

Action Center

The Tasks functionality has been treated to a major overhaul. It is now called Action Center, with actions instead of tasks working as the operational units of the center. Don't worry, the functionality itself stays the same. Details about actions here.

Breaking Changes

Starting with today’s deployment, you will no longer be able to start jobs or create triggers from Orchestrator on a Robot of type Studio or StudioX. This is what you need to do to keep your environment trouble-free:

  • If you use Studio in production environments via unattended scheduling configured in Orchestrator, use Unattended robots.
  • If you use Orchestrator in development environments to schedule and execute jobs on Studio or StudioX robots, use NonProduction robots instead.

Bug Fixes

The text inside an action was not readable when using dark theme. We made sure to fix that, and improved readability.

12th March 2020

Cloud Portal

What's New

This spring brings you a fresh look for your already known Cloud Portal. It’s a modest first step to some ambitious longer-term plans. We've reworked the entire UX to be cleaner, lighter and more intuitive for your daily activities. The Portal's modern look comes with a new header, fresher colors, crisp appearance for buttons, tables, and tabs.

Hopefully, you also noticed what hasn’t changed today: easy access to the functionalities. We’ve kept most elements in the same place – so that you can get things done while you get used to the new look. The small number of items that have moved around should now be more discoverable than they were before.

  • Dashboard becomes Homepage, with more functionality aimed at easing your automation process and your navigation to existing Orchestrator services. You can also see at a glance when those services were last updated. The License Usage graph and Distributed Licenses charts are also here, but with a twist - if there is no data to be displayed, an empty graph appears, instead of the No data available message displayed before.
  • Audit Logs was previously a bit of a treasure hunt if you weren’t an old hand at it. We've enabled you to quickly and easily check the audit trail, without diving through various menus to find the way in.
  • Organization Settings are now accessible through your User menu located in the top-right corner of every Cloud Portal page.

While the notification messages continue to show up, we've removed the Notifications page. From now on, the notifications bell icon in the top-right corner signals UiPath announcements regarding our products. Click the bell and then the announcement within to read our post on the UiPath Forum.

Read more about your Cloud Portal's new look in our Forum post. The product design team here at UiPath is committed to listening to your feedback.

Improvements

Navigation from Cloud Portal to the selected Orchestrator service is now performed within the same browser tab. In your Cloud Portal's Homepage or Services page, click the name of an available Orchestrator service to be instantly directed to that service.

Bug Fix

  • For accounts having AI Robots licenses, the License Usage Trend graph on your Homepage displayed zero activity lately due to a miscommunication between Cloud Portal and your Orchestrator services. We've fixed it so that future data should show up correctly. You can view the data from the missing period in your Orchestrator service's Dashboard.

10th March 2020

Orchestrator

What's New

Just a quick heads-up regarding upcoming Orchestrator changes:
Starting with 2020.4, you will no longer be able to start jobs or create triggers from Orchestrator on Studio or StudioX robots. While we are well aware this might bring adjustment pains, you need to know this happens in an effort to achieve a more streamlined business solution. Without further ado, this is what you need to do to keep your environment trouble-free:

  • If you use Studio in production environments via unattended scheduling configured in Orchestrator, use Unattended robots.
  • If you use Orchestrator in development environments to schedule and execute jobs on Studio or StudioX robots, use NonProduction robots instead.

In an effort to achieve better control in terms of Orchestrator performance, new queue items cannot contain Specific Data that surpasses 1 MB. Anything beyond this limit cannot be added to a queue. If you need to upload larger items, store the data in an external storage and only reference the link within the item.

We know that having too many columns in the column grid can be a pain, so for those of you who only want to see the most frequently used, we added a new button for controlling column visibility. By default, all columns are displayed on all pages. Click the Columns button and clear the check boxes corresponding to the columns you want to stay hidden. That's it. Have fun.

Updated 5 days ago


March 2020


Suggested Edits are limited on API Reference Pages

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