Skip to Content
Flower 3.7.1 is released 🎉 See what's new
DocsBPMN ReferenceBPMN Gateways
BPMN Reference· 8 min read· Updated November 2026

BPMN Gateways

Next releaseThis page already describes the next release of Flower BPM: the event-based gateway lets only the first event win, and a condition can be a choice of statuses and resolutions.

A BPMN gateway is the element that splits or joins the flow of a process. It is drawn as a diamond, and the marker inside the diamond tells you its type. A gateway does no work itself. It only decides which sequence flows the process takes next.

🛠️

Guide: Decide with Gateways shows how to write conditions on Jira fields, and Make Approval Steps builds an approval with them.

An exclusive gateway chooses one path, a parallel gateway starts all paths at the same time.

Exclusive, Parallel, and Inclusive Gateway Compared

Exclusive gateway (XOR)Parallel gateway (AND)Inclusive gateway (OR)
MarkerX, or an empty diamond+O
As a splitTakes exactly one pathTakes all pathsTakes every path whose condition is true
ConditionsYes, on the outgoing flowsNoYes, on the outgoing flows
As a joinPasses each incoming flow through at onceWaits for all incoming flowsWaits for the flows that were started
Typical useApproved or rejected? Amount above the limit?HR, IT, and facilities work at the same timeAny combination of optional steps

Which Gateway Do I Need?

  • Only one of several paths can run: use an exclusive gateway. Example: an approved request continues, a rejected request goes back.
  • All paths always run at the same time: use a parallel gateway. Example: the tasks before the first day of a new employee.
  • One or more paths run, depending on data: use an inclusive gateway. Example: a request needs a security review, a legal review, both, or none.
  • Join what you split with the same type. Paths that a parallel gateway started are joined by a parallel gateway. If an exclusive gateway joins them, every branch passes through on its own and the steps after the gateway run once per branch.

Supported Gateways

GatewayWhat it doesSupport in Flower
Exclusive (XOR)Chooses exactly one path, based on conditionsSupported
Parallel (AND)Starts all paths, and as a join waits for all of themSupported
Inclusive (OR)Starts every path whose condition is true, and as a join waits for the paths that were startedSupported
Event-basedWaits for the first of several eventsSupported: the first timer, conditional event, message, signal, or receive task behind it takes the path, the others are discarded
ComplexRoutes with custom rulesRuns like an inclusive gateway (the validator warns)

What Flower does with each element that it does not execute as in BPMN is listed in BPMN Coverage in Jira.

Exclusive Gateways

An exclusive gateway (or XOR gateway) lets you make a decision based on data, namely the data of your Jira work items.

An exclusive gateway: if totalPrice > 100 the parcel is shipped with transport insurance, else without

If an exclusive gateway has several outgoing sequence flows, all of them except one need a condition that defines when the flow is taken. One flow can have no condition. You mark it as the default flow.

When the process enters an exclusive gateway, Flower evaluates the conditions. The process takes the first sequence flow whose condition is fulfilled.

If no condition is fulfilled, the process takes the default flow. If the gateway has no default flow, the process does not go on: the process instance gets the error comment The gateway … found no outgoing flow whose condition is true, and it has no default flow, and Flower does not save the step. After you correct the data (or the model), resolve the work item again, and the gateway is evaluated again. Therefore, always define a default flow.

An exclusive gateway can also join several incoming flows to make the model easier to read. A joining exclusive gateway only passes tokens through. It does not wait for the other flows, unlike a parallel gateway.

Conditions

A condition says when a flow is taken. In BPMN it is an expression on the data of the process. In Flower this data is your Jira work items:

  • pi is the work item of the process instance.
  • model is the work item of the model (model.key, model.fields.summary), in every run.
  • par is the calling process instance in a sub-process.
  • cur is the work item whose change moved the process to the gateway, usually the work item of the activity before it. Exceptions (after a join, a timer, a condition, right after the start) are listed in Expressions.

The condition is written inside ${ } and is fulfilled when the expression returns true:

ExpressionWhat it checks
${cur.fields.status.name == 'Rejected'}The status of the last work item
${cur.fields.customfield_10113 >= 5000}A number field of the last work item
${pi.fields.summary == 'New Request'}The summary of the process instance

An expression is not code: Flower evaluates it with its own parser, and only the operators, methods, and functions listed in What an Expression Can Do work. A script condition (a condition with a script language, from older models) is never executed: it is always false, the process instance gets an error comment, and the validator warns. Change it to an expression.

