Workflow nodes #
Nodes have different properties based on their type. There are common attributes for all nodes:
| Attribute | Description |
|---|---|
| Name | Visible name of the node |
| Throw event | A name of the event that will be thrown by this node when executed |
| On/Off | If checked, node is active and can be executed |
Start node #
The start node begins the workflow. It defines conditions for start the workflow. The options are as follows:
- Interval
- Daily at specified time
- Weekly on specified day and at specified time
- Monthly on day number at specified time
- Cron string
- Other workflow finish
- Script
Finish node #
Finish node end the flow execution. There is an option to run a script that (e.g.) writes execution logs to a logging table.
Execute node #
Execution node is the basic node that allows to execute mappings in a proper order. It has the following attributes:
| Attribute | Description |
|---|---|
| Input parameter | |
| Execution method | It is possible to run or call mapping or run script; the method is selected in dropdown box |
| Mapping/script | An argument for selected execution method - mapping or text input for a script |
| Wait until finished | This option prevents flow to continue before this execution is not successfuly finished |
Wait for event node #
This node enables a synchronization between workflows. As each node can throw an event, this node allows to wait for a specific event before execution continues.
Lock/unlock resource nodes #
If some resource needs exclusive access, these nodes allows to manage its locking. There are two attributes for this:
| Attribute | Description |
|---|---|
| Input parameter | Addition parameter (if necessary) |
| Resource name | Identification of the resource |
Subflow execute node #
| Attribute | Description |
|---|---|
| Sub-workflow | Name of the sub-workflow that should be started |
| Input parameter | Addition parameter (if necessary) |
| Wait until finished | This option prevents flow to continue before this execution is not successfully finished |
Parallel start/merge nodes #
These two nodes enable parallelization of other nodes. It ensures that several actions are started in parallel (parallel start) or that engine waits for all parallel tasks are sucessufuly finished before start the next action.