Subscribe

UiPath Orchestrator

The UiPath Orchestrator Guide

September 2022

27 September 2022

VPN gateway for serverless cloud robots (preview)

📘

This feature is only available to customers who have signed up for preview from the UiPath Insider Portal.

You can now use your tenant-level VPN gateway for serverless cloud robots as well.
Automation Cloud™ robots - Serverless

 

16 September 2022


New scheduling system

We have integrated a new scheduling system, which uses an internal library tailored for performance. As such, it allows for better and faster trigger scheduling, with much shorter delays, to the tune of maximum 30 seconds.

 

19 September 2022


Modern migration wizard is now GA

With general availability, the Modern migration wizard is now available to all customers.
Migrating from classic folders to modern folders

Error codes in unsuccessful request responses

Explicit error codes are now displayed in the responses returned by CyberArk CCP when a request is not successful.

Absolute time columns

We added new time columns on several Orchestrator pages to display the action absolute timestamp, in addition to the relative time: Audit, Alerts, Jobs, Triggers, Logs, Testing. The new time format includes milliseconds, thus ensuring a detailed view.
To see the new columns, you must select them individually on each page, as they are not visible by default.
Note: Absolute timestamps are rendered in the tenant time zone. For triggers, the next run time is rendered in the trigger time zone which may differ from the tenant time zone.

Personal Workspace APIs

Personal workspace endpoints have been exposed and are now available for you to use them in your API requests:

  • GET /odata/PersonalWorkspaces - retrieves personal workspaces;
  • POST /odata/PersonalWorkspaces({key})/UiPath.Server.Configuration.OData.StartExploring - starts an exploratory session of a personal workspace on the current user;
  • POST /odata/PersonalWorkspaces/StopExploring - ends an exploratory session of a personal workspace for the current user;
  • POST /odata/PersonalWorkspaces/ConvertToFolder - converts a personal workspace into a folder;
  • GET /odata/PersonalWorkspaces/GetPersonalWorkspace - retrieves details about the personal workspace of the current user.

Converting the personal workspace with a certain ID into a modern folder via API.

Bug fixes

We fixed a deadlock that was preventing new jobs from being created in classic folders, while using specific robots.

 

13 September 2022


Automation CloudTM Robots - Serverless: Regenerate client secrets

When using client credentials to connect your serverless robots to Orchestrator, what happens behind the scenes is that the serverless machine template generates a client ID - client secret pair that authorizes the connection between that host machine and Orchestrator. This provides the serverless robot on that machine with access to Orchestrator resources.

If you feel that the client secret has been compromised, you can now regenerate it.

799799

 :

7 September 2022


Classic to modern migration wizard (preview)

This is a preview feature and is only available to:

With the upcoming deprecation and removal of classic folders, we have created a migration wizard to assist you in transitioning your tenants from using classic folders to using modern folders.

The wizard can greatly reduce the required migration effort by recreating your existing classic folder hierarchy and resources in modern folders.

For more information about the wizard and instructions, see Migrating from classic to modern folders.

For more information about the differences between folder types, see Classic folders vs modern folders.

 

5 September 2022


Studio triggers in Orchestrator

Queue triggers in personal workspaces

Now, when you publish a Studio project containing a queue trigger activity to your personal workspace feed, a queue trigger gets automatically created in Orchestrator. A few notes to have in mind:

  • Republishing the automation project to Orchestrator overwrites the queue trigger properties set by the activity.
    For example, if you manually edit a queue trigger in Orchestrator and set an alert option, this setting will be preserved at republishing. However, a queue trigger’s SLA prediction, which is a property configurable in the queue activity, will be overwritten by the value set in the activity in the workflow.
  • At publish time, Orchestrator chooses from the available personal workspace's runtimes to execute the job. The runtime precedence is the following:
    1. Serverless
    2. Production (Unattended)
    3. Nonproduction
    For example, if no Serverless runtimes exist in your personal workspace, Orchestrator uses available Production runtime. If that doesn't exist either, Orchestrator uses an available NonProduction runtime. If none exists, the job fails.
    Note: If the selected runtime becomes unavailable between job executions, the upcoming job execution fails, since Orchestrator does not look for the next available one.

📘

Important:

The queue trigger activity is available in the UiPath.System.Activities pack and UiPath Studio version 22.8.0-preview. It will become generally available with the 22.10-GA version of the UiPath.System.Activities pack and UiPath Studio.

Managing connected trigger requirements in your processes

Starting today, Orchestrator provides you with the means to configure the queue triggers and time triggers in your processes via the Package Requirements tab. This allows you, for example, to create missing queue and time triggers. Find out more in our documentation.

 


When can I see these changes?

The date when a change is first announced in the release notes is the date when it first becomes available.
If you don't see the change yet, you can expect to see it soon, after we roll out changes to all the regions.

More information

Deprecation timeline

We recommend that you regularly check the deprecation timeline for any updates regarding features that will be deprecated and removed.

Updated about a month ago


September 2022


Suggested Edits are limited on API Reference Pages

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