> For the complete documentation index, see [llms.txt](https://docs.apica.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.apica.io/platform-docs/test-data-orchestrator-tdo/user-documentation/tdo-project-builder-user-guide/business-rules/business-rule-sets.md).

# Business Rule Sets

Business rules can be saved to Business Rule Sets. This lets you save rules that may be used again and reload them quickly.

To save a set of business rules as a business rule set, go to the business rules page. In the upper right corner of the rules section, there are two icons - the 'reload' icon on the left and a 'save' disc icon on the right. To save the rules currently displayed, click the 'save' icon.

<figure><img src="/files/Vkz6F6jYSike1hOpRFKB" alt=""><figcaption><p>Biusiness Rules page</p></figcaption></figure>

Once you click the icon, you'll be asked to give the rule set a name. You can also enter a free-form text description of the rule set. Click 'Save' to save the rule set.

<figure><img src="/files/lpO2LkEXCYqnc3JmbwgI" alt=""><figcaption><p>Saving a rule set</p></figcaption></figure>

After the rule set is saved, it can be reloaded at any time by navigating to 'Business Rule Sets' on the menu, in the 'Coverage Engine' section of the menu. Hover over the rule set you want to restore to view the icons on the right. Click the first icon to reload the business rules.

<figure><img src="/files/liyoMgMuMEIYUTxrBTrC" alt=""><figcaption><p>Viewing saved rule sets</p></figcaption></figure>

When you click the restore icon, you will be asked if you want to replace the existing business rules (the ones currently on the business rule page) with this set. Your options are 'Yes' (replace existing rules with this set), 'No' (add this set to the existing rules), or 'Cancel' (do not restore these rules).


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.apica.io/platform-docs/test-data-orchestrator-tdo/user-documentation/tdo-project-builder-user-guide/business-rules/business-rule-sets.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.