12.1.6.2 Dependency Configuration

Dependencies are configured using the AF_TB_COMBINATION_DEP_MAPPING table.

Each dependency includes:

  • Template Name
  • Parent Combination
  • Child Combination
  • Condition

The following table outlines the supported dependency conditions in the Template Builder Framework and describes how each condition controls the activation behavior of child combinations.

Table 12-6 Supported Dependency Conditions

Condition Type Behavior
Not Null or Has Value The child combination becomes active when the parent combination contains any value.
Specific Value Match The child combination becomes active only when the parent combination equals a specified value.
The following rules define how dependency relationships are structured and enforced within a template in the Template Builder Framework.
  • Dependencies apply within the same template.
  • One parent can control multiple children.
  • A child can depend on multiple parents, if supported.
  • All dependency logic is configured through database mapping.