Add Data-Driven Dependency Conditions

A data-driven dependency condition identifies a condition within a field when processing a scenario that determines whether a subsequent dependent scenario or role is processed or if a workflow notification is sent. Refer to Add a Dependent Scenario for more information.

Before performing this task, Design a Governance Hierarchy.

Once conditions are added to the category, the Designer assigns conditions to a scenario dependency relationship.

Conditions can also be assigned to roles. Refer to Assign a Condition to a Role Dependency Relationship and Add Dependencies to Roles for more information.

This topic contains the following sections:

Data-driven Dependency Condition Example

The following flowchart illustrates an example situation for using a data-driven dependency condition:

The same logic applies to data-driven dependencies conditions for roles. If a condition is met in a role, a subsequent role is processed. Otherwise it is skipped.

Along with processing dependent scenarios or roles, conditions control whether workflow messages are sent. If a scenario or role is not processed, the workflow notifications are not sent.

If multiple conditions exist, if one of the conditions are not met, processing stops and the role is automatically finished. If one data record meets the condition, the workflow is sent and the role is not automatically finished.

Add the Data-Driven Dependency Condition

To add data-driven dependency conditions to a category in dspConduct™:

  1. Select dspConduct > Design in the Navigation pane.

  2. Click Vertical View for the category.

  3. Click Edit.

    View the field descriptions for the Category page’s Vertical View.

  4. Select the data source for the condition table in the Condition Table Datasource Id list box.

  5. Click Save.

  6. Click the Conditions icon.

  1. If no records exist, the page displays in add mode. Otherwise, click Add.

    View the field descriptions for the Conditions page.

  2. Select the table name for the condition from the TABLE NAME list box.

  3. Select the column for the condition from the COLUMN list box.

  4. Select the operator for the condition from the OPERATOR list box.

  5. Enter a value for the condition in the CONSTANT field.

  6. Click Save.

View the Dependency Relationships for a Data-Driven Dependency Condition

A Designer can view the scenarios or roles that use data-driven dependency conditions at the category level.

Before performing this task, Create a Category, Add Data-Driven Dependency Conditions and Assign a Condition to a Scenario Dependency Relationship.

To view the dependency relationships for a data-driven dependency condition in dspConduct™:

  1. Select dspConduct > Design in the Navigation pane.
  2. Click Vertical View for the category.
  3. Click the Conditions icon.
  4. Click the SCENARIO DEPENDENCIES or ROLE DEPENDENCIES icon.

View the field descriptions for the Scenario Dependency Condition page.

View the field descriptions for the Role Dependency Condition page.