Parameters
- Inbound: Used to send data during an action or contextualize an action
- Outbound: Used to record the results of actions performed by operators
The value of an input parameter must be provided in advance by the workflow mapping process. Any value entered by the operator or provided by a lookup on a form must be defined as an In/Out. These values can then be provided in advance. Otherwise, they are provided by the form and then written back to the result set.
All parameters values are included in eBRs and are the basis for the record of performed actions.
System parameters
System parameters are automatically maintained and can be used to change runtime values into actions.
This table shows available system parameters:
| Parameter | Description |
|---|---|
| WONumber | Production order number |
| QuantityOrdered | Quantity ordered on the production order |
| PartNumber | Material number of the material being manufactured on the production order |
| PartType | Type of the produced material |
| MachineStage | Name of the machine used in the operation |
Custom parameters
We recommend that you name custom parameters in a way that reflects their related workflow layer. For example, operation parameters can start with O_, phase parameters with P_, and routing parameters with R_.
Parameter deferral
At any level, parameters can either be given literal values at the time of assignment, or they can be deferred to a parameter from a higher level, so that the actual value used at runtime is whatever has been transferred.