Action Center offers a way for business users to handle actionable items and provide business inputs to Robots. It enables support for long-running unattended workflows that require human intervention as workflow execution is fragmented and can be suspended and resumed at a later time after human input is provided.
There are two facets of Actions Center:
- Processes—Enable users to launch unattended processes.
- Actions—Enable users to provide inputs to Robots, which are later on used to successfully complete the workflow execution.
For the time being, actions can also be managed in Orchestrator as a way to help you smoothly transition to the new paradigm.
Actions capabilities in Orchestrator are limited and do not include the features documented in this guide. To take advantage of the new capabilities, use the dedicated on-premises Action Center. We recommend taking advantage of the new experience, as starting with Action Center v2021.10, Actions capabilities will be removed from Orchestrator, and so will be the documentation.
Action Center is a licensed feature, you are legally bound to procure licenses before granting access to users.
A long-running workflow in which human validation is required is configured in Studio using the Orchestration Process template and specific activities.
Such a workflow generates actions to be acted upon by users in Action Center. After an action is human-handled, the execution is routed back to the process, as marked in the workflow by the corresponding activity, and gets executed on an available UiPath Robot. In the context of long-running business processes, this allows for better resource allocation and reduced execution downtime, especially since the fragments of the jobs can be executed by any available Robot.
Once an action is generated, it is displayed on the Actions page with the status Unassigned. Attributes like priority, title, or action catalog are populated based on how the action was customized in Studio using the corresponding activity.
Actions are grouped according to user-defined criteria in Action Catalogs that need to be defined in Orchestrator first and then set at action creation in Studio, using the same activity mentioned above.
Say you have an invoice-processing workflow. A user with execution permissions starts a job for the corresponding process.
The job is executed as usually, up until it encounters the activity which suspends it. That's when human intervention is required.
In Orchestrator > Actions tab, an activity is generated awaiting completion. An action admin who handles the actions inbox, further assigns the item to a specialized user. The user gets notified that an action is pending.
After the action has been validated, the job is resumed and the execution is finished by any Robot that is available.
Since fragments of the same job can be executed by different Robots, the corresponding logs target the entire job progress, providing a summary of the execution beginning with Robots, human-reviewer, and the triggers the job is waiting on.
In order to build and execute long-running workflows, the following Orchestrator, Studio, UiPath Robot, and UiPath.Persistence.Activities requirements must be met:
UiPath Studio/UiPath Robot
Authenticating your Robot using Secure Authentication requires recompilation of workflows that use Orchestrator activities or make direct HTTP calls to the Orchestrator API utilizing v2020.10 activity packages or higher.
The job execution may fail if you use UiPath.Persistence.Activities versions lower than v1.1.7.
If you are currently using Action Center within Orchestrator (the Actions tab), consider moving to the on-premises Action Center, as the Actions tab and functionality in Orchestrator will be dropped starting with the 2021.10 release.
Here are some features of the on-premises Action Center that you will benefit from:
- Separate installation on the same server as Orchestrator or on a different one.
Although installed separately, Action Center requires a connection to an Orchestrator instance.
One Action Center (single node or multi-node supported setup) can be connected to one Orchestrator, either a production or a non-production environment. To connect to more Orchestrator environments, you need to run an equal number of different Action Center installations.
- Business user interface, with quick outside-Orchestrator access to Actions and Processes. All the existing actions will be automatically reflected in the new UI.
- Ability for business users to trigger unattended processes through forms or file uploads, and track the process status.
- Ability to add any file attachments to actions.
- Action summary.
- More operations available on actions, such as forwarding or reassigning.
- Intermediate Save, allowing you to save the progress made on a form before completion.
- Peer collaboration on actions through the Comments panel.
- Bulk actions management (assignments, deletions, forwarding).
- Downloadable action lists, containing details such as action creation time, title, status, the assigned user, etc.
- Improved filtering and sorting options.
Updated 18 days ago