Process Task

Process Task
A ProcessTask can be used in the Case to call a Business Process (see
— CMMN 1.1 Standard,, Process Task

In Flowable, Process Tasks are used to create new process instances. As soon as the task is activated, a new process instance is created. It is possible to create Sub cases as well as completely independent cases.

Case tasks are completed once the newly created case is completed unless the Blocking attribute is set to false.


Group Attribute Description



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.


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.


The description attribute additionally adds a description to the component.


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



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.

Fallback to default tenant

Indicates the case is created with the default tenant if it is not available on the current tenant. This is only relevant if the application is running in a multi-tenant setup.


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.


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.

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.


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 Process Tasks, blocking indicates that the created process instance must be completed to start the plan item’s transition to the state COMPLETE.

Process reference

The process model reference referring to the BPMN process that is to start as this Process Task moves to state ACTIVE.

Process instance name

An optional run-time expression for the name of the newly started process instance. If left empty, defaults to the value of the 'Name' attribute.

* Sub case: the started Case is a child of the current Case. * Root case: the started Case is an independent top-level Case.


An optional input parameter map. Allows to pass variables to the created process instance.


An optional output parameter map. Allows to store variables of the process instance back to the parent case when the process instance completes.

Process ID

An optional variable that holds the ID of the created process instance.


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.


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.


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.