Configure the Task Tab
This content applies solely to Appian RPA, which must be purchased separately from the Appian base platform.


On the Task tab of the robotic task configuration page, you can configure the following settings:

Example Task Tab

Robotic task definition

Robotic tasks follow a specific sequence. The definition is the guide that leads the robotic task's operation, determining its starting point and driving it through a series of tasks and actions.

Do you need more information about robotic tasks before you configure the Task tab? The Robotic Task Definition page has the information you need.

Configure a robotic task definition

Required role: Developer or Administrator

To configure a robotic task definition:

  1. Go to the Robotic tasks tab.
  2. Find the robotic task you want to configure in the list.
  3. Click Configure 2236505.png in the Actions column.
  4. Go to the Task tab of the robotic task configuration page.
  5. Add actions to the robotic task definition.
  6. Add conditions and loops.
  7. Configure the actions you added.
  8. Move actions or delete actions as needed.
  9. Click SAVE CHANGES in the page toolbar.

Looking to speed up robotic task definition design? Create robotic task definition sections using the task recorder.

Add actions to the robotic task definition

To add an action to the robotic task definition:

  1. Click and hold an action in the Palette.
  2. Drag and drop it to the section or action group where you want to add the action.
  3. Click and drag the action to reorder it relative to the other actions in the section or action group.

That's it! You can configure the action in the Configuration Pane.

As a best practice, limit each action in your robotic task to 12 or fewer nested actions. Having more than 12 nested actions can lead to performance problems. Instead, split the robotic task into smaller robotic subtasks to prevent problems from occurring.

Action groups

Action groups help you organize actions that work together to achieve a desired outcome. For example, you may want to organize your robotic task definition so that login actions are contained in an action group.

To add an action group to the robotic task definition, click and drag Action Group from the Actions Palette to a section.


The robotic task designer allows you to quickly configure conditional flows. Conditional flows are decision points for a robotic task's execution, where the path of the flow adjusts based on specified conditions. The results of conditional actions determine the path the robotic task will follow. Use conditional actions to make your robotic tasks more dynamic. For example, if a web element is present, copy the value; otherwise, add an error message to the log.

Conditional actions only return true or false and include:

When you place conditional actions in the robotic task definition, they automatically generate Yes or No flows to configure. Actions that return true map to Yes flows; actions that return false map to No flows. Add actions to the resulting flows just as you would for the main robotic task definition.

Conditional action screenshot


Loops repeat actions until a condition is satisfied. Use the Loop action to process items in a list such as files in a directory or line items on an invoice. RPA supports the following loop types:

  • While: Executes the loop until the loop expression returns false.
  • Repeat: Executes the loop a fixed number of times, equal to the integer in the Iterations field.
  • For Each: Executes the loop for each item in a list.

Loops can't repeat more than 1000 times.

In the following example, the loop will execute the Create a folder and Copy a file or folder actions until the Loop Expression returns false.

Screenshot of the loop action in the system

To add and configure a Loop action:

  1. Click and hold the Loop action in the Actions Palette.
  2. Drag and drop the action to a section or action group.
  3. Select a loop type from the Configuration Pane.
  4. Configure additional properties from the Configuration Pane depending on the loop type.
    • While loops must have a loop expression.
    • Repeat loops must have a number specified in the Iterations field.
  5. Drag and drop additional actions from the Actions Palette into the loop action. Actions will only repeat when inside the Loop action.

Action expressions in loops can reference function variables (../ Supported function variables in loops include:

Function Variable Description While Repeat For Each
fv!index The current iteration of the loop, starting at 1. Yes Yes Yes
fv!isFirst true for the first iteration of a loop, otherwise false. No Yes Yes
fv!isLast true for the last iteration of a loop, otherwise false. No Yes Yes
fv!itemCount The total number of loop iterations. No Yes Yes
fv!item The current item. No No Yes

Configure an action

When you add an action to the robotic task definition, the configuration options appear in the Configuration Pane within the designer. The configuration options vary based on the action you're adding.


See the action documentation for details on each action's configuration options:

  1. If your selected method includes CONFIGURATION parameters, configure the parameters as appropriate:
    • Enter a static value.
    • Select a robotic task variable from a picker.
    • Use the Expression editor to write an Appian expression. You can reference a robotic task variable in the Expression editor using pv! and concatenate variables as needed.

    For example:


  2. If your selected method includes OUTPUT parameters, configure the following parameters:
    • Operator: Select an option to store the value as a single-value variable (is stored as) or add the value as a multiple-value variable (is appended to).
    • Target: Enter the name of the robotic task variable where you want to store or append the value. If your variable is type CDT, you can specify which field of a CDT to store the value into using dot notation.
  3. Configure the AFTER COMPLETION parameters:
    • Wait before executing next action: Enter the number of seconds the robotic task waits before it continues to the next action in the robotic task definition.
    • Take a screenshot: If you select this option, the robotic task takes a screenshot of the host machine immediately after the action completes successfully.
  4. Click SAVE CHANGES in the page toolbar.

Move an action

To move a single action within a robotic task definition section, drag and drop the action to a new position.

Delete an action

To delete an action, hover over the action and click Delete action.

Robotic task variables

Robotic task variables can store and pass values in your robotic task's definition and even between your robotic task and other design objects.

Similar to process variables in a process model, robotic task variables are placeholders for data that can be accessed throughout the lifecycle of a robotic task. These variables can be referenced in actions to display values or to store an action's result value and use it later in other actions of a workflow. You can also set robotic task variables as parameters so they can be used as input fields in a robotic task's execution.

Do you want more information about robotic task variables? The [Robotic Task Variables] page in the Learn category has more information to get you started.

Create a new robotic task variable

Complete the following steps to create a new robotic task variable. You can also create robotic task variables as you record actions with the task recorder

  1. Go to the Task tab of robotic task configuration page.
  2. Find the Variables pane.
  3. Click Add variable.
    The Create Variable dialog displays.
  4. Configure the following fields in the Create Variable dialog:

    Field Description
    Name The name of the robotic task variable. Only letters, numbers, and underscores are accepted.
    Type The data type of the robotic task variable. Robotic task variables can be primitive data types, legacy instructions types, or custom data types (CDTs). The Credential type is used to reserve credentials for use in robotic subtasks.

    Note: The following system types cannot be selected for a robotic task variable type: Encrypted Text, Time, complex system data types, and hidden CDTs. See the Data Types page for a complete list of system data types.
    Array (multiple value) Lets the process variable accept an array of values. You cannot enter an initial value if this checkbox is selected. If your variable is a parameter and you select this checkbox, you can only pass one value when executing the robotic task from the console. To pass multiple list values in your input parameter, use the Execute Robotic Task Smart Service.
    Initial value The default value of a robotic task variable. Note that you cannot provide an initial value if you select the Array checkbox, if your variable is type CDT, or if your variable is type Date or Date and Time and marked as a parameter.
    Parameter? Allows variables to pass values to the robotic task before its execution. If selected, the variable will be used as an input field for the robotic task's execution. Input fields ask a user to provide data before a robotic task is executed.
    Required? Requires that a parameterized variable has a value before the robotic task is executed from the Execute robotic task page in the Appian RPA console.
  5. Click CREATE.

To edit a robotic task variable:

  1. Go to the Task tab of the robotic task configuration page.
  2. Find the Variables pane.
  3. Click a variable name.
  4. Make your changes to the variable fields described above.
  5. Click OK.

To delete a robotic task variable:

  1. Go to the Task tab of the robotic task configuration page.
  2. Find the Variables pane.
  3. Click a variable name.
  4. Click DELETE.
Open in Github Built: Wed, Aug 16, 2023 (04:37:39 PM)

On This Page