User Information Prioritization in Workflow Design

When designing workflows, the system determines which authentication source to use for user‑related information based on a defined prioritization order. At runtime, the workflow selects the highest‑priority source that contains the required information, regardless of the order of workflow steps.

This prioritization affects how the system retrieves user identity data, such as user ID, profile attributes, roles, groups, and additional information.
Note:
  • Data Prompt refers to workflow steps such as Display a Form, where the user enters information directly during the workflow.
  • Default system values and the default user ID are used only when no authentication source provides the required data.
  • Identity Sources Considered: The workflow evaluates identity data from the following sources:
    • SAML Authentication
    • Directory Server Auth (LDAP or Active Directory)
    • Data Prompt
    • Default system values
  • Priority Rules by Information Category
    • User ID Priority: When a workflow step requires a unique user identifier, the system uses the following priority order:
      • SAML Authentication
      • Directory Server Auth
      • Default User ID
    • User Profile Information Priority: User profile data includes the following attributes:
      • Username
      • Email
      • Phone Number
      • First Name
      • Last Name
      • Display Name
      Profile data is determined in the following order:
      • SAML Authentication
      • Directory Server Auth
      • Data Prompt
    • Roles and Groups Priority: Workflow logic that evaluates group membership and user roles follows this order:
      • SAML Authentication
      • Directory Server Auth
    • Additional Information Priority: For additional identity attributes, the workflow uses:
      • SAML Authentication
      • Data Prompt
    Note: System Behavior: Each information category (user ID, profile details, roles and groups, and additional attributes) follows its own independent priority path. Once a valid source provides the required value, lower‑priority sources are not used. The order of workflow steps does not influence the identity source selected. All evaluations occur dynamically at runtime.