Skip to content

Azure MySQL Conditionals

Conditional Processing or Execution Conditions gives you the power to decide if a particular action on Azure MySQL 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 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.

Example Scenario

At the time of defining an action on Azure MySQL you can use conditional processing to define certain conditions for its execution using the AND (+) or OR logic. Only if this logic is satisfied the action will be executed in Azure MySQL. For example in Figure 1, Azure MySQL action will be carried out only when the CC-Name does not contain John and subject exists from Microsoft Outlook. You can construct complex conditions to create filter criteria using AND (+) and OR (OR) conditions.

Azure MySQL execution condition

Figure 1. Execution Condition for Azure MySQL Application on Connect iPaaS