Connections are used to join together Specification Macro Nodes. Connections are made between each of the Nodes Inputs and Outputs to create a Specification Macro flow. For more information about Nodes see: Specification Macro Nodes
Connection Points are what is used to make Connections between different Nodes. The two different types of Connection Points are Navigation and Data Points (green for Navigation and black for Data). For more information on Specification Macro Connection Points see here.
Connections can be easily thought about with some simple rules to how they work. These are:
All Inputs except Data Inputs can have multiple Connections. This is because Data Inputs can only take one Output.
You can only connect Node Navigation and Data points to same type of point (green points to green points and black points to black points).
DriveWorks will execute all valid Tasks from the first available route before backtracking and checking for all other valid Tasks.
When three Tasks are all connected to the Start Node and all are then connected to a fourth Task, DriveWorks will execute the first and fourth Tasks first (the most direct route) before executing the second to fourth and third to fourth Tasks.
To create a Connection:
To delete a Connection:
There are a two different Connection types possible. These are Navigation and Data but there are multiple ways of using these connections. Here are some examples:
|If the order of execution matters||This example shows how to use a Navigation Connection so that a Node is executed after another one. This is how you can force the order in which Nodes are executed.|
|If the order of execution doesn't matter||This example shows how to use Navigation Connections so that two Nodes are executed after another one. This is if you want these two Nodes to be executed but you don't need to force their order of execution.|
|Sharing Data between Nodes||This example shows a Data Connection between the Released Documents Output of the Release Document(s) Task and the Constant Value Input of the Drive Constant Value Task. This means that the constant will be driven with a pipe-bar list of all the released documents.|
|Reacting to the status of a Task||This example shows how you can use Tasks Status Output Connection Points to run different Nodes depending on its Status. For more information see Specification Macros Task Node.|
|Triggering Tasks based on Conditions||This example shows how you can use Condition Nodes to trigger other Tasks and Conditions. For example, Cancel Specification would be executed if one condition fails, Released Documents if the same condition passes and Toggle if two conditions pass.|