Property | Description |
|---|---|
Process Code | Identifier of the process |
Code | Identifier for the parameter |
Description | A short description of the parameter, usually stating its use |
Type | The data type of the parameter: (blank), Integer, Text, Code, Decimal, Option, Boolean, Date, Time, and DateTime |
Table Name | The related table of the parameter |
Field Name | The related field of the parameter |
Scope | The scope of the parameter: either Stack or Process |
Initial Value | An Expression functions to give the parameter an initial value |
Validation | An Expression functions that executes when the parameter receives a value |
Lookup Activity No. | The activity called when a lookup executes on the parameter |
No. of Related Parameters | The number of parameters that receive a value when this parameter receives a value |
Option String | When Table Name and Field Name are set and type is Option, this field populates automatically. Replace with other values if needed. Also applicable for boolean values. |
Decimal places
Only available for decimal parameters. Controls the decimal precision of the parameter value.
Use the following structure: "Minimum Decimal Value:Maximum Decimal Value", for example "2:2" or "4:6".
When no value is specified, the default value from Anywhere Setup properties applies.
Scope
Process parameters are available during the process's lifecycle, starting from the activity where they are first used, or from the start of the process when they have an initial value. They go out of scope when the process changes.
Stack parameters are available from the first activity they are used until they reach the same activity again. They are not available on that activity but initialise again when it is reached. They have a sliding scope: when the same parameter is modified in a later activity, it attaches to that activity and initialises when that later activity is reached.
.png)