> 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/business-rules-1.md).

# Executing Rule Sets

## Executing Rule Sets

The ExecuteRuleSet activity is used for defining, validating and executing Rule Sets in appRules.  Rule Set in appRules is a set of rules and the Actions to be performed when each rule evaluates to true or false.

#### Creating Rule Sets

To create a Rule Set, drag an ExecuteRuleSet activity from the "Business Rules" module of the toolbox on to the designer.  The following modal will be displayed:

Enter a Rule Name, then click on the button after the name to set the related condition.

For each rule, you can set action(s) if true or false.

To add new rules and actions, right click in the related area of the window to display the context menu:

#### Testing Rule Sets

To test your rule set, simply click the Run button from your IDE.  If the ViewExecutionResults property is set to True (checked), the result of the run in debug mode will be displayed.


---

# 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/business-rules-1.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.