Parameter variables are used to pass up to four parameters into a query used by Design Test 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 splitt information of a big data table into smaler pieces of information.
The values "1,2,3,4,5" within the red frame will replace the variable @param1 within the query A and B at execution time.
The values "1,2,3,4,5" within the yellow frame will replace the variable @param2 within the query A and B at execution time.
Like @parma3 / @param4 "not used" it is not necessary to define and use parameters. The @param variables are placeholders within a query and do replace 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.