> For the complete documentation index, see [llms.txt](https://interfacing.gitbook.io/interfacing-help-files/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://interfacing.gitbook.io/interfacing-help-files/interfacing-help-files-fr/analystes-de-processus/business-process-management/creating-and-editing-process-diagrams/mapping-a-process/editing-bpmn-properties-for-objects-and-flows/gateways-and-flows.md). # Gateways & Flows Configure properties to define gateway behavior and flow rules, controlling branching, merging, synchronization, and sequencing. A **gateway** controls the movement of a process, determining which path(s) are taken and how multiple paths are joined or synchronized. A **flow** connects process elements, defining the sequence of execution or the type of interaction between them. Both gateways and flows have **types** that define their behavior. *** ## Gateway Types Gateways direct process flow through branching, merging, or synchronization.

	What It Is	What It Looks Like
None	A gateway with no specific symbol or defined behavior; serves as a generic decision or merge point.
Exclusive	An exclusive gateway routes the flow to only one outgoing path based on conditions, allowing only a single path to be taken.
Inclusive	An inclusive gateway routes the flow to one or more paths simultaneously depending on the specified conditions. Multiple paths may be taken.
Parallel	A parallel gateway splits or joins multiple paths that execute concurrently, without evaluating any conditions.
Complex	A complex gateway handles advanced synchronization and branching scenarios that cannot be modeled by other gateway types.
Exclusive — Event Based	An exclusive event-based gateway routes the flow based on events, waiting for one event among many to occur before proceeding.
Exclusive — Event Based — Start	An exclusive event-based start gateway starts a process flow by waiting for one of several possible events to trigger continuation.
Parallel — Event Based — Start	A parallel event-based start gateway triggers multiple events simultaneously, enabling concurrent flows based on event occurrences.

*** ## Flow Types Flows show how activities, events, and gateways are connected.

	What It Is	What It Looks Like
Sequence Flow	A sequence flow shows the order in which activities and events are executed within the process.
Default Flow	A default flow acts as a fallback path taken when none of the conditions on other outgoing sequence flows are met.
Conditional Flow	A conditional flow routes the process based on a specified condition, proceeding only if the condition evaluates to true.
Message Flow	A message flow represents communication between different participants or processes, typically indicating the exchange of messages.
Association	An association connects artifacts—such as data objects or text annotations—to BPMN elements to provide clarification or additional information.
Directed Association	A directed association is a one-way link between BPMN elements that indicates the direction of the relationship.
Bidirected Association	A bidirected association indicates a two-way connection between an artifact and a BPMN element.
Conversation	A conversation flow represents interactions or exchanges between two or more participants in a collaborative process.

{% hint style="warning" %} Flows connecting an artifact or data store automatically use **directed association**, which cannot be changed. {% endhint %} --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://interfacing.gitbook.io/interfacing-help-files/interfacing-help-files-fr/analystes-de-processus/business-process-management/creating-and-editing-process-diagrams/mapping-a-process/editing-bpmn-properties-for-objects-and-flows/gateways-and-flows.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.