Azure AD Conditionals¶
Conditional Processing or Execution Conditions gives you the power to decide if a particular action on DocuSign 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 an 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 Azure AD as the trigger application. There could be multiple application actions invoked upon receiving an Azure AD trigger. Each of the actions in the flow would apply its own execution condition based on the data attributes of the Azure AD trigger event. This will allow each of the actions to independently choose to execute based on the defined execution conditions.
In this example, the workflow is triggered when a new user is created in Azure AD. The trigger events will create a new object in Salesforce and send an email from Microsoft Outlook.
When using Azure AD "User Created" as the trigger event, attributes of user object will be available to you in all your application actions.
As seen in Figure 1, a new object will be created on Salesforce only if the user Location is in Fairfax County or Montgomery County.
Similarly in Figure 2, in the same workflow, an email from Microsoft Outlook will only be sent if user Location does not exist.
