1.1 - Default Branch and Merge Node Conditions - Teradata Analytic Apps - Vantage Analyst

Vantage Analyst with Machine Learning Engine User Guide

Product
Teradata Analytic Apps
Vantage Analyst
Release Number
1.1
Published
December 2019
Language
English (United States)
Last Update
2020-08-06
dita:mapPath
ezh1551894635141.ditamap
dita:ditavalPath
wsp1565965728073.ditaval
The following use cases have the Branch and Merge node conditions set to default values:
Node Type Default Condition Setting
Branch Execute all
Merge All executed branches must succeed

Workflow with Two Nodes in Path A and One Node in Path B

None of the nodes in the workflow has a failure path configured.

If the first node in Path A fails, the second node is skipped and the failed node looks to the Merge node to determine the resolution. Even if the node in Path B succeeds, this workflow is considered a failure because of the Merge node configuration (All executed branches must succeed).

The default path proceeds to the End (failure) node in the workflow.

When you execute the workflow, the Status values are listed as follows:
  • Unsuccessful (first node in Path A)
  • Skipped (second node in Path A)
  • Successful (node in Path B)

Success Scenario: Two Nodes in Path A with Success and Failure Paths Defined on the First Node, One Node in Path B

The first node in Path A has a success path that points to the second node in Path A, and a failure path that points to the Merge node. Because an explicit failure path is created on the first node, when it fails, the Merge node ignores the failure because the second node in Path A can still succeed.

Failure Scenario: Two Nodes in Path A with Success and Failure Paths Defined on the First Node, One Node in Path B


Failure scenario with two nodes in path A

The first node node in Path A has a success path that points to the second node in Path A, and a failure path that points to a node that fails the workflow, pointing to the End (failure) node.

Upon execution, the second node on Path A is skipped because the first node failed. Additionally, the node in Path B is canceled, which causes any subsequent Path B nodes to be skipped.

The workflow status values follow:
  • Unsuccessful (first node in Path A)
  • Skipped (second node in Path A)
  • Canceled (first node in Path B)
  • Skipped (subsequent nodes in Path B)