dspConduct

Dependencies and Role Types

The request process uses standard roles with role types that require specific dependencies.

These dependencies must be configured. Refer to Add Dependencies to Roles for more information.

The Application type role is used to enter data into pages in the Content WebApp for preparation to send to the system(s) of record. Application roles:

  • Must have a lower priority than the Review or Post roles (i.e., the Review role must have a higher priority than the Application role).
  • Can have a dependency on other Application type roles.
  • Cannot be dependent on a Review or Post role.  

The Review type role is used to review changes to a preceding dependent Application type role. Review roles:

  • View all changes made within the execution of a request and approve or reject them.  
  • Review everything within the tasks of their dependent Application roles within a scenario.
  • Must have a higher priority than the Application type role but a lower priority than a Post role.
  • Can only be dependent on Application roles.

The Post type role is used when all Application and Review roles are complete to send the collected and validated data to the system(s) of record. A Post role must have a higher priority than a Review role.

NOTE: The Post role can be configured to execute automatically if dependencies are completed. Results can be emailed to the Requestor and any other persona configured at the request level. This Auto Post Role option is set on the Scenario (Roles) page’s Vertical View.

NOTE: The Auto Post Role option can only be set for the Post role.  Refer to Auto Post a Request for more information.