Skip to Content
Flower 3.7.1 is released 🎉 See what's new
Developer Reference· 3 min read· Updated November 2026

BPMN Element Catalog

Next releaseThe catalog already shows the next release of Flower BPM: 43 executed, 2 with a limit, 10 not executed.

The catalog lists 55 elements of BPMN 2.0 in ten groups. It is the same catalog that the BPM software comparison uses for every engine. Each element has one status:

  • Executed: the engine runs the element as BPMN describes it.
  • Executed with a limit: the engine runs it; the note names the limit.
  • Not executed: you can draw the element; the note says what happens instead, for example that the process passes it.

For the explanation of each element and how to model it, see the BPMN reference and BPMN Coverage.

Generated from bit.flower master by util/generate-specs.mjs. Do not edit this section by hand.

55 elements in 10 groups: 43 executed, 2 executed with a limit, 10 not executed.

Tasks

ElementStatusNote
User taskExecuted
Manual taskExecuted
Undefined taskExecuted
Service taskExecutedwith Wait for Jira Automation (a rule does the work); without it the task is passed
Script taskExecutedwith Wait for Jira Automation; the script itself never runs on the server
Business rule taskExecutedwith Wait for Jira Automation
Send taskExecutedwith Wait for Jira Automation
Receive taskExecuteda comment with @FlowerBPM, Jira Automation or the REST endpoint (Data Center) sends the message

Sub-processes

ElementStatusNote
Embedded sub-processExecuted
Call activityExecuted
Event sub-processExecutedconditional, timer, error, message, signal and escalation start events (an escalation start reacts to escalation throw and end events; the status of a work item escalates the boundary event of its task); in a process with an event start event that must be its only start event
TransactionNot executedruns like an embedded sub-process
Ad-hoc sub-processNot executedruns like an embedded sub-process

Markers

ElementStatusNote
Multi-instance, parallelNot executedthe task runs once
Multi-instance, sequentialNot executedthe task runs once
LoopExecuted with a limiton tasks with a loop condition; on sub-processes and call activities it runs once

Gateways

ElementStatusNote
Exclusive gatewayExecuted
Parallel gatewayExecuted
Inclusive gatewayExecuted
Event-based gatewayExecutedthe first event behind it takes the path, the others are discarded (timer, conditional event, message, signal, receive task)
Complex gatewayNot executedruns like an inclusive gateway

Start events

ElementStatusNote
None startExecuted
Message startExecuted
Timer startExecuted
Signal startExecuted
Conditional startExecuted

Intermediate catch events

ElementStatusNote
Message catchExecuted
Timer catchExecuted
Signal catchExecutedevery waiting process instance gets the signal (the ones a person can edit, when a person sends it)
Conditional catchExecuted
Link (catch and throw)Executed

Intermediate throw events

ElementStatusNote
None throwExecutedtriggers a Jira Automation rule or a webhook
Message throwExecutedJira Automation or a web service; to another pool of the model through a message flow
Signal throwExecutedreaches every process instance that waits for the signal; also triggers a Jira Automation rule or a webhook
Escalation throwExecuted with a limittriggers a Jira Automation rule or a webhook; reaches the escalation boundary event of an embedded sub-process around it, not of a call activity
Compensation throwNot executedtriggers the rule like a none throw event, no compensation

Boundary events

ElementStatusNote
Timer boundary, interruptingExecuted
Timer boundary, non-interruptingExecuted
Message boundaryExecuted
Error boundaryExecuteda work item resolved in the status of the error, an error end event inside
Escalation boundaryExecuteda work item moved into the status of the escalation, an escalation throw or end event inside
Signal boundaryExecuted
Conditional boundaryExecuted
Compensation boundaryNot executednever fires
Cancel boundaryNot executednever fires

End events

ElementStatusNote
None endExecuted
Message endExecutedtriggers a Jira Automation rule or a webhook, to another pool through a message flow
Error endExecuted
Escalation endExecuted
Signal endExecutedreaches every process instance that waits for the signal; also triggers a Jira Automation rule or a webhook
Terminate endExecuted
Compensation endNot executedends its flow like a none end event
Cancel endNot executedends its flow like a none end event

Participants

ElementStatusNote
Lanes assign tasks at run timeExecuted
Several pools with message flowsExecuted
Last updated on