Conditional Processing or Execution Conditions gives you the power to decide if a particular action on FinancialForce will be performed 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 decide 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 types like a string, number, boolean, etc. Read here to find more about Conditional Processing.
We will take a scenario where you are using FinancialForce as the trigger application. There could be multiple application actions attached to be invoked upon receiving a FinancialForce trigger. Each of the actions in the flow would apply its own execution condition based on the data attributes of the FinancialForce trigger event. This will allow each of the actions to independently choose to execute based on the defined execution conditions.
In the example below, we put a single HubSpot action to synchronize the contact data received from the FinancialForce trigger event. As you can see, the HubSpot action will only continue the process whenever the "Department" from FinancialForce trigger event contains 'Stockton' OR the "Title" from FinancialForce trigger event contains "Executive".
Since the FinancialForce application in Connect iPaaS utilizes the metadata API provided by FinancialForce, all the fields you see from the 'item' dropdown are available for you to choose for setting up the criteria.