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 equivalent of if-then-else, as a 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.
We will take a scenario where you are using DocuSign as the trigger application. There could be multiple application actions invoked upon receiving a DocuSign trigger. Each of the actions in the flow would apply its own execution condition based on the attributes of the DocuSign trigger event. This will allow each of the actions to independently choose to execute based on the defined execution conditions.
When using DocuSign as the trigger application, the following attributes will be available to you in all your application actions:
- Status - Status of the document
- Documents_Uri - Unique Resource Identifier (Uri) of the document
- Recipients_Uri - Uri of the recipients
- Attachments_Uri - Uri of the Attach document
- Envelope_Uri - Uri of the envelope
- Email Subject - Subject of the email in which document sent
- Email Message - Message of the email in which document sent
- Envelope Id - Unique value of the envelope
- Created DateTime - Template created time
- LastModified DateTime - Template last Modified time
- Sent DateTime - Template sent tome
- StatusChanged DateTime - Envelope status update time
- Templates_Uri - Uri of the template
- Expire Enabled - Expiry is save of the template, it is boolean (true/false) value
- SignatureProvider Envelope - Provider of the signature to the envelope
- UserName - Name of the user
- UserId - Unique ID of the user
- Email - Email ID of the user
In Figure 1, the action on Microsoft Dynamics 365 will only be performed if
Email Subject contains "Business Contract".
Similarly in Figure 2 below, in the same workflow, an MySQL record will only be created if the
Signature Provider is true AND
Email Subject contains "Job Offer".