Extensions Setup#
The inputs of this task can be used as tokens and be replaced in the final extensions object. This task outputs the extensions defined by the user in the task settings, based on the extension templates that are available in the default value of the Automation Protocol Parameter with Data Type ExtensionParameters. The user is also free to add custom extensions and fill the required information in the settings. In runtime, this task uses the defined extensions and replaces the defined tokens with the respective input values.
Inputs#
| Name | Data Type | Description |
|---|---|---|
<custom list> | <custom> | Specific input values for each command |
| Activate | any | Sends the command |
Outputs#
| Name | Data Type | Values | Description |
|---|---|---|---|
| Extensions | any | Extensions array of objects to be used by the Equipment Setup task | |
| Success | Boolean | Triggered when the the task is executed with success | |
| Error | Error | Triggered when the task failed for some reason |
Settings#
On the General tab, you have the usual settings.
Additional inputs can be defined in the Inputs tab:
Additional outputs can be defined in the Outputs tab:
Note
The value of the extension parameter defined in the Outputs tab supports tokens to be replaced in runtime with the respective input values. When the DataType does not support tokens (for Integer, Decimal, Boolean, among others), the DataType can be changed to String and then the token can be added.
Behavior#
Configure the extensions to be used in the task's settings, with the possibility of using tokens received as the task's inputs and pass those extensions to the 'Equipment Setup' task to be used by the driver.
Remarks#
None