# Decision

Used to define multiple option paths and proceed to a particular path when the respective condition is satisfied. Allows the user to add multiple option paths with their own title and condition.

The option that satisfies the given condition will be executed. If all conditions are failed then the else option will be executed.

<figure><img src="/files/p3kZHQ3HlOtjic1viZOz" alt=""><figcaption></figcaption></figure>

### Options

For each option

* Title - Title of the option for better readability and understandability. Keep it short.
* Condition
  * Field - Selected from [Data Hub](/project-manager/workflows/flow-builder.md#data-hub)
  * Operator - to compare the field and value
  * Value - to which the field is compared

In a single option, multiple conditions can be configured with the joining operators `AND, OR`. The nested level is also allowed to provide precedence to the sub-condition.

**Example:** `{{1.name}}` is equal to `Alice` <mark style="color:orange;">AND</mark> (`{{1.city}}` is equal to `New York` <mark style="color:orange;">OR</mark> `{{1.zipcode}}` is equal to `10001`)

In the above example, the precedence is given to city and zip code. Nested is used to provide that precedence in Condition Builder.

There are no limitations on how many options can be added.&#x20;

### Use Cases:

Multiple options to execute different workflow paths based on the city of the customer.

**Option A:**&#x20;

Title: Customer from New York

Condition: `{{1.customer.city}}` is equal to `New York`&#x20;

<mark style="color:green;">This will be executed when the customer is from New York</mark>

**Option B:**&#x20;

Title: Customer from Los Angeles

Condition: `{{1.customer.city}}` is equal to `Los Angeles`&#x20;

<mark style="color:green;">This will be executed when the customer is from Los Angeles</mark>

**Else Option**

No condition is needed for the else option. <mark style="color:green;">This will be executed when the customer is neither from</mark> <mark style="color:green;"></mark><mark style="color:green;">`New York`</mark> <mark style="color:green;"></mark><mark style="color:green;">nor</mark> <mark style="color:green;"></mark><mark style="color:green;">`Los Angeles`</mark><mark style="color:green;">.</mark>


---

# 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.dckapintegrator.com/project-manager/workflows/actions/decision.md?ask=<question>
```

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.