Skip to content

Coupa Conditionals

Conditional Processing or Execution Conditions gives you the power to decide if a particular action on Coupa 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 or 123), number (123), boolean (true/false) etc.

Example Scenario

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

In this example, the workflow is triggered when a new invoice has been created in Coupa. It has two actions, the first action will take effect in Microsoft Dynamics 365 and the second in NetSuite.

When using Coupa as the trigger application, the following attributes are available in all your conditional processing: - Gross-total: Gross total of the invoice from Coupa - Paid: Was the invoice paid or unpaid - Exported: Has the export been exported - Advanced-payment-received: Before the due date how much payment has been received - Many more attributes

In Figure 1 below, an action on Netsuite will only be performed if the Gross Total is above 70,000 and the invoice has been paid or the invoice has not been exported.

Conditional Processing for Coupa Connect iPaaS

Figure 1. Conditional Processing for Coupa on Connect iPaaS

Similarly in Figure 2 below, in the same workflow, the action on Microsoft Dynamics 365 CRM will only be performed if the Advance payment received is above 100,000 or the Gross total is above 100,000 and the invoice has been paid.

Conditional Processing for Dynamics Connect iPaaS

Figure 2. Conditional Processing for Dynamics Connect iPaaS