> For the complete documentation index, see [llms.txt](https://developer.collibra.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://developer.collibra.com/workflows/designing-workflows/processes/shape-repository/inclusive-gateway.md). # Inclusive gateway Used to create diverging, parallel alternative paths within a process where one or more paths can be taken based on conditions. Conditions are evaluated on the outgoing sequence flows, not on the gateway itself. An inclusive gateway can act as a fork, a join, or both: * **Fork**: All outgoing sequence flows whose conditions evaluate to `true` are followed in parallel. A sequence flow without a condition is always followed. * **Join**: Execution waits until all active incoming paths have completed before the process continues. {% hint style="info" %} If no condition evaluates to `true` and no unconditioned sequence flow exists, the process gets stuck. To prevent this, add an unconditioned default flow or ensure at least one condition always evaluates to `true`. {% endhint %} ## General properties | Property | Description | | ------------- | ------------------------------------------------------------------------------------------------------------ | | Model ID | The unique identifier of the element within the process model. | | Name | The name of the element displayed in the diagram. | | Documentation | A description and any additional information about this element. | | Flow order | The order in which the outgoing flows will be evaluated and stored in the XML representation of the process. | ## Advanced properties | Property | Description | | ----------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | [Asynchronous](/workflows/designing-workflows/processes/process-execution.md#asynchronous-activities) |

Whether the activity starts as an asynchronous job, placing a transaction boundary before the activity:

| | Leave asynchronously |

Whether the activity leaves as an asynchronous job after it completes, placing a transaction boundary before the process advances to the next element:

| ## Visual properties | Property | Description | | ---------------- | --------------------------------------------------- | | Font size | The font size of the element in the diagram. | | Font weight | The font weight of the element in the diagram. | | Font style | The font style of the element in the diagram. | | Font color | The font color of the element in the diagram. | | Background color | The background color of the element in the diagram. | | Border color | The border color of the element in the diagram. | --- # 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 by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://developer.collibra.com/workflows/designing-workflows/processes/shape-repository/inclusive-gateway.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. 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.