UiPath Community 20.10 Release - Orchestrator

UiPath Community 20.10 Stable Release

As we approach our LTS enterprise release date, we took the time to review what changed in Orchestrator over the last 6 months. :mailbox_with_mail:
It all starts with a completely new user experience, but it doesn’t end there. Check below all the new features and improvements the team delivered and please continue to share your feedback with us to help us improve in the upcoming releases. :rocket:

Modern Folders

  • The new Orchestrator UX heralds a brave new world for your deployment management - out with Classic (folders) and into a Modern only world. We have disabled classic folders for all new tenants, making the modern paradigm the default option for new users and deployments. Details about the new UI here.
  • To streamline robot migration from classic folders to modern folders, we’ve made it possible to easily enable/disable robots residing in classic folders. This way, you are presented with a rollback option if a step errors out during migration.

Folder Packages

To help with delegating responsibilities in your company while keeping packages separate, first-level folders can now be created with a dedicated packages feed. See how here.

Personal Workspaces Experience

  • Personal workspaces come with their own packages feed by default and mark a historical minimum in package deployment efforts as any package that is added to the workspace gets automatically deployed as a process in the workspace.
  • Keep an eye on all workspaces from a centralized location and give a helping hand to developers in their daily activities by exploring the contents of their personal workspaces at a glance.
  • Keeping Orchestrator clean of unused data is now a breeze as you can easily identify all workspaces with little or no activity, or those which have been orphaned upon employees leaving the organization. The clean-up strategy is at your discretion and is pretty much hassle-free, as you can either delete or convert the workspace into a folder from the convenience of the dedicated Personal Workspaces page.
  • To help new users in their automation journey, we’ve added a simplified UI profile in Orchestrator for those using personal workspaces, so the user experience is stripped down to the functionality available in their workspace. Learn about UI Profiles

Unattended Automation

  • To ease unattended automation ordeals concerning local Windows users residing on multiple host machines we made sure that unattended robots impersonating local accounts only require the corresponding Windows username and password - the host machine is no longer a mandatory identifier. Say you are using LocalUser1 on 5 host machines. Instead of having to set up 5 user entities in Orchestrator for each combination, you define the unattended robot on one user entity only, using the .\LocalUser1 syntax in the Domain\Username field.
  • If you were looking for better-debugging capabilities, rest assured, as of now, you can select the host machine on which a certain job is launched. Click here for details about jobs.

Processes Improvements

Among all the usability improvements we are excited about, this release we are especially excited about solving some common frustrations regarding processes.

  • Updating processes across multiple folders to the latest available package version just became easy-breezy with a new bulk update feature which enables you to upgrade all processes associated with a package. Simply select the target packages, and Orchestrator does the job for you by searching for and displaying all associated processes which are not using the latest available package version. Choose the processes to be updated to the latest available package version and you’re done.
  • To help you easily identify and differentiate processes from one another, regardless if they are deployed manually or automatically in a personal workspace, processes now inherit the description of the associated package as set at design time in Studio. Furthermore, you can also add a description to your processes or edit the existing one as you wish, no restrictions imposed.
  • To increase the level of control you have over your processes, we’ve added the Always Running Process option on the Process Setting page to restrict process termination from the UiPath Assistant.

Automatic Trigger Disabling

You can now configure automatic trigger disabling with two new parameters: Triggers.DisableWhenFailedCount and Triggers.DisableWhenFailingSinceDays. The trigger gets disabled automatically after a certain number of failed launches (Triggers.DisableWhenFailedCount) if it hadn’t been successfully launched in a specific number of days (Triggers.DisableWhenFailingSinceDays).

Test Data Management

Decrease your time spent on testing by managing your test data through test data queues and synthetic test data creation. The Test Data Queue is your central storage where you can prepare, store, and consume test data. You can expand your testing efforts through test cases that store and consume queues items in and out of the test data queues, on a FIFO (first-in-first-out) order.



Does “out with Classic (folders) and into a Modern only world” mean that in the future, we really won’t have classic folders available?

Yep! As we are closing the feature gaps between old and new way of managing the robots/machines/processes, there won’t be a need for classic folders – we will only have … folders :). But that won’t happen for a while - we are doing all efforts to make sure migration is smooth and all current use cases can be implemented in modern folders as well (easier and faster).

1 Like

This version will fix that old problem where the Transaction Item “progress” value get erased whenever the Transation State is not “In Progress”?

Yes. Fixed.

1 Like

Please work with support

Do parameters entered for a Process in Orchestrator now flow through to an attended bot started through the task tray icon?

If not, this is an enormous oversight. I see in the forums people have been asking for this for YEARS. It’s a gigantic road block to improvements we’re trying to make in our development standards - specifically getting rid of the clunky Excel config file stuff.

So we upgraded to 2020.10.4 Orchestrator and 2020.10.2 Studio/Assistant.

Now Assistant shows the parameter value as set in Orchestrator. But when you run the bot it doesn’t actually USE that value. It still gets the value from in the code/Studio.

Yes, that’s right - even though it shows you the parameter value as configured in Orchestrator, it doesn’t actually USE that value. Ridiculous.

If you manually CHANGE the value in Assistant, then it uses the value you put into Assistant.

Of course that’s not good either. We don’t want end users to be able to see and change these things. This is very, very poor design, lacks common sense and solid usability.

Hopefully there’s a way to prevent users from seeing, or at least changing, parameter values.

Hi there, I have started to test Modern Folder on 2020.10.4 version (Cloud) and have few items to address/ask.

  1. User role that allows to update the UserID for changing Unattended Robot (UserName + Password) the in the folder’s level requires ‘Edit’ user permission. For example, RPA Admin (tenant’s level) wants to give the customers an ability to manage their resources under modern folder - each function can have 1 parent folder level. However, those Folder’s admin will not be able to ‘Edit’ user for input/change the UserID to enable Robot nor unable to change the credential without Tenent’s User -Edit permission. That is where i found a little worried that Folder’s admin level can Edit user at the Tenant level which can cause quite a mess to the Tenant Administrator.

  2. ‘Trigger’ does not have the Machine selection unlike the ‘Process’ that we can pick the UserID and the machine. Yes, Trigger normally pick up any available machine from the machine-template, but there are also cases which UserA has to use MachineA specifically when scheduling Automation in advance.

I think those 2 items that should be useful feature for an enterprise scale.

Thanks a lot

Patom P

Please share the further details where to find and update this settings to completely turn off this feature ? @Ovidiu_Constantin