15.11 - Workflow Design Node Properties - Teradata Ecosystem Manager

Teradata Ecosystem Manager User Guide

prodname
Teradata Ecosystem Manager
vrm_release
15.11
created_date
May 2016
category
User Guide
featnum
B035-3201-056K

The following nodes are available to build a workflow.

Node Icon Node Type Description Maximum Inputs Maximum Outputs
Start Node Initial node of every workflow. When a workflow begins, it proceeds to the node specified after the Start node. Every workflow must have this node. 0 1
Task Node Activity node for a workflow. Five different types of Task nodes are available: Script Execution, Table Validation, Data Mover, Email, and Unity. The first output connection is followed if the task execution is successful. The second output connection is an optional error transition path (represented with a dashed line) which only executes if the Task node fails. 1 2
Split Node (Conditional) A decision node to direct different connection paths on a workflow. Requires a preceding Task node and the output determines which path the workflow follows. One condition for each outgoing connection. See next section for more details on using split nodes with conditions. 1
  • unlimited (preceding node is Script Execution or Table Validation using max rowcount mismatch table variable)
  • 3 (preceding node is Data Mover)
  • 2 (Preceding node is Email, Unity or Table Validation with sync variable)
Split Node (Unconditional) A decision node to allow multiple paths on a workflow. All outgoing connections are executed in parallel. Does not require a Task node preceding the Split node. 1 3
Merge Node (Conditional) A node to combine paths for a workflow. The workflow continues if one of the preceding task node completes. Based on outputs from conditional split 1
Merge Node (Unconditional) A node to combine paths for a workflow. The workflow continues only after all preceding task nodes are complete. 3 1
Exit Node Last node of every workflow. It shows the workflow is successful. Every workflow must have this node. unlimited 0

Split Node (Conditional) Properties

All conditions defined for conditional split nodes should be mutually exclusive. Do not create conditions that overlap. If none of the conditions are met, the workflow fails.
Preceding Task Conditional Operator Conditional Value
Email equal to successful or failed
Script Execution greater than, greater than or equal to, less than, less than or equal to, equal to, between integer or decimal
Unity equal to completed or failed
Data Mover equal to completed, failed, or cancelled
Table Validation with variable type max rowcount mismatch greater than, greater than or equal to, less than, less than or equal to, equal to, between integer or decimal
Table Validation with sync equal to in sync, or not in sync