> 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/samples/sample-projects/integration-and-automation/conditional-actions-execution.md).

# Conditional Actions Execution

Conditional Actions Execution sample project demonstrates how to use the PerformActions activity in the Business Rules module to execute a series of actions.

The workflow activities and other modules used in this sample project are available in the following appRules Platform products:

<table><thead><tr><th width="375"> Platform Product</th><th data-type="checkbox">Availability</th></tr></thead><tbody><tr><td>appRules Data Migration Engine</td><td>false</td></tr><tr><td>appRules Integration &#x26; Automation Engine</td><td>true</td></tr><tr><td>appRules Enterprise 360</td><td>true</td></tr></tbody></table>

##

The action executions can be based on the results of executed conditions.

**Points of Interest:**

1. In row 1, the selected  condition is executed.  if the result is True, Action Default/True action is executed.  If the result is False, the Action False action is executed.
2. In row 4, since no condition is specified, the action specified as the Default action is executed.
3. You can use the Option button to select the execution option from a list of available 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/samples/sample-projects/integration-and-automation/conditional-actions-execution.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.