Task Nodes can be added to a Specification Macro to perform Tasks.
One example of a Task Node is the Release Document(s) Task:

As for every Nodes, Task Nodes have a Navigation Input
Connection Point.
Some Task Nodes require Properties to pass data into the Task and define the Tasks behavior.
There will be a
Data Input per required Properties.
As for every Nodes, Task Nodes have a Navigation Output
Connection Point.
Some Task Nodes will have additional Data Outputs.
Data Outputs are used to pass data from a Task back into a Specification.
Typically they will be connected to a Data Input node of a Task such as Drive Constant Value.
There will be a Data
Connection Point per Output.
As Tasks perform actions and report on their status in the Specification Reports, Task Nodes show 3 additional Navigation Connection Points at the bottom of the Node:

The 3 additional Navigation
Connection Points are:
when the Task was successful
when the Task was successful but warnings were raised

when the Task failedCreate one or more Connections with these Connection Points to trigger other Nodes.
For example:
An email can be sent (if using DriveWorks Autopilot) when the task has been successful.
A different email can be sent if any warnings or failures were encountered.
