26 May 2021
Orchestrator in the Left Rail
Orchestrator is now shown on the left rail in Automation Cloud, the same as your other services.
You can continue to access Orchestrator from the Home page, but now you can also switch to Orchestrator from any page in Automation Cloud without having to return to Home.
Remember, while in Orchestrator, you can use the tenant picker in the top right to switch between tenants without leaving Orchestrator.
4 May 2021
May the 4th be with you!
Apollo for Orchestrator
Today we are advancing our cloud journey by further melding the cloud Orchestrator service into Automation Cloud with the adoption of the freshly launched Apollo design system. What this means for you is consistency in the user interface across the Automation Cloud services and Orchestrator, easier navigation, and some user interface improvements.
Most Notable Changes
While Orchestrator itself remains functionally the same, there are a few things you should know right off the bat:
You no longer leave Automation Cloud when you open Orchestrator. Instead, Orchestrator opens in the page area and you retain access to the following shared Automation Cloud controls: the user menu (a), the header (b), the tenant picker (c), and the left rail (d) from where you can switch to one of your other services:
Some controls have moved out of Orchestrator menus to the shared Automation Cloud header.
The user menu (previously in the top right in Orchestrator) is now replaced by the Automation Cloud user menu (top left). This includes the options for user language selection, theme selection, and the sign out option:
You can now use the tenant picker in the shared header to switch tenants without leaving Orchestrator:
For more details about these changes, also see this forum post.
Searching for packages and libraries in Orchestrator did not work for NuGet packages in external feeds. We've improved search term extraction and searching now works as expected.
The metadata for the
/odata/ProcessSchedules/UiPath.Server.Configuration.OData.SetEnabled endpoint was incorrect, leading to a generated OData client failing to call the endpoint.