UiPath Release Notes

UiPath Release Notes

Release date: 3rd February 2020

 What's New

Queue Triggers

Aligning our Mobile app's features with those available on the web-based Orchestrator, we've added support for Queue Triggers. Create queue triggers in the Add Trigger page's new Queue tab. Remember to select a queue within the Select Queue page, and to set the trigger details within the Trigger Conditions page.

Edit triggers either by long pressing on each trigger on the Triggers page or by pressing the overflow menu in the top right corner of the Trigger Detail page. Note that once a trigger is created, you cannot switch its type. Read more about managing queue triggers here.

External Tasks

Starting now, the Orchestrator Mobile app also offers support for the external tasks just launched on the UiPath Platform. Note that you can only Complete these tasks, and you cannot view, assign or reassign them.

Filter the tasks by Type according to your preferences, selecting External to list the formless tasks.

Improvements

The messages we've implemented offer more clarity on the occasions when our Cloud Orchestrator is under maintenance. At such times you cannot access your service, therefore you are presented with a message like this: Orchestrator is undergoing scheduled maintenance. Sorry for the inconvenience. Please try again later.

We've also improved the messages displayed for situations when new builds requiring downtime are being deployed on UiPath Cloud Platform, resulting in communication issues with Orchestrator. Note that you can check status.uipath.com for status updates.

Note: The apps are released following a staged roll out process that adheres to safe deployment practices. Each day the app is available to an increasing percentage of users. The actual users are defined randomly by Apple & Google. The app becomes available to all users 7 days after the initial release date.

Updated 4 months ago


3.3


Suggested Edits are limited on API Reference Pages

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