Define Actions and Queues

Introduction

In an app or Discovery Accelerator, you can define Actions and Queue items that will be displayed as tasks and robots in the UiPath Action Center. Similar to Tags and Due dates,Actions andQueue items are additional properties that you can define on an event.

You define the Actions for your Action center and Queue items to trigger robots in separate folders in the event view tables of the app or Discovery Accelerator.

Creating Actions and Queue Items

Note: If you are using the Basic Connector for AppOne, the groups and expressions described in this page are already predefined. You only need to edit the expressions to set the correct value.

Follow these steps to define expressions for actions and queues.

Step	Action
1	Open the App or Discovery Accelerator in your development environment and go to the Data tab.
2	Locate the events view table for which you want to define actions and queue items.
3	Create a new group Actionable insights in the table item list of the events view table.
4	Create subfolders for Actions and Queues.
5	Create expressions to define actions in the Actions folder. See Creating a queue item.
6	Create expressions to define queue items in the Queues folder. See Defining Actions and Queues.
7	Create an expression Actions in the Actionable insights folder. This should contain a list with all the actions in a Jointext function, where the actions are separated by Newlines. Note: Set the Availability of the expression to Private.
8	Note: Create an expression Queues in the Actionable insights folder. This should contain a list with all the queues in a Jointext function, where the actions are separated by Newlines.

See the illustration below for an example.

Note: If you need additional Case,Tag,Due date or Reference model information, you can retrieve this extra information with a lookup.

Creating an Action

Note: An Action Catalog must be configured for your tenant in UiPath Orchestrator. See Managing Action Catalogs.

Follow these steps to create a new Action.

Step	Action
1	Create an expression attribute in the Actions folder. This expression contains the logic for the action. The result of the action must be a JSONOBJECT, for which there is a function in our expression language.
2	Define the following mandatory properties for the action: • FolderID: The ID of the folder for which the action is created. • title: Display name of the action. • priority: The priority of the action to be done, Low, Medium, High, Critical. There are constants in the Globals table present to make sure you pick available priorities. • catalog: The catalog to which the action belongs. Note: this catalog should be predefined in your Action Center in the Orchestrator, otherwise it will not be shown. • message: A message containing specific information about the action.
3	Set the Availability of the expression to Private.
4	Add the new action to this list in the Actions expression in the Actionable insights folder. See the illustration below.

// This expression combines all actions.
// This expression is used in the globals table to define the input for actionable insights.
//Example:
jointext([
    Do_activity_A,
    Activity_A_is_finished,
    Due_date_is_today
], NL)

Your Actions will be created in the Action Center when you reload the Actions table or Reload all tables in the app or Discovery Accelerator.

Other tables

The following tables with attributes are needed to generate the output of your Actions.

• Globals

  • Actions Output
• Actions (runs Python script)

See the illustration below.

Creating a Queue Item

Follow these steps to create a new queue item.

Note: A Queue must be predefined in your Action Center in Orchestrator, otherwise the items cannot be added.

Step	Action
1	Create an expression attribute in the Queues folder. This expression contains the logic for the queue item. The result of the queue item must be a JSONOBJECT, for which there is a function in our expression language.
2	Define the following mandatory properties for the Queue item: • folderID: The ID of the folder for which the queue item is created. • name: The name of the queue, to which the queue item will be added. Note: this queue must be predefined in your Action Center in Orchestrator, otherwise the items cannot be added. • reference: A reference to the queue item. Note: It is recommended to use a unique reference. However, if the Unique Reference option in Orchestrator is set to Yes (see illustration below) for this queue, the queue item will not be created again when a queue item with this reference is already present in the queue. If the Unique Reference option is set to No, the queue item will be added to the queue even when a queue item with this reference already exists.
3	If required define the following optional properties for the Queue item: • priority: The priority of the queue item to be done, Low, Normal, High. There are constants in the Globals table present to make sure you pick available priorities. Note: If the priority is not specified in the Queue Item definition, it is set to high by default. • deadline: The latest time at which the queue item should be processed. • postpone: The earliest time at which the queue item is available for processing.
4	Set the Availability of the expression to Private.
5	Add the new action to this list in the Actions expression in the Actionable insights folder.

Orchestrator setting Unique Reference

See the illustration below.

Jointext function

See the illustration below.

// This expression combines all queue items.
// This expression is used in the globals table to define the input for actionable insights.
//Example:
jointext([
    Queue_item_for_activity_A,
    Queue_item_for_activity_B
], NL)

Your Queue items will be created in the Action Center when you reload the Queues table or Reload all tables in the app or Discovery Accelerator. See the illustration below.

Note: There are optional arguments that can be passed on in a Queue item. This information will be shown in the details of a queue item. These arguments also need to consist of a key and a value. Examples are Case,Amount, etc.

Other tables

The following tables with attributes are needed to generate the output of your Queues. Do not change these attributes.

• Globals

  • Queues Output
• Queues (runs Python script)