> For the complete documentation index, see [llms.txt](https://docs.appstrategy.com/apprules-r-documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.appstrategy.com/apprules-r-documentation/platform-products/apprules-integration-and-automation-engine/business-rules/evaluating-conditions.md).

# Evaluating Conditions

## Evaluating Conditions

The following activities are used for evaluating conditions:

EvaluateCondition

EvaluateConditions

### EvaluateCondition Activity

The EvaluateCondition activity is used to evaluate a condition in appRules.&#x20;

To configure a EvaluateCondition activity, drag the EvaluateCondition activity from the Base module of the toolbox on to the designer.  Select the Condition or configure a new one.  Then save the workflow activity.

### EvaluateConditions Activity

The EvaluateConditions activity is used to evaluate a group of conditions. &#x20;

To configure the EvaluateConditions activity, drag the EvaluateConditions activity from the "Business Rules" module of the toolbox on to the designer.  The following modal will be displayed:

#### To configure the Conditions to be evaluated.

1. Click the "Evaluation Option" toolbar button to set the evaluation option for the Conditions to be included in the list.    &#x20;
2. Configure the Conditions by entering a unique description for each Condition, and clicking the configuration button to select or configure the Condition.  **Note:**  Right-Mouse-Click on any row to view a menu of additional options.

#### To configure the optional Actions to be performed if the Conditions evaluate to True

1. Click the "Evaluation Option" toolbar button to set the execution option for the Actions to be performed if the Conditions evaluate to True - (Then Actions Option) &#x20;
2. Configure the optional THEN Actions by entering a unique description for each Action, and clicking the configuration button to select or configure the Action.  These Actions will be performed only if the Conditions evaluate to True.  **Note:**  Right-Mouse-Click on any row to view a menu of additional options.

#### To configure the optional Actions to be performed if the Conditions evaluate to False

1. Click the "Evaluation Option" toolbar button to set the execution option for the Actions to be performed if the Conditions evaluate to False - (Else Actions Option)Configure the optional ELSE Actions by entering a unique description for each Action, and clicking the configuration button to select or configure the Action.  These Actions will be performed only if the Conditions evaluate to False.  **Note:**  Right-Mouse-Click on any row to view a menu of additional options.


---

# 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://docs.appstrategy.com/apprules-r-documentation/platform-products/apprules-integration-and-automation-engine/business-rules/evaluating-conditions.md?ask=<question>&goal=<user_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.
