Various Branch and Merge Node Conditions | Vantage Analyst - 1.1 - Various Branch and Merge Node Conditions - Vantage Analyst

Vantage Analyst User Guide

prodname
Teradata Analytic Apps
Vantage Analyst
vrm_release
1.1
category
User Guide
featnum
B035-3805-099K
Branch node condition options follow:
  • Execute all (selected by default)
  • Execute all true conditions
  • Execute the first true condition only

The Merge node condition option specifies if all executed branches must succeed when you execute the workflow (check or clear this option).

Base Scenario: Branch Node Executes All Conditions; Merge Node Indicates All Executed Branches Must Succeed


Base scenario where branch node executes all conditions

Path A includes a failing node followed by a second node; Path B includes success node. A single node follows the Merge node.

Upon execution, the failing node skips the second node and goes to the Merge node to determine the outcome. The workflow fails; status values follow:
  • Unsuccessful (first node is Path A)
  • Skipped (second node in Path A)
  • Successful (node in Path B)
  • Unsuccessful (Merge node)
  • Skipped (node that follows the Merge node)

Branch Node Implements Workflow-Level Variables for Paths A and B, Execute All True Conditions


Branch node that implements workflow level variables
  • The workflow-level variable value in Path A is equal to 1, meaning it will execute its path.
  • The workflow-level variable value in Path B is equal to 0, meaning it will not execute.
Upon execution, the workflow fails. Status values follow:
  • Unsuccessful (Failing node causes Path A to fail)
  • Skipped (node in Path B) because the Branch node is set to execute all true conditions
  • Skipped node after Merge node

Branch Node Implements Workflow-Level Variables for Paths A and B, Execute All True Conditions; Merge Node Setting is Cleared

Both workflow-level variables will execute (both values are true):
  • The workflow-level variable value in Path A is equal to 1
  • The workflow-level variable value in Path B is <10

Because the Merge node setting (All executed branches must succeed) is not set, the workflow is successful even though the failing node fails because the alternate path can be executed. The node after the Merge node also succeeds.

Upon execution, the workflow succeeds. Status values follow:
  • Unsuccessful (failing node)
  • Skipped (failing node success path)
  • Successful (alternate path, merge, and after merge nodes)

Failing Node Implements Explicit Error Path, All Executed Branches Must Succeed

Specifying an error path to go to the Merge node means action is being taken to manage that error. The path drawn from the failing node to the Merge node means treat this as a success.


Failing node implements explicit error path

When the All executed branches must succeed setting is checked on the Merge node, the failing node is going to be considered a success.

Upon execution, the workflow succeeds. Status values follow:
  • Unsuccessful (failing node)
  • Skipped (failing node success path)
  • Successful (alternate path, merge, after merge)

Failing Node Points to Another Node

The failing node points to another node; action is taken based on the error but it still fails and terminates the workflow. A path is drawn from the failing node to another node but the path still succeeds. The node pointed to can be a SQL node or email notification or a rule that converts to log file or table. The failing node error path node points to the End failure node.


Failing node points to other node

The alternate path can still be executed. Anything that executes at a point when the End failure is achieved needs to be canceled.

Workflow execution shows that the alternate path was canceled and the node after the merge is skipped.

Upon execution, the workflow fails. Status values follow:
  • Unsuccessful (failing node)
  • Skipped (failing node success)
  • Successful (failing node error path)
  • Canceled (alternate path)
  • Skipped (merge, after merge)

Handling an Error and Continuing Execution

A failing node's error path points to another node that handles the error and continue execution and get evaluated by the Merge node.


Handling error and continuing execution
Upon execution, the workflow succeeds. Status values follow:
  • Unsuccessful (failing node)
  • Successful (failing node error path, alternate path, merge, after merge)