User Tasks

User tasks are tasks that should be completed by a user, by filling out a given process form.

User Task

User Task Properties

Form

Each user task must have a form assigned. The form should be defined in the process YAML file.

Assignee

A user task can be automatically assigned to:

  • A user

  • A group

  • An app role

  • An email address (guest user).

Because of this, the assignee dropdown will show: ` - The initiator variable - All app roles - All table fields of type user, group, or email.

If the task is assigned to a group or an app role, any user that belongs to that group or role can claim the task and then work on it.

A task can always be reassigned to another user, or to guest users, using their email address.

Save Assignee

When defining a user task, you can save the user that is assigned to the task as a variable or in a field. This is useful, for assigning the same user further tasks of the same case.

For example, in the following process, let’s say that task A is assigned to the recruiter role. John Doe and Jane Doe have that app role, thus, any of them can work on it.

Tasks A and B

You want to assign task B to the same user that worked on task A. You don’t know if it will be John, or Jane.

The solution is:

  • When defining task A, you enable Save Assignee option, and define that the assignee should be stored As variable. Let’s say caseOwner.

  • Then, you configure task B to be assigned to the value of the variable caseOwner.

If John works on task A, then task B is automatically assigned to John. Same for Jane.

Saving the assignee As Field is also useful for persisting the user that completed a specific task. For example, if you have an approvedBy field.

Due in

You can set the expected due date for the task. This information will be used to help users see which tasks are overdue, and also for analytics to determine if the task was completed on time or not.