Skip to content

Active Directory Conditionals

Conditional Processing or Execution Conditions gives you the power to decide if a particular action on Active Directory will be executed or not when the workflow is triggered by the incoming event. This is similar to the if-then-else logic applied to the execution of an action based on the attribute from the trigger event of the workflow.

Think of Conditional Processing as equivalent of if-then-else, as decision diamond in the flow chart, or the Conditional Branching in BPEL (Business Process Execution Language).

You can add conditional processing to any action in your workflow and evaluate which actions should be performed in response to a particular trigger event identified by its characteristics or the data attributes. You can apply complex logic using AND, OR and grouping of such conditions. Each of the conditions supports different operators based on the event data type being a string (abc and/or 123), number (123), boolean (true/false) etc. Read here to find more about Conditional Processing.

Example Scenario

We will take a scenario where you are using Active Directory as the trigger application. There could be multiple application actions to be invoked upon receiving an Active Directory trigger. Each of the actions in the flow would apply its own execution condition based on the data attributes of the Active Directory trigger event. This will allow each of the actions to independently choose to execute based on the defined execution conditions.

In the figure below ServiceNow action will be executed only if the Object class of the User added in the Active Directory contains 'person' AND the Department matches 'Human Resources'.

Active Directory execution condition

Figure 1. Active Directory Execution Condition