OMrun Help
Version 4.x
Version 4.x
  • Introduction
    • Features
      • 📊Facts
      • 🔢Figures
    • System Requirements
    • Terms and Definitions
    • Release Notes
      • 📄Version 4.2
      • 📄Version 4.1
      • 📄Version 4.0
    • ❓Getting Help
  • Installation
    • ↘️Install OMrun
      • 📃OMrun Paths
      • 🔑License Key
    • ✔️Verify Setup
    • 🗑️Uninstall OMrun
  • Configuration
    • Data Adaptor
      • Data Queries
    • Program Adaptor
    • Dashboard Configuration
    • Customize own adapter
      • Own data adapter
      • Own program adapter
    • Configuration Files
      • PublishConfig.cfg
      • OMrunDataProvider.cfg
      • OMrunGuiProvider.cfg
      • OMrun.exe.config
    • Using Variables
      • OMrun Variables
      • Environment Variables
      • Parameter
  • Start OMrun
    • Start via Desktop
    • Start via Batch File
    • Start via Task Scheduler
  • Menu Functions
    • ▶️Button Execute
    • ⏹️Button Stop
    • 🎓Button License
    • ⚙️Button Configuration
    • 📥Button Export
    • ❓Button Help
    • 📌Button About
    • 🗂️Button Windows
    • ⏩Shortcuts and Functions
  • Element Overview
    • Navigation Tree
    • Business System
    • Component
    • Environment
    • Scenario
    • Test Data Object
      • Query
      • Body
      • Business Mapping
    • Test Program Object
      • Batch
      • CSV Converter
      • Data Staging
      • Housekeeping
      • Json Converter
      • Program
      • RTL Generator
      • XML Converter
      • XML Converter XL
    • Parameter List
  • Result Analysis
    • Color Codes
    • OMrun Test Results
    • Excel Result Reports
    • OMdashboard
Powered by GitBook
On this page
  1. Configuration
  2. Using Variables

Parameter

PreviousEnvironment VariablesNextStart OMrun

Last updated 1 year ago

Parameter variables are used to pass up to four parameters into a query used by .

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.

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.

Design Test Object
OMrun test data object screen
OMrun test data object screen