Action Center offers business users a way to handle actionable items, and provide business inputs to Robots. It enables support for long-running unattended workflows, that require human intervention. The execution of long-running workflows is fragmented. Therefore, Action Center allows you to suspend and resume the workflow, 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 used to complete the workflow execution.Important: Action Center is a licensed feature, you are legally bound to procure licenses before granting access to users.
How Action Center Works
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 that can be completed by users in Automation Cloud. After an Action is handled by a human, 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 that the job is waiting on.
Granting user access
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.
- When the Azure AD integration is
enabled, you cannot assign tasks to users in Action Center if they haven't signed in using
their AD account. The same behavior occurs for local user groups , when the users
haven't signed in using their local user account.
Workaround: Consider asking your users to sign in after their accounts have been created, using either their AD or local user account. 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 the case of folders that have permissions set for DirectoryGroup, all Azure AD users appear in the Assign To User dropdown list, even if they don't have permissions for the specified folder. Even if users without the appropriate permissions show up in the Assign To User dropdown list, you can't assign Actions to them. This behavior is a user interface issue only, caused by an API that returns all Azure AD users, regardless of their folder permissions.
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 using 2022.4 activity packages or higher.
There is a chance job execution will fail if you use UiPath.Persistence.Activities versions lower than v1.1.7.
Here are some features of the on-premises Action Center that you can 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.
- Actions overview.
- 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.