May 2023
30 May 2023
New execution setting
A new execution setting, Queues - Unprocessed queue items check frequency (minutes), is now available on the General tab of your tenant settings, allowing you to control the amount of time between checks for queue items that are waiting to be processed.
Mandatory webhook name
The Name parameter is now mandatory for webhooks created via the POST odata/Webhooks endpoint.
$count function calls
Calls to $count endpoints are no longer allowed, as they impacted API performance due to large data scans.
Collapsed App launcher menu
The App launcher menu in the top left corner of the application is now always collapsed, displaying the full list of products and services available to you only when clicked.
Packages with sources in the package explorer
Studio packages that are uploaded along with all their .xaml sources (i.e. the Include Sources option selected in the Publish options > Compilation settings section) can now be viewed in their entirety in the package explorer. This applies to Windows and cross-platform projects.
23 May 2023
Features out of preview
The video recording, live streaming, and remote control features are now out of preview.
19 May 2023
Registering ACR-VMs with Azure AD
Now you can register your ACR-VMs with Azure AD, provided that the VM is built on top of a Windows Desktop machine. Details...
16 May 2023
Apps in folders
Apps are now readily available in Orchestrator: they are always published to a tenant, and can subsequently be deployed in folders, enabling you to get up and running at lightning speed.
The Apps page allows you to deploy a published app, manage previously deployed apps, keep all your apps up to date with the most recent versions, run a deployed app, and go directly to an app project.
As part of this feature, two new permissions are available in Orchestrator: Apps and App Versions.
Erratum 13 June 2023 Due to a mishap on our side, this feature was not available on the original announcement day (16 May 2023).
3 May 2023
Blocking classic executions
Today marks the start of the gradual blocking of classic executions in classic folders.
This will occur throughout the next two weeks for Community organizations, with Enterprise organizations being scheduled for the month of June.
If you haven't already, please migrate your classic folders to the modern framework using the dedicated wizard or through manual migration.
Read more about the implications of this change, and why it is important to migrate as soon as possible.
Host feed changed
The URL of the official host feed for packages has been changed to https://pkgs.dev.azure.com/uipath/Public.Feeds/_packaging/UiPath-Official/nuget/v3/index.json, and the Myget feed is now deprecated.
If you are using a firewall, it is important that you add https://pkgs.dev.azure.com to the allow list. Otherwise, you will no longer be able to download official UiPath libraries.
New type filtering option in tenant search
The Action Catalog option has been added to the Type filtering menu in the tenant search window.
Improved behavior for Trigger APIs
Enabling or disabling a trigger via API returned "200 OK" regardless of the validity of the trigger ID, and you could only determine if there were any invalid links by the {"value": false} line in the response body, without the possibility to see which were those IDs.
To fix this behavior, the functionality of the /odata/ProcessSchedules/UiPath.Server.Configuration.OData.SetEnabled endpoint has been improved by adding the multistatusEnabled parameter (Boolean) to the request payload. The default value of the new parameter is "false", to preserve the previous behavior for backwards compatibility. However, an important change applies when you provide a single ID, which is invalid. In this case, the proper response code (for example, "404 Not found") is returned.
For when you provide multiple trigger IDs, setting the multistatusEnabled value to "true" changes the response output:
- If all IDs are valid, the response code is "200 OK".
- If at least one ID is invalid, the response code is "207 Multi-Status", and the response body lists all the invalid schedule IDs.
The following figure summarizes the new behavior of the endpoint:
Altering the transaction final state via API is now deprecated
As announced in January 2023, we're deprecating the possibility to alter the final state of a transaction using APIs. See the Deprecation timeline in our Overview guide for more information.
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.
Deprecation Timeline
We recommend that you regularly check the deprecation timeline for any updates regarding features that will be deprecated and removed.