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
| Element | Status | Note |
|---|---|---|
| User task | Executed | |
| Manual task | Executed | |
| Undefined task | Executed | |
| Service task | Executed | with Wait for Jira Automation (a rule does the work); without it the task is passed |
| Script task | Executed | with Wait for Jira Automation; the script itself never runs on the server |
| Business rule task | Executed | with Wait for Jira Automation |
| Send task | Executed | with Wait for Jira Automation |
| Receive task | Executed | a comment with @FlowerBPM, Jira Automation or the REST endpoint (Data Center) sends the message |
Sub-processes
| Element | Status | Note |
|---|---|---|
| Embedded sub-process | Executed | |
| Call activity | Executed | |
| Event sub-process | Executed | conditional, 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 |
| Transaction | Not executed | runs like an embedded sub-process |
| Ad-hoc sub-process | Not executed | runs like an embedded sub-process |
Markers
| Element | Status | Note |
|---|---|---|
| Multi-instance, parallel | Not executed | the task runs once |
| Multi-instance, sequential | Not executed | the task runs once |
| Loop | Executed with a limit | on tasks with a loop condition; on sub-processes and call activities it runs once |
Gateways
| Element | Status | Note |
|---|---|---|
| Exclusive gateway | Executed | |
| Parallel gateway | Executed | |
| Inclusive gateway | Executed | |
| Event-based gateway | Executed | the first event behind it takes the path, the others are discarded (timer, conditional event, message, signal, receive task) |
| Complex gateway | Not executed | runs like an inclusive gateway |
Start events
| Element | Status | Note |
|---|---|---|
| None start | Executed | |
| Message start | Executed | |
| Timer start | Executed | |
| Signal start | Executed | |
| Conditional start | Executed |
Intermediate catch events
| Element | Status | Note |
|---|---|---|
| Message catch | Executed | |
| Timer catch | Executed | |
| Signal catch | Executed | every waiting process instance gets the signal (the ones a person can edit, when a person sends it) |
| Conditional catch | Executed | |
| Link (catch and throw) | Executed |
Intermediate throw events
| Element | Status | Note |
|---|---|---|
| None throw | Executed | triggers a Jira Automation rule or a webhook |
| Message throw | Executed | Jira Automation or a web service; to another pool of the model through a message flow |
| Signal throw | Executed | reaches every process instance that waits for the signal; also triggers a Jira Automation rule or a webhook |
| Escalation throw | Executed with a limit | triggers 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 throw | Not executed | triggers the rule like a none throw event, no compensation |
Boundary events
| Element | Status | Note |
|---|---|---|
| Timer boundary, interrupting | Executed | |
| Timer boundary, non-interrupting | Executed | |
| Message boundary | Executed | |
| Error boundary | Executed | a work item resolved in the status of the error, an error end event inside |
| Escalation boundary | Executed | a work item moved into the status of the escalation, an escalation throw or end event inside |
| Signal boundary | Executed | |
| Conditional boundary | Executed | |
| Compensation boundary | Not executed | never fires |
| Cancel boundary | Not executed | never fires |
End events
| Element | Status | Note |
|---|---|---|
| None end | Executed | |
| Message end | Executed | triggers a Jira Automation rule or a webhook, to another pool through a message flow |
| Error end | Executed | |
| Escalation end | Executed | |
| Signal end | Executed | reaches every process instance that waits for the signal; also triggers a Jira Automation rule or a webhook |
| Terminate end | Executed | |
| Compensation end | Not executed | ends its flow like a none end event |
| Cancel end | Not executed | ends its flow like a none end event |
Participants
| Element | Status | Note |
|---|---|---|
| Lanes assign tasks at run time | Executed | |
| Several pools with message flows | Executed |
Last updated on