BPMN Elements Reference
A complete reference for every element you can place, connect, and configure in the EW-FLOW editor.
The BPMN Editor provides a curated set of elements drawn from the BPMN specification. Only the elements listed on this page are available — standard BPMN elements that do not apply to EW-FLOW workflows have been removed to keep the editor focused and easy to use.
Events
Events represent points in time during a workflow — when it starts, when it ends, and when it pauses for external input.
Start Event
| Property | Value |
|---|---|
| Icon | Thin circle |
| BPMN type | bpmn:StartEvent |
| Palette | Yes |
| Configurable | No |
The entry point of every Process. When a Session is triggered via a Channel, the Token is created at the Start Event and begins moving through the diagram. Every Process must have exactly one Start Event.
Replace menu: can only convert to End Event.
End Event
| Property | Value |
|---|---|
| Icon | Bold (thick border) circle |
| BPMN type | bpmn:EndEvent |
| Palette | Yes |
| Configurable | No |
The termination point of the workflow. When the Token reaches an End Event, the Session is marked as completed and no further Tasks execute.
Replace menu: can only convert to Start Event.
Intermediate Catch Event (Message)
| Property | Value |
|---|---|
| Icon | Double-bordered circle with envelope |
| BPMN type | bpmn:IntermediateCatchEvent |
| Palette | Yes (via intermediate event icon) |
| Configurable | Yes (via Module Task type) |
Pauses the Token and waits for an external message before continuing. In practice, the Standard Module's InputTask is mapped to this element — it waits for the end user to send a message on the active Channel.
Replace menu: can convert between Message Catch, Message Throw, Start Event, and End Event.
Intermediate Throw Event (Message)
| Property | Value |
|---|---|
| Icon | Double-bordered circle with filled envelope |
| BPMN type | bpmn:IntermediateThrowEvent |
| Palette | Yes (via intermediate event icon) |
| Configurable | Yes (via Module Task type) |
Sends a message and continues execution without waiting. In practice, the Standard Module's OutputTask is mapped to this element — it sends a message to the end user on the active Channel.
Replace menu: can convert between Message Throw, Message Catch, Start Event, and End Event.
Activities
Activities represent work performed during the workflow.
Task
| Property | Value |
|---|---|
| Icon | Rounded rectangle |
| BPMN type | bpmn:Task |
| Palette | Yes |
| Configurable | Yes |
The primary building block. When placed from the palette it is a generic Task with no behavior. Use the right-click replace menu to convert it to a specific Module Task type (e.g., LanguageTask, StringNormalizationTask, OpenAICreateThreadTask).
After conversion, the Task displays its name at the center and its type label at the bottom-right corner. Click the Task to open the configuration side panel and set its properties.
Replace menu: shows "Convert to ..." entries for every Task type registered by the Modules installed in the current Process.
Script Task
| Property | Value |
|---|---|
| Icon | Rounded rectangle with script marker |
| BPMN type | bpmn:ScriptTask |
| Palette | No (created via replace menu) |
| Configurable | Yes |
Used by the JavaScript Module to execute custom scripts. The JSTask is mapped to this element type.
Gateways
Gateways control branching and merging of Sequence Flows.
Exclusive Gateway
| Property | Value |
|---|---|
| Icon | Diamond with X marker |
| BPMN type | bpmn:ExclusiveGateway |
| Palette | Yes |
| Configurable | Yes (via SwitchTask from Standard Module) |
Routes the Token down exactly one of multiple outgoing paths. The Standard Module's SwitchTask is mapped to this element — it compares a Session variable against configured conditions and selects the matching output.
Each outgoing Sequence Flow should be labeled to match one of the SwitchTask's configured outputs.
Replace menu: no other gateway types are available. Parallel, Inclusive, Complex, and Event-Based Gateways have been removed.
Connections
Sequence Flow
Sequence Flows are the arrows that connect elements and define execution order. Draw one by dragging from an element's connection point to another element.
- On Exclusive Gateways, label each outgoing flow to match the output value that should trigger that path.
- Sequence Flows have no configurable properties beyond their label.
Removed elements
The following standard BPMN elements are not available in EW-FLOW:
| Category | Removed Elements |
|---|---|
| Sub Processes | Collapsed, Expanded, Transaction, Ad-Hoc Sub Process |
| Gateways | Parallel, Inclusive, Complex, Event-Based |
| Typed Tasks | Service Task, User Task, Manual Task, Business Rule Task, Send Task, Receive Task |
| Containers | Participant / Pool creation from the palette |
| Data | Group, Data Object, Data Store |
| Markers | Loop, Sequential Multi-Instance, Parallel Multi-Instance |
| Other | Call Activity |
EW-FLOW replaces typed BPMN Tasks with a generic Task + Module type system. Instead of a "Service Task" or "User Task," you place a generic Task and convert it to the specific Module Task you need.
Related pages
- BPMN Editor — editor overview, toolbar, and Pools.
- Task Configuration — how to configure Task properties in the side panel.