# Inclusive Gateway The **Inclusive Gateway** is used to create **conditional process flows** where **one or more outgoing paths** can be followed based on condition evaluation. Unlike the **Exclusive Gateway**, which allows the process to follow only a single path, the Inclusive Gateway enables the process to continue through **all outgoing paths whose conditions evaluate to true**. Outgoing paths are represented as **arrow links (`→`)** that connect the Inclusive Gateway to subsequent activities or events. *** ### Purpose The **Inclusive Gateway** is designed for decision points where: * Multiple conditions may be true at the same time * More than one process path should be executed * Conditional branching is required, but parallel execution is optional and condition‑dependent This makes the Inclusive Gateway suitable for **flexible business logic**, where several actions may need to occur depending on evaluated conditions. *** ### Behavior of Inclusive Gateway When a process reaches an Inclusive Gateway: * All outgoing paths with conditions that evaluate to **true** are activated * One, multiple, or all outgoing paths may be executed * Paths with conditions evaluating to **false** are skipped If no conditions evaluate to true, the process will not proceed unless a default (otherwise) path is defined. *** ### Comparison with Exclusive Gateway Although similar in configuration, Inclusive and Exclusive Gateways differ in execution behavior: | Gateway Type | Execution Behavior | | --------------------- | ----------------------------------------------------- | | **Exclusive Gateway** | Only **one** path is taken (first matching condition) | | **Inclusive Gateway** | **All matching paths** are taken | This distinction is critical when designing decision logic. *** ### Configuration Properties The **Inclusive Gateway configuration properties are the same as those of the Exclusive Gateway**, including: * **General Tab** * Gateway name * Gateway ID * **Gateway Parameter (on outgoing links)** * Condition * Otherwise (default path) * Label Conditions are configured **on each outgoing link**, not directly on the gateway node. > For detailed property definitions and step‑by‑step configuration instructions, please refer to: > > **Exclusive Gateway Configuration Properties**\ > *** ### Condition Evaluation Conditions on Inclusive Gateway links are defined using the **Formula Editor**.\ Each outgoing path is evaluated independently, and all conditions returning **true** will be executed. Best practice: * Ensure conditions are clearly defined and non‑overlapping where necessary * Use meaningful labels for outgoing links * Always define an **Otherwise** path if a fallback is required *** ### Usage Guidelines * Use Inclusive Gateway when **multiple conditional paths may be required** * Do not use Inclusive Gateway if only one path should ever be executed * Avoid excessive complexity by clearly defining and documenting conditions * Use a matching Inclusive or Parallel Gateway to **synchronize** paths if needed * Test all condition combinations carefully during process validation *** ### Example Use Cases * Trigger approval plus notification when certain thresholds are met * Execute optional checks based on available data * Apply conditional business rules where more than one rule may apply *** ### Summary The **Inclusive Gateway** enables **multi‑path conditional execution** in ONEWEB Process Designer. Key points: * Executes all paths with true conditions * Allows one or multiple outgoing paths * Similar configuration to Exclusive Gateway * Uses Formula Editor for condition logic * Ideal for flexible, rule‑driven workflows Correct use of Inclusive Gateways allows you to model **complex, condition‑dependent business scenarios** while maintaining clarity and control over process execution. --- # Agent Instructions: 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: ``` GET https://docs.onewebstack.com/designer-reference/process-designer/process-designer-component/gateway/inclusive-gateway.md?ask= ``` The question should be specific, self-contained, and written in natural language. 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.