Skip to main content

BPMN Editor

Design, connect, and configure the nodes that make up your workflow.

The BPMN Editor is the visual canvas where you build your Process. You drag elements onto the canvas, connect them with Sequence Flows, and configure each node's data to define your workflow's logic. The editor uses a simplified subset of the BPMN specification tailored to EW-FLOW's workflow patterns.

How it works​

You place elements from the left-hand palette onto the canvas and connect them by dragging from one element's connection point to another. Each connection creates a Sequence Flow that defines the order of execution.

When you drag a Task onto the canvas, it starts as a generic Task. Using the right-click replace menu you can convert it to any Task type provided by the installed Modules (e.g., InputTask, OutputTask, SwitchTask). The Task's type and data properties are set via this menu and the configuration side panel.

The visual diagram maps directly to the deployed Process. When you click Deploy, the engine reads the diagram and its configured data to execute your workflow.

Channels and Task resolution​

Every Session runs on a Channel (e.g., Chat, AculabVoice, SlackChannel). When the Token reaches a Task node, the engine resolves the implementation in two steps:

  1. Look for a channel-specific handler matching the Task type + Channel.
  2. If none exists, fall back to a generic handler for the Task type.

This is why I/O Tasks like Input and Output behave differently on Chat vs. Voice — each Module registers separate implementations per Channel. Logic Tasks like Switch or StringNormalization are registered without a Channel and run the same way everywhere.

info

You do not need to configure Channels manually. The Channel is determined automatically by how the Session is started (chat widget, phone call, Slack message, etc.).

Available elements​

EW-FLOW uses a simplified subset of the BPMN specification. The editor palette and replace menus have been customized to show only the elements relevant to EW-FLOW workflows.

Start Event​

Marks where the workflow begins. Every Process must have exactly one.

  • Palette — available via the circle icon.
  • Replace menu — can only convert to End Event.
  • Configuration — none. The start is triggered by the Channel.

End Event​

Marks where the workflow terminates and the Session ends.

  • Palette — available via the bold circle icon.
  • Replace menu — can only convert to Start Event.
  • Configuration — none.

Task​

The core building block. A generic Task is placed from the palette, then converted to a specific Module Task type via the replace menu.

  • Palette — available via the rounded rectangle icon.
  • Replace menu — shows "Convert to ..." entries for every Task type provided by the Modules installed in the current Process.
  • Configuration — click a Task to open its data panel on the right. Each Task type has its own set of properties (defined by the Module).
  • Custom rendering — Tasks display their name at the center and their type label at the bottom-right corner.

Exclusive Gateway​

Routes the Token down one of multiple outgoing paths based on the output of the previous Task.

  • Palette — available via the diamond icon.
  • Replace menu — no other gateway types are available; only Exclusive.
  • Configuration — each outgoing Sequence Flow should be labeled to match the possible outputs of the preceding Task.

Intermediate Catch Event (Message)​

Pauses the Token until an external message is received.

  • Replace menu — can convert between Message Catch, Message Throw, Start Event, and End Event only.

Intermediate Throw Event (Message)​

Sends a message and continues execution.

  • Replace menu — same restrictions as Intermediate Catch Event.

Sequence Flow​

Connects two elements. Drawn by dragging from one element's connection point to another.

  • Labeled flows — on Exclusive Gateways, each outgoing flow should have a label matching a Task output value.

Elements NOT available​

info

The following standard BPMN elements have been intentionally removed from EW-FLOW to keep the editor focused on supported workflow patterns:

  • Sub Process — collapsed, expanded, transaction, ad-hoc
  • Parallel Gateway, Inclusive Gateway, Complex Gateway, Event-Based Gateway
  • Typed Tasks — Service Task, User Task, Manual Task, Business Rule Task, Send Task, Receive Task (EW-FLOW uses generic Tasks with Module types instead)
  • Participant / Pool creation from the palette
  • Group, Data Object, Data Store
  • Loop and multi-instance markers
  • Call Activity

Toolbar and controls​

  • Save — creates a new version of the Process without deploying.
  • Deploy — publishes the current version to the selected Environment.
  • Chat — opens the test chat panel to interact with the deployed Process.

Pools​

A Pool is a BPMN container that groups a set of nodes within the Process. Pools define execution scope — Tasks inside different Pools can represent separate participants or logical boundaries in your workflow.

warning

Pool creation is not available from the palette. Pools are defined in the Process XML and managed through the platform.

Best practices​

  1. Name every Task — descriptive names make the diagram self-documenting and help collaborators understand the workflow at a glance.
  2. Label gateway flows — always label the outgoing Sequence Flows from an Exclusive Gateway so it is clear which path corresponds to which output.
  3. Keep workflows linear where possible — deeply branched workflows are harder to debug. Use Exclusive Gateways only when routing logic is genuinely needed.
  • Elements — detailed reference for every available BPMN element.
  • Task Configuration — how to configure Task data in the side panel.
  • Marketplace — install Modules to unlock additional Task types.