Introduction

Introduction to Human Tasks

Human Task is a feature in Robot Runner and Studio that enables semi - attended automation. The term 'semi - attended' means as in an unattended bot, user is not required to be present when the bot is running, instead the user is free to choose their time to do their part in the automation. Human Task workflows usually have three stages which may include two robots.

1. Running a bot which generates the data, creates the Human Task, and assigns the Task to one or more users.

2. Validating the task by the user to whom the task is assigned.

3. Running the second bot which uses the validated task to complete the workflow.

A task is created and assigned to a user using Create Task activity. This the only activity from Human Task category required in the first bot if the above design is followed.

Then in the second bot tasks are retrieved using Get Tasks activity. The output of the Get Tasks activity is a list of Human Tasks. Other Human Task activites can be used to update the tasks retrieved by Get Tasks activity.

Task Name and Task Group Name

A human task has a Task Group Name property which usually identifies the purpose of the task. The Task Name identifies the task in the task group. Generally it is assumed that all the Tasks within a Task Group has the same data structure. Which means all tasks have the same number of dependencies, every similar dependency has the same number of fields. Usually all the tasks created by a single Robot has the same Task Group Name.

Task Status

There are several task statuses representing different states of the Task. The status of a task is not determined by the application instead it is set by the user.

• Assigned - the task is assigned to one or more users and yet to be validated.

• Partially Done - the task is partially validated.

• Done - the task is fully validated.

• Verified - the task is validated and verified.

• Cancelled - the task is cancelled.

• On Hold - the task is put on hold.

• Pending, Ready - used internally

Task Dependency

A Human Task contains one or more dependencies. The dependencies in a task should hold related data. The dependency contains the actual data of the Task. In case of a validation task each dependency contains the document and the data extracted using that document. For a validation task the data of the dependency is an Extraction Result object.

See HumanTask for a summary of properties available in Human Task.

Creating a Human Task

A human task is created using the Create Task activity. To create a document validation task Extraction Result from one or more document extraction workflows are given as input. To create a Task using a single Extraction Result, the Extraction Result is given in the Extraction Data property on the Configure Task Data Window.

To create a task using multiple Extraction Results a list of Extraction Results must be created and given in the Extraction Data property on the Configure Task Data Window. The list of Extraction Results can be created using Create List and Add to list activites.

Validating a Human Task

Human Task is validated using the Validation Task Window.

See Validation Task Window for More Details