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.
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, 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 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.
To allow users to operate in Action Center services, set the desired level of access for their user groups, by granting the corresponding permissions on Actions, Action Assignment, and Action Catalogs.
See the Leveraging User Groups section for details about user groups.
Action Center cannot see Azure AD users who haven't signed in
With the Azure AD integration active, Action Center cannot see those Azure AD users who have not singed in yet using their directory account and so you cannot assign tasks to them.
Workaround: Ask all your users to sign in one time using their directory account. The account must link to the Orchestrator instance configured for Action Center. Alternatively, you can continue to assign tasks to the user's UiPath account, but then organization administrators should delay the task of discontinuing UiPath account use until the issue is resolved.
In order to build and execute long-running workflows, the following 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.
There is a chance job execution will fail if you use UiPath.Persistence.Activities versions lower than v1.1.7.
Updated about a month ago