Read and Review Automation Anywhere Documentation

Automation 360

Close Contents

Contents

Open Contents

AARI variable types

  • Updated: 12/09/2020
    • Automation 360 v.x
    • Build
    • AARI

AARI variable types

Data flow (workflow engine) is the core part of a process that moves data between each task. Tasks require variables in order to run properly and three types of variables are available: input, output, and meta-type variables.

Variable types

Input
Users can use this type of variable in the process editor to return values that went “in” a task.
Output
Users can use this type of variable in the process editor to return values that went “out” a task.
Meta
Users can use this type of variable in the process editor to return high-level information about the request of a task.

Variable entities

Two types of entities can hold variables:

Request
Requests can only hold meta-type variables and have the following form: $<meta variable name>]$

This meta-type variable value is from the request.

Task
Tasks can hold three types of variables (input, output, meta) and have the following forms:
  • $<task>.<input|output>[<variable name>]$: This variable value is read from the task input or output.
  • $<task>.<meta variable name>$: This meta-type variable value is read from the task.

Date time variables

Name Entities Description
createdOn Request, Task Shows the date when the request or task was created.

Example: $createdOn$ or $Approval_Task.createdOn$

updatedOn Request, Task Shows the date when the request or task was last updated.

Example: $updatedOn$ or $Approval_Task.updatedOn$

Dictionary variables

Name Entities Description
assignedTo Task Shows information about the user who is assigned to the task.

Dictionary key: {id}, {username}, {email}

Example: $Approval_Task.assignedTo$

createdBy Request Shows information about the user who created the request.

Dictionary key: {id}, {username}, {email}

Example: $createdBy$

Number variables

Name Entities Description
executionCount Task Shows the number of times the task was run.

Example: $Name_Bot.executionCount$

id Request, Task Shows the numerical ID of a request or task.

Example: $id$ or $Approval_Task.id$

assignedTo{id} Task Shows the numerical ID of the user who is assigned to the task.

Example: $Approval_Task.assignedTo{id}$

createdBy{id} Request Shows the numerical ID of the user who created the request.

Example: %createdBy{id}$

String variables

Name Entities Description
status Task Shows the label of the button clicked (action) for a human task or the bot return code for a bot task (equal to failed when the bot fails).

Example: %Approval_Task.status$ or $Name_Bot.status$

title Request, Task Shows the title of the request or task.

Example: %title$ or %Approval_Task.title$

type Request Shows the task type (equal to BOT for bot tasks and FORM for human tasks).

Example: %Task.type$

assignedTo{username} Task Shows the username of the user who is assigned to the task.

Example: $Approval_Task.assignedTo{username}$

createdBy{username} Request Shows the username of the user who created the request.

Example: $createdBy{username}$

assignedTo{email} Task Shows the email of the user who is assigned to the task.

Example: $Approval_Task.assignedTo{email}$

createdBy{email} Request Shows the email of the user who created the request.

Example: $createdBy{email}$

Send Feedback