Skip to main content



Coupa Success Portal

Process Builder Global Context


We've introduced a new Process Builder framework that provides a global context to your processes. What this means is that now, all information that's captured or generated by an object or process step is available for conditions and inputs for any later step processes. Previously, Process Builder let you conditionally automate actions using information from the object hosting the trigger or the outcomes of the previous process step, but not both. Additionally, step conditions couldn't use the outcome of all previous steps in the process. The conditions for the next step were limited to the outcome of the previous step.

What this mean was that process builders were limited to configuring single-path if-then processes with no possibility for more complex logic paths. So now, by allowing data outputs from each of the process steps to be available as inputs and conditions in subsequent steps, process builders can create processes of growing complexity and flexibility.

How it works

When you create a new Process, you'll see a new field called Object. This field shows you exactly what object or document your process step will act on. Previously, this field wasn't shown because it can only be set by your selection for the trigger Document field. But now, Coupa explicitly shows that the object you're acting on. In the example below, we chose Invoice as our document type, so the object that's acted upon is shown as Trigger.Invoice.


For Step 1 in a process, the fact that Coupa shows you the object isn't very helpful since you can't change the Object field, and the Conditions Trigger.Invoice field can't be changed.

However, for Step 2 and all other following steps, you can change the Object field and the Conditions object. This means for Step 2, you can perform an action based on either the initial trigger (Trigger.Invoice) or the Step 1 action result (Step 1.Invoice). 

process-step-2-object field.png

Like the Action, the conditions you set for Step 2 can also be based on either the initial trigger (Trigger.Invoice) or the outcome from Step 1 (Step 1.Invoice). So, as you add additional steps, you can perform actions and set conditions based on any of the previous steps or the initial trigger conditions, or even a combination of the results from previous steps. For example, you can build a process where Step 3 proceeds only when conditions:

  • For Step 1 have been met
  • For Step 2 have been met
  • For both Step 1 and Step 2 have been met

This gives you much greater flexibility when creating processes including the ability to build parallel actions in a single process or build scenarios with more complex condition sets that span the outcome of multiple steps.

Upgrade impact

Roles and permissions





This enhancement is included with the Coupa Core platform and doesn't require any configuration to start using. 

  • Was this article helpful?