Contents x
    Workflow Actions - Check Condition
    • 02 Jun 2025
    • 2 Minutes to read
    • Print
    • Dark
      Light
    Contents

    Workflow Actions - Check Condition

    • Updated on 02 Jun 2025
    • 2 Minutes to read
    • Print
    • Dark
      Light
    Article summary

    Overview

    The Check Condition action in workflows can be used to verify that a condition is met before continuing. Typically this is used to take one or more values from the workflow form as inputs to pass through a Connect action (using the Connect Action workflow action) and validate that some condition is true. For example, an input in a workflow form might be that the requestor must be in a particular department (Technology) in order for the workflow to move to the next step. The requestor distinguished name (dn) can be passed through to Connect as a parameter, and a Connect action can verify that the person has a value of “Technology” in their department attribute on their RapidIdentity profile.

    Field

    Required (Y/N)

    Description

    Name

    YES

    Enter a name for this approval action step.

    Description

    NO

    Optional description of the approval action step.

    Previous Action

    NO

    A read-only field if a previous action exists,  it will be populated with the name of that action.

    Next Action

    YES

    Choose the next action step to perform if the condition is TRUE.

    Next Action on False

    YES

    Choose the next action step to perform if the condition is FALSE.

    Operation

    YES

    The Operation field defines which type of check to perform between Operands 1 and 2. There are four options:

    • Match Any Against Regular Expression: If any values resolved by Operand 1 match the regular expression defined for Operand 2, the condition will evaluate to true and the Next Action will execute next. Otherwise the Next Action on False will execute next.

    • Match All Against Regular Expression: If all of the values resolved by Operand 1 match the regular expression defined for Operand 2, the condition will evaluate to true and the Next Action will execute next. Otherwise the Next Action on False will execute next.

      Note

      If either of the regular expression options is chosen, the value defined for Operand 2 must be a valid regular expression.

    • Match Any Against Expression: If any values resolved by Operand 1 match the RapidIdentity expression in Operand 2, the condition will evaluate to true and the Next Action will execute next. Otherwise the Next Action on False will execute next.

    • Match All Against Expression: If all of the values resolved by Operand 1 match the RapidIdentity expression in Operand 2, the condition will evaluate to true and the Next Action will execute next. Otherwise the Next Action on False will execute next.

      Note

      If either of the expression options are chosen, the value defined for Operand 2 must be a valid RapidIdentity Workflow expression.

    Operand 1

    YES

    The criteria to check against Operand 2. This can be a string or expression.

    Operand 2

    YES

    The criteria against which Operand 1 is checked. For Regular Expression matches, this field must contain a regular expression. For Expression matches, this field must contain a RapidIdentity Workflow expression.

    Was this article helpful?
    What's Next