Workflow Start#
The task Start is used to set the starting point of a sub-workflow execution.
Inputs#
| Name | Data Type | Values | IsTrigger | Description |
|---|---|---|---|---|
Auto Input | None | Create a new Output based on the origin of the link |
Outputs#
| Name | Data Type | Values | Description |
|---|---|---|---|
<custom list> | <custom> | Custom Outputs that will receive the values transferred to the inputs of the Workflow task that will use the sub-workflow | |
Auto Output | None | Create a new Output based on the target of the link | |
| Activate | Any | Triggered when the Workflow Activate input is triggered |
Automatic Outputs#
This Task has implemented an automatic creation of dynamic outputs that dramatically reduce the configuration time.
The behavior is rather simple. Just link to the Link here to add new input and a copy of the origin is created (same name and data type as output), but no link is created. Also, you can drag the Link from here to add new output into an input of another task to create a new output of the same name and type and link them.
Settings#
In the General Tab, you have the usual settings.
In the Outputs Tab, you have the following options settings:
| Name | Data Type | Values | Default | Description |
|---|---|---|---|---|
| Name | String | Name of the output | ||
| Friendly Name | String | Text that will be displayed in the output | ||
| Type | enum | LongDecimalDateTimeBooleanStringInteger... | Type of the output value | |
| Collection Type | enum | NoneArrayMap | The Collection type of the output |
Behavior#
When a Workflow task has it's Activate triggered, all the inputs of the Workflow will be emitted as outputs of the Start task, setting the starting port of the sub-workflow execution.
Remarks#
This task doesn't have any Input. The Auto input exists only to allow creation of outputs based on other tasks outputs.



