Dynamics 365 CRM 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 or 123), number (123), boolean (true/false) etc. Read here to find more about Conditional Processing.
We will take a scenario where you are using Dynamics 365 CRM as the trigger application. There could be multiple application actions invoked upon receiving a Dynamics 365 CRM trigger.
Each of the actions in the flow would apply its own execution condition based on the data attributes of the Dynamics 365 CRM trigger event. This will allow each of the actions applications to independently choose to execute based on the defined execution conditions.
In this example, the workflow is triggered when an object is created in Dynamics 365. The trigger events will be to add a row in Smartsheet and create a new object in Coupa.
When using Dynamics 365 as the trigger application, attributes depending upon your entity selection will be available to you in all your application actions.
Click here to know more Entities and their attributes in Dynamics 365.
In Figure 1, the Smartsheet action of adding a new row will only be performed if the account created in Dynamics CRM has attribute
Category which is equal to
Similarly in Figure, in the same workflow, the action on Coupa will only be performed if attribute
Marketing Only is set as