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.
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.
Action Center 是一项许可功能，在授予用户访问权限之前，您必须获得许可证。
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.
在 Automation Cloud 中，将生成一个等待完成的活动。处理操作收件箱的操作管理员会进一步将项目分配给专门用户。该用户将收到操作待处理的通知。
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.
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||2019.10+|
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.
如果您使用的 UiPath.Persistence.Activities 版本低于 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 in Orchestrator has been dropped starting with the 2021.10 release.
Here are some features of the on-premises Action Center that you can benefit from:
- 在与 Orchestrator 相同的服务器上进行单独安装，或在不同的服务器上进行单独安装。
Warning: Although installed separately, Action Center requires a connection to an Orchestrator instance.
Warning: 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.
- 业务用户界面，从 Orchestrator 外部可以快速访问“操作”和“流程”。所有现有操作将自动反映在新用户界面中。
- Actions overview.
- More operations available on Actions, such as forwarding or reassigning.