Synchronize#
The task Synchronize is used to synchronize data between tasks.
Inputs#
| Name | Data Type | Values | Description |
|---|---|---|---|
<custom list> | <custom> | Inputs to synchronize | |
Auto Input | None | Create a new Input and output based on the origin of the link | |
| Activate | Any | Activates the task execution |
Outputs#
| Name | Data Type | Values | Description |
|---|---|---|---|
<custom list> | <custom> | outputs synchronized | |
Auto Output | None | Create a new Output and Input based on the target of the link | |
| Success | Boolean | If there was no problem emits a true | |
| Error | Error | Error that occurred during the processing of this task |
Auto Inputs/Outputs#
This Task has implemented an automatic creation of dynamic inputs/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) and the link is also created between the two elements. 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 and the following options settings:
| Name | Data Type | Values | Default | Description |
|---|---|---|---|---|
| Expiration Time | Integer | 60000 | Maximum amount of time (in milliseconds) to keep the inputs of a context without a new value. Each new value restarts the count. Set to 0 to keep the inputs until Activate is triggered. | |
| Emit when all defined | Boolean | False | Only emit the outputs when all inputs are filled within the same zone/context |
In the Inputs/Outputs Tab, you have the following options settings:
| Name | Data Type | Values | Default | Description |
|---|---|---|---|---|
| Name | String | Name of the input and output | ||
| Friendly Name | String | Text that will be displayed in the input/output | ||
| Type | enum | LongDecimalDateTimeBooleanStringInteger... | Type of the input/output value | |
| Collection Type | enum | NoneArrayMap | The Collection type of the input/output |
Behavior#
The top example, shows an equipment interface that uses the same event for both loader and unloader. The only way to identify which scenario we are handling, is by the $Port variable supplied by the event. Now, let's imagine both occurrences happen at the same time and you want to make sure that the Loader performs a TrackIn and the Unloader a TrackOut.
Without the Synchronize Task, it would require far more logic/Tasks to make sure the $MagazineId variable would be the correct one on the TrackIn and TrackOut respectively.
Depending on the settings, the outputs will emit their values when the Activate input is triggered immediately or only if all inputs are filled.
If during the specified timeout period the Activate is not triggered, all the input values received will be discarded.
Remarks#
This task uses a specific structure of context-based data called zone. More information on this topic can be read in the Zones page.
When Activate is received, the task emits only the inputs received in that context. An input that has received no value emits nothing, even when it has a default value.
Any value received on Activate, false included, releases the inputs. An Activate that arrives before any value is not kept: with Emit when all defined off, the task emits the error Execution context '<id>' doesn't have any inputs, and with it on, the activation is ignored.



