> 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/using-occurrences-in-business-rules.md).

# Using Occurrences in Business Rules

There will be times when you want to create multiple occurrences of the same test; this is generally to support high volume testing such as performance testing. One way to get a high volume is to create multiple rules with many values. An easier way is to set the 'occurrences' value at the top of the 'Create Business Rules' window.

Start by clicking the pencil to the right of the rule to open the 'Create Business Rule' window. At the top left of the window is a line labeled 'Occurrences'. By default, this will be populated with '1'.

<figure><img src="/files/BZ22qbgulcCwFbuh7zKM" alt=""><figcaption><p>Occurrences field in business rules window</p></figcaption></figure>

Type the number of tests you want to run with each condition set in the business rule. Then click the 'Set' button at the bottom of the window to save this change. You will not see any changes in the business rules page when you do this; the impact of this setting will be seen in the Coverage Matrix.


---

# 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/using-occurrences-in-business-rules.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.