You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The table below lists every BPMN 2.0 element the engine recognises, grouped
by category.
Each of these Elements has full Runtime support.
Activities
Element
Notes
Task (Untyped)
Pass-through
User Task
Defines User Forms, Actions and Assignees. Waits for User Input
Manual Task
Either pass-through, or optional requires confirmation to wait for manual user continuation
Service Task
Plugin-driven Service dispatch; built-in HTTP default handler; always asynchronous
Script Task
Inline FEEL evaluation or plugin dispatch. Always synchronous
Business Rule Task
Either simple FEEL Expression, or full DMN execution
Send Task
Publishes messages for 1:1 and deterministic 1:n communication
Receive Task
Receives messages, with optional process-level correlation
Call Activity
Executes a target process and waits for the result
Sub Process (Embedded)
Inline-Subprocess. Semantically similar to Call Activity, but restricted to one untyped Start Event. Re-uses the parent's lanes.
Multi-Instance
Includes Standard Loop, Sequential and Parallel MI
Subprocesses
Element
Notes
Event Subprocess
Interrupting + Non-Interrupting, triggered by a single typed Start Event
Transaction
All or nothing style Subprocess. Always succeeds or fails as a whole. Can use Cancel Events for premature cancelling and rolling back the subprocess and triggering compensation.
Ad Hoc Subprocess
An unstructured Activity "Menu", where users can pick the tasks to execute.
Gateways
Element
Notes
Exclusive Gateway
Split evaluates FEEL conditions with optional default path, Join is pass-through
Event-Based Gateway
First Catch Event to trigger wins, all others get interrupted.
Parallel Gateway
Split activates all outgoing paths, Join waits for ALL incoming tokens before continuing
Inclusive Gateway
Split activates all outgoing paths with a matching condition; Join waits for all incoming paths, with dead-path awareness.
Complex Gateway
Like Inclusive Gateways, but Splits disallow unconditional flows; Joins fire once, when condition is fulfilled and kills all remaining incoming paths.
Start Events
Element
Notes
Untyped
Normal Entry Point for a BPMN Process Instance
Timer
Automated Process Start via Cyclic, Date or Duration Timers
Message
Automated Process Start, when a Message is received. Correlation-aware; only triggers if no Message Catch Event in the same process listens for the same message with the same correlation.
Signal
Automated Process Start, when a Signal is received
Start Events - Event Subprocess only
Element
Notes
Conditional
Triggers when a FEEL condition is met.
Error
Triggers when an Error is caught.
Escalation
Triggers when an Escalation is caught.
Compensation
Triggers when a Compensation is caught.
Note: Event Subprocesses can use all Typed Start Events, but not The Untyped Start Event. The exact opposite of Embedded Subprocesses.
End Events
Element
Notes
Untyped
Finishes a single process path normally
Terminate
Terminates all remaining parallel Paths
Message
Publishes message and finishes the process path
Signal
Publishes signal and finishes the process path
Error
Terminates all remaining paths and throws an Error. The error propagates to the parent process and can be caught by an Error Boundary Event.
Escalation
Finishes a single process path and triggers an Escalation. The escalation propagates to the parent process and can be caught by an Escalation Boundary Event.
Compensation
Triggers compensation for completed activities in the current scope, then finishes the PI with Compensated state
Cancel
Transaction only. Cancels a Transactional Subprocess.
Intermediate Catch Events
Element
Notes
Untyped
Pass-through
Link
Landing pad for Link Throw with the same name
Timer
Duration and Date Timers, FEEL Expression Support
Message
Receives messages, with optional process-level correlation
Signal
Receives signal broadcasts from any source
Conditional
FEEL-based condition
Intermediate Throw Events
Element
Notes
Link
Resolves matching Link Catch by name within the same process
Message
Publishes messages for 1:1 and deterministic 1:n communication
Signal
Publishes signals for non-deterministic broadcasts
Escalation
Propagates escalation to the parent without terminating the current process; PI continues normally after the throw
Compensation
Triggers compensation on a specific finished activity, or ALL finished activities. Waits for handlers to complete, then continues normally.
Boundary Events
Element
Notes
Error
Matches by error code and/or message; alternative catch-all mode
Timer
Interrupting and Non-Interrupting; Cyclic, Date and Duration Timer Support
Message
Interrupting + non-interrupting
Signal
Interrupting + non-interrupting
Conditional
Interrupting + non-interrupting; FEEL condition, fires only once
Escalation
Interrupting + non-interrupting; For Call Activity and Embedded Subprocess only
Compensation
Passive marker; registers the host activity for compensation upon completion
Cancel
Catches Cancellations from a Cancel End Event. Transaction Subprocesses only
Data & Flows
Element
Notes
Sequence Flow
Connects 2 Flow Nodes
Conditional Flow
FEEL-based condition, used by forking Exclusive- and Inclusive Gateways
Data Associations
Input or Output Variants. Links Flow Nodes to a Data Object and vice versa
Data Object
DOA-driven writes, value contracts, FEEL reads, full write history for audit trail
Data Object Reference
Visual Data Object representation
Association
Links compensation boundary events to their handler activities
DMN 1.5 Support
The engine includes a full DMN 1.5 Conformance Level 3 (CL3) decision
engine in the BfwEngine.DMN subsystem. DMN models are deployed independently
or alongside BPMN diagrams and evaluated via Business Rule Tasks or the
REST API.
Decision Elements
Element
Notes
Decision
DRG-aware evaluation; bfw:decisionElementId selects root in multi-decision models
Input Data
Typed inputs declared in the model; bound from the BPMN token or REST payload
Business Knowledge Model
Encapsulated logic with formal parameters; invoked via knowledgeRequirement references
Decision Service
Evaluate a published subset of decisions; REST POST /decisions/:id/services/:sid/evaluate
Knowledge Source
Parsed and stored in the AST; no runtime behaviour (documentation-only per DMN spec)
Item Definition
Parsed; type coercion tracked in evaluation trace
Import
Cross-model imports with max-depth circuit breaker (:max_import_depth, default 10)
Expressions
Expression Type
Notes
Decision Table
All 7 hit policies; input/output entries are FEEL expressions
Literal Expression
Single FEEL expression; precompiled at deploy time
Context
Ordered key-value entries; entries can reference earlier siblings
Invocation
Calls a BKM's encapsulated logic with explicit parameter bindings
List
Ordered collection of sub-expressions
Relation
Tabular data (named columns, expression rows)
Function Definition
FEEL-kind supported; Java/PMML kinds parsed but rejected at evaluation
Conditional
if / then / else boxed expression
Filter
in / match list filtering
For
Iteration with iterator / in / return
Every
Universal quantifier (every x in list satisfies ...)
Some
Existential quantifier (some x in list satisfies ...)
Hit Policies
Policy
Notes
UNIQUE (U)
Exactly one rule matches; error on multiple matches
FIRST (F)
First matching rule in declaration order
PRIORITY (P)
Highest-priority matching rule by output values
ANY (A)
All matches must agree on the same output
COLLECT (C)
Aggregation: list, sum, min, max, count
RULE ORDER
All matching rules, in declaration order
OUTPUT ORDER
All matching rules, sorted by output priority
Diagram Interchange
Feature
Notes
DMNDI
Parsed and preserved in model AST; round-trips through deploy