Default Branch and Merge Node Conditions | Vantage CX - Default Branch and Merge Node Conditions - Vantage Customer Experience

Vantage Customer Experience User Guide

Deployment
VantageCloud
VantageCore
Edition
Enterprise
IntelliFlex
VMware
Product
Vantage Customer Experience
Release Number
1.6
Published
October 2023
Language
English (United States)
Last Update
2023-10-26
dita:mapPath
hbt1563223944614.ditamap
dita:ditavalPath
oyf1565965838286.ditaval
dita:id
tmo1562969305444
Product Category
Teradata Applications
The following node types have Branch and Merge node conditions set to the default values:
Node Type Default Condition Setting
Branch Execute all
Merge All executed branches must succeed

Workflow or Customer List with Two Nodes in Path A and One Node in Path B

None of the nodes in the workflow or customer list 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 or customer list 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 workflowor customer list.

When you execute the workflow or customer list, 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 or customer list 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)