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 directly from the Automation Cloud portal.
- Actions - Enable users to provide inputs to Robots, which are later on used to successfully complete the workflow execution.
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 Automation Cloud. 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 in Orchestrator, it is displayed on the Actions page with the status Unassigned. Attributes like priority, title or 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 which 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 Automation Cloud, 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.
User access in Automation Cloud and Automation Cloud services is based on user groups. In order for a user to be able to use Action Center services and the desired level of access, their parent group requires the corresponding permissions on Actions, Action Assignment and Action Catalogs.
See the Leveraging User Groups section for details about user groups.
The action admin sees all the generated form actions and handles having them assigned to users on the Administer page. Can also validate an action himself. Should be granted the following permissions:
- View, Create on Action Assignment.
- View, Edit, Create on Action Catalogs.
- View, Edit, Create on Actions.
The action user sees all the form and form actions assigned to himself such that he is able to validate them on the My Actions page. Should be granted the following permissions:
- View, Edit, Create on Actions.
In order to build and execute long-running workflows, the following Studio/Robot and UiPath.Persistence.Activities requirements must be met:
UiPath Studio/UiPath Robot
UiPath.Persistence.Activities activity package
Updated about a month ago
|How to enable Actions|
|How to enable Processes|
|How to build long-running workflows in Studio|
|How long-running workflows reflect in Orchestrator|