Subscribe

UiPath Action Center

The UiPath Action Center Guide

Lights :bulb+:, camera :movie-camera+:, Action Center :white-check-mark+:!

Introduction

This page will help you get started with Action Center. You'll be up and running in a jiffy!

Overview


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.

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 Action Center web app. We recommend taking advantage of the new experience, as after the transition is complete, Actions capabilities will be removed from Orchestrator, and so will be the documentation.

🚧

Important

Action Center is a licensed feature, you are legally bound to procure licenses before granting access to users.

Behavior


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 on the Action Center website. 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 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 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.

task_flow

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.

Access Control


In order for a user to be able to use Action Center services and the desired level of access, they require the corresponding permissions on Actions, Action Assignment and Action Catalogs in Orchestrator.
Learn About Roles in Orchestrator.

User Personas

Document Validation Admin

The validation admin sees all the generated document validation actions and handles having them assigned to users on the Administer page. Can also validate an action themselves. Should be granted the following permissions:

  • View, Edit on Actions
  • View, Edit, Create, Delete on Storage Files
  • View on Storage Buckets
  • View, Edit, Create on Action Assignments
  • View, Edit, Create on Action Catalogs.

Document Validation User

The validation user sees all the form and document validation actions assigned to themselves such that they are able to validate them on the My Actions page. Should be granted the following permissions:

  • View, Edit on Actions
  • View, Edit , Create on Storage Files
  • View on Storage Buckets
  • View, Edit on Action Assignments

Document Classification Admin

The classification admin sees all the generated document classification actions and handles having them assigned to users on the Administer page. Can also validate an action themselves. Should be granted the following permissions:

  • View, Edit on Actions
  • View, Edit, Create, Delete on Storage Files
  • View on Storage Buckets
  • View, Edit, Create on Action Assignments
  • View, Edit, Create on Action Catalogs.

Document Classification User

The classification user sees all the form and document classification actions assigned to themselves such that he is able to validate them on the My Actions page. Should be granted the following permissions:

  • View, Edit on Actions
  • View, Edit on Storage Files
  • View on Storage Buckets
  • View, Edit on Action Assignments

Form Action Admin

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 themselves. Should be granted the following permissions:

  • View, Create on Action Assignment.
  • View, Edit, Create on Action Catalogs.
  • View, Edit, Create on Actions.

Form Action User

The action user sees all the form actions assigned to themselves such that they are able to validate them on the My Actions page. Should be granted the following permissions:

  • View, Edit, Create on Actions.

Robot Role

In order for the Robot to generate an action, upload, download and delete data from a storage bucket, it needs the appropriate permissions. Make sure the Robot role has been granted the following:

To create an action:

  • View, Edit, Create on Actions

To upload document data:

  • View, Edit, Create on Storage Files
  • View on Storage Buckets

To delete document data after downloading:

  • View, Edit, Delete on Storage Files
  • View on Storage Buckets

Prerequisites


In order to build and execute long-running workflows, the following Studio/Robot and UiPath.Persistence.Activities requirements must be met:

Software

Version

UiPath Studio/UiPath Robot

2019.10+

UiPath.Persistence.Activities activity package

1.1.7+

Updated 2 months ago


Introduction


This page will help you get started with Action Center. You'll be up and running in a jiffy!

Suggested Edits are limited on API Reference Pages

You can only suggest edits to Markdown body content, but not to the API spec.