dspConduct

Role Dependencies Overview

Role dependencies are designed in dspConduct™ to manage the logical progression of tasks that must be finished to complete a request. For example, dependencies establish that when processing a request to start a Post role type, the Application and Review role types must BOTH first be completed. The buttons on the Request Role Task page  for the Post role is disabled until all Application roles and the Review role that the Post role depends on are completed.

A Designer can assign one or many dependencies among roles. Those dependencies can be used across all assigned business processes and scenarios but only apply if both roles are within the same scenario.  

Role records become active when the dependent roles are completed. A role is completed when the Role Processor clicks the Finish button on the Request Role page and the validations all pass.

As roles are finished, workflow emails are sent to the users assigned to dependent roles, notifying them that they have work to complete.

Dependencies must be configured for role types for requests to process. Refer to Dependencies and Role Types and Add Dependencies to Roles for more information.

Data-driven dependencies can also be configured so that work on a role can begin when certain conditions are met. Refer to Assign a Condition to a Role Dependency Relationship for more information.

NOTE: Scenarios also have dependencies. Refer to Add a Dependent Scenario to a Scenario for more information.