# Parameter

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

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="https://2873353689-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfK1YJaTCqOiS0L22wVKG%2Fuploads%2Fgit-blob-c22ac9920ace5333466a4f5833b6b59e8e15a85e%2FOMrunHelp_VarParameters1.gif?alt=media" 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.