> For the complete documentation index, see [llms.txt](https://dbi-services.gitbook.io/omrun-help/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://dbi-services.gitbook.io/omrun-help/version-4.x/configuration/using-variables/parameter.md).

# Parameter

Parameter variables are used to pass up to four parameters into a query used by [Design Test Object](/omrun-help/version-4.x/element-overview/test-data-object.md).

If using the @param concept within a "WHERE" clauses it is possible to use the same query with different parameters listed in several rows to split information of a big data table into smaller pieces of information.

<figure><img src="/files/UU8adBGvA5pCL3UfM1K5" alt="OMrun test data object screen" width="80%"><figcaption><p>OMrun test data object screen</p></figcaption></figure>

The values "1,2,3,4,5" within the red frame will replace the variable @param1 within the query A at execution time.

The values "1,2,3,4,5" within the yellow frame will replace the variable @param2 within the query B at execution time.

Like @param3 / @param4 are "not used" it is not necessary to define and use parameters. The @param variables are placeholders within a query and are replaced with the relevant value during run time.

The behavior is the same for all 4 parameters.\
The remark field is important to fill out with unique comments for each row in a parameter list because it is distributed to the OMdashboard.

It is possible to nest any @param into another @param and use it within a query. As an additional benefit a environment variable can also be uses within the parameter list in combination with hardcoded parameter value e.g. XX-\@VAR\_Test\_Env.


---

# 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://dbi-services.gitbook.io/omrun-help/version-4.x/configuration/using-variables/parameter.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.