Status or resolution without an expression: for the outcome of the task before the gateway, check its statuses or resolutions in the properties panel (group Condition) instead. The flow is taken when the work item of that task is in one of the checked statuses or has one of the checked resolutions; with a choice in both lists, both must fit. The expression counts only when nothing is checked. See Choose a Status or Resolution.

How to write expressions, combine them, read complex fields, use external data, and troubleshoot them is the subject of the guide Decide with Gateways.

Parallel Gateways

A parallel gateway (or AND gateway) splits the flow into concurrent paths.

Parallel gateways: when the order is ready, Ship Parcel and Process Payment run at the same time, the order is completed when both are done

When the process enters a parallel gateway with several outgoing sequence flows, all flows are taken. In Flower, the work items of all branches are created at the same time, and the people responsible work on them independently.

You can join the concurrent paths with a parallel gateway that has several incoming sequence flows. The process waits at this gateway until every incoming flow has arrived.

Inclusive Gateways

The inclusive gateway (or OR gateway) lets you make several decisions based on data. The process takes every flow whose condition is fulfilled, so more than one flow can run.

A process model to prepare lunch at lunchtime can use an inclusive gateway to decide which steps to take to prepare the different lunch components, e.g. cook pasta,stir-fry steak, prepare salad, or any combination of these.

If an inclusive gateway has several outgoing sequence flows, all of them need a condition. If it has only one outgoing sequence flow, it needs no condition.

You can mark one flow as the default flow. It should not have a condition, because it is only taken when no other condition is fulfilled.

When the process enters an inclusive gateway, Flower evaluates the conditions. The process takes all flows whose condition is fulfilled.

For example, the selected courses are pasta and salad:

An inclusive gateway has decided to take the steps to cook pasta and prepare salad, but not stir-fry steak.

For example, the selected courses are steak, pasta, and salad:

An inclusive gateway has decided to take the steps to cook pasta, stir-fry steak, and prepare salad.

If no condition is fulfilled, the process takes the default flow. Flower does not evaluate the default flow. If no condition is fulfilled and the gateway has no default flow, the process does not go on, with the same error comment as at the exclusive gateway. The validator warns about a missing default flow here as well.

For example, no courses are selected, so the default flow is taken:

An inclusive gateway has decided to take the step to prepare salad as the default because none of the conditions were fulfilled.

As a join, the inclusive gateway waits for exactly the paths that its split started, then the process continues once. The validator expects the join to have as many incoming flows as the split has outgoing flows.

Conditions

The conditions of an inclusive gateway work as described for the exclusive gateway: expressions inside ${ } that use the data of your Jira work items. The flow is taken when the expression returns true.

Event-Based Gateways

The event-based gateway waits for the events behind it, and the first of them takes its path: a timer or a conditional event when it fires, a message catch event or a receive task when its message arrives, a signal catch event when its signal comes. A message is sent by a comment, Jira Automation, or the REST API, see BPMN Message Events. A signal is sent the same ways or by a signal throw or end event of another process, see BPMN Signal Events.

As in BPMN, only the first event counts: when one event has taken its path, Flower discards the other events behind the gateway. A timer behind it does not fire any more, and a message or signal that arrives later does not reach them. A task directly behind the gateway (BPMN does not allow one there) becomes a work item at once, like behind a parallel gateway.

The validator does not warn about an event-based gateway. For a deadline on a task, a timer boundary event is often simpler, and for alternative outcomes of a task an exclusive gateway or a conditional boundary event.

Complex Gateways

A complex gateway runs like an inclusive gateway: every outgoing flow whose condition is true is taken, and its activation condition is not evaluated. The validator warns about it, and about a complex gateway without a default flow.

Frequently Asked Questions

What is a gateway in BPMN?

A gateway is a diamond-shaped element that splits the flow of a process into several paths or joins several paths into one. The marker in the diamond shows the type.

What is the difference between an exclusive and an inclusive gateway?

An exclusive gateway (XOR) takes exactly one outgoing path. An inclusive gateway (OR) takes every outgoing path whose condition is true, so several paths can run at the same time.

What is the difference between an exclusive and a parallel gateway?

An exclusive gateway decides between paths with conditions. A parallel gateway has no conditions: it always starts all outgoing paths, and as a join it waits for all incoming paths.

Does an exclusive gateway need a default flow?

BPMN does not require it, but you should always define one. Without a default flow the process cannot continue when no condition is fulfilled.

Can I split or merge without a gateway?

BPMN allows several flows to leave or enter an activity. A gateway makes the behavior explicit and the model easier to read, so use one. See 11 Common BPMN Modeling Mistakes.

Learn More

Last updated on