Params
Params feature in Realtask allows users to customize runs and behavior using dataset that is configured before the run and during the run.
Params are stored under $params namespace and is available in all Realtask Formulas.
Param names are case-insensitive so if you define param named AccountNumber, you can refer to it as accountnumber
Params Types
There are multiple types of params, each of which defines how param value data type/content of the param value.
| Type | Description |
|---|---|
| Scalar | Scalar value (number of string). If source returns multiple values, then all sources are concatenated as comma separated values |
| Array | Array of particular source type. |
| Auto | Either scalar (if source returns single value) or array (if source returns multiple values) |
| Mapset | Mapset of given source from one field to another |
Params Precedence
Params are stored under $params namespace, and it's same namespace that is available in Job Params, Multi Run Params, Run Loop Params,
and Task Params. If you use same name in all places, which value takes precedence?
Params precedence rules is as follows.
Job Params
Multi Run Params
Run Loop Params
Task 1 Params
Task 2 Params
...
Task n Params
Params precedence is great feature which allows you to initialize some default value in Job Params and override that with specific value as part of Multi Run or Run Loop.
However, if you do not intend to override values, it is always best to use unique names across all params configuration. You can make use Job Action Validate Params which goes through all defined params and checks if any of the names overrides.