Conditional Processing or Execution Conditions gives you the power to decide if a particular action on MFT will be performed or not when the workflow is triggered by the incoming event. This is akin to the ability to apply 'if-then-else' logic to the execution of an action based on the value of 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 as a string, numeric, and boolean. Read here to find more about Conditional Processing.
We will take a scenario where you are using MFT as the trigger application. There could be multiple application actions attached to the flow that will be invoked upon receiving an event from the MFT trigger. Each of the actions in the workflow would apply its execution condition based on the data attributes of the MFT trigger event. This will allow each of the actions to independently choose to execute based on the defined execution conditions.
In this example, the workflow is triggered when records are extracted from new or updated CSV files in MFT. In this MFT trigger node, the user can add custom column headers along with its data type. The action will be performed only if the execution conditions are evaluated to be true based on the value of the defined column header.
In Figure 1 below, the action on Microsoft Teams will only be performed if the value of the custom column header
Location is equals to
San Diego in the event of the MFT trigger.