Human Task

Human Task
A HumanTask is a Task that is performed by a Case worker.
— CMMN 1.1 Standard, 5.4.10.4, Human Task

In Flowable, Human Tasks are the primary way to interact with humans within a case. Once a Human Task is activated, a user is required to fill in a form of some sort.

Through forms, it is possible to create and update variables which can be used in other tasks or can be used to control the flow of a process.

Each task can be assigned to one or more people as well as shared with any number of groups. In addition, a task can optionally have a due date.

Attributes

Group Attribute Description

General

ID

A unique ID for the element. The ID is used to refer to a model element from outside of the diagram (for example, from a CMMN Action button in a form or when referring to a model element, such as plan item ID, in a CMMN REST call). For convenience, this ID can be edited.

Name

The name of the element. This is the name displayed in the diagram. If no run-time name is specified, this name is also used in the running case.

Description

The description attribute additionally adds a description to the component.

Security policy

The security policy associated with this element.

Documentation

Documentation intended to explain concepts of its use for future reference.

Assignment

Owner

The Owner attribute describes who owns the task. The owner can delegate a task to another user who then becomes the assignee. The assignee can then resolve the task which reassigns it to the owner who then decides whether or not the task is completed.

Assignee

Defines the assignee of a task. The assignee is the person who is responsible for the completion of a task. By default, the assignee is set to $INITIATOR which is a special variable that is set to the user who started the process. It is possible to set the assignee directly or through an expression. In both cases, the expected value is the User ID of the assignee.

Candidate users

Defines a list of users that can become assignee by claiming the task. It is possible to set the candidate users directly or through an expression. In both cases, a list of user IDs is expected.

Candidate groups

Defines one or more groups that can become assignee by claiming the task. You can either directly select a group or use an expression. It is possible to set the candidate groups directly or through an expression. In both cases, a list of group IDs is expected.

Participant users

The selected users to add as participant identity links to the task.

Participant groups

The selected groups to add as participant identity links to the task.

Watcher users

The selected users to add as watcher identity links to the task.

Watcher groups

The selected groups to add as watcher identity links to the task.

Details

Form reference

The form associated with the User Task. Once a user opens the task, he or she is presented with the referenced form. It is possible to create a new form, reference an existing one or delete the current reference.

Validate form fields (server-side)

If the form is submitted and validate form fields expression evaluates to true, form fields are validated on the back send according to the form model restrictions.

Expose human task as action to object

Allows you to expose the activation action to objects other than the case, such as a user or conversation.

Expose human task as an action message

Allows you to expose the human task as a message in a conversation.

Asynchronous

When enabled, the behavior of the plan item is executed as an asynchronous job. This happens when the plan item transitions to the ACTIVE state. During the execution of the behavior, the plan item is set to an intermediate ASYNC_ACTIVE state.

Required

Select this option to mark the element as required (exclamation mark decorator).

Required plan items must either be in the state COMPLETED, TERMINATED or DISABLED for their parent stage to complete.

Repetition counter variable

Name of the repetition counter variable.

Repetition

Select this option to mark the element as repeatable (number sign decorator)

By default, only one instance of a plan item may be created at runtime. Repeatable plan items do not have that limitation.

The combination of this property, Manual activation and no entry sentry has a special meaning called Automatic repetition: As a previous instance of the plan item completes, a new instance is automatically created and set into state Enabled.

Blocking

Blocking is the default behavior where a task plan item remains active until it transitions from the ACTIVE state to another one as work on the case progresses. By marking a plan item as non-blocking, the task is immediately moved to the next state instead.

For Human Tasks, blocking indicates that the created task must be completed to start the plan item’s transition to the state COMPLETE.

Completion neutral

Completion neutral influences the plan item’s parent stage completes.

Plan items in the state AVAILABLE may prevent the parent stage (or case) from automatically completing. By checking this property, the plan item behaves neutral with respect to the completion of the parent container.

Priority

An integer number denoting the priority of the task.

Due date

The due date of the task. There are three different modes to set the due date:

  • Relative: Add or subtract a number of days, months or years to the current date.

  • Absolute: Set an absolute date.

  • Expressions: Use an expression to dynamically calculate a date.

Task listeners

Sets Task listeners for this task. This lets you react to the following events:

  • Create: occurs when the task has been created and all task properties are set.

  • Assignment: Occurs when the task is assigned to somebody. Please note that the Assignment event is fired before the Create event.

  • Complete: Occurs when the task is completed and just before the task is deleted from the runtime data.

  • Delete: Occurs just before the task is going to be deleted or completed.

Folder path for uploaded content items

The folder path where uploaded content items for this case are uploaded.

Activation

Manual activation

Select this option to mark the element to have Manual activation (right arrow 'play' decorator).

Plan items with Manual activation move from state AVAILABLE to state ENABLED once they trigger. A plan item in state ENABLED exposes an action button that allows the user to manually start the plan item.

Expose as action to object

Allows you to expose the activation action to objects other than the case, such as a user or conversation.

Expose as an action message

Allows you to expose the activation action as a message to a conversation.

More

Lifecycle listeners

Allows you to define lifecycle listeners for a plan item. Lifecycle listeners allow you to execute an expression, a delegate expression or a class when a plan item transitions from one state to another.

Visual

Font weight

The font weight of the element in the diagram.

Font size

The font size of the element in the diagram.

Font color

The font color of the element in the diagram.

Font style

The font style of the element in the diagram.

Background color

The background color of the element in the diagram.

Border color

The border color of the element in the diagram.