...
| Trigger Type | Trigger Description |
|---|---|
| Execute Trigger | Upon completion, this trigger will be automatically set and the next Unit, which has its Execute Trigger wired to this Complete Trigger, will be executed next. |
| Complete Trigger | This trigger gets set by the execution flow and the Unit will be called to execute. |
| Gliffy | ||||
|---|---|---|---|---|
|
| Info |
|---|
Units may have several Complete Triggers, which can be used to branch to individual flows. These triggers, when wired together, precisely define the execution flow of the Workflow. As a consequence to the strictly controlled execution flow, it is not possible that an Execute Trigger of a Unit gets wired to more than one trigger or port. |
Events
| Events are used to trigger execution of an entire Workflow, or just a subset of a Workflow, or a Subworkflow. This is a very powerful concept, allowing Workflows to be triggered from any Workflow condition, but also – for example – from network events. The simplest example is the Trigger on Start |
...
| event. |
| Event Type | Event Description |
|---|---|
| Trigger on Start | Sends a Trigger when the Workflow is started. |
| Trigger on Stop | Sends a Trigger when the Workflow is stopped. |
| Trigger on True | Sends a Trigger when the Update Signal input is true. |
| Trigger Tick | Sends a trigger based on a time interval. If the old-style method |
...
| of regular execution |
...
| is required, |
...
| this Unit can be used. |