Conditionals or Execution Conditions give you the power to decide if a particular action on Outlook will be performed or not when the workflow is triggered by the incoming event. This is similar to applying "if-then-else" logic to the execution of an action based on the attribute value coming from the workflow's trigger event.
You can add conditions to any action in your workflow.
To decide which actions should be performed in response to a particular trigger based on its characteristics or the data attributes. you can even apply a complex logic using AND, OR, and grouping of such conditions.
Each of the Conditionals support different operators based on the passed data type like string, number, boolean, etc. Read here to learn more about Execution Conditions.
We will take a scenario where you are using Outlook as the trigger application. There could be multiple application actions that could be performed upon receiving an outlook trigger.
Each of these actions in the flow could use different conditions as per the data attributes available in the Outlook trigger event. This allows each action to execute based on its defined execution conditions.
While using Outlook as the trigger application, the following attributes will be available to you in all your application actions:
|Cc-Name||Name of the CCed entity|
|Cc-Email Address||Email address of the CCed entity|
|Date-Email Send||Date on which email was sent|
|From-Email Address||Sender's email address|
|Subject||Subject of the email|
|To-Email Address||Receiver's email address|
|HTML Body (plain text)||The content of email in plain text|
|HTML Body (HTML)||The content of an email in HTML|
In Figure 1 below, when you receive an email from any correspondent of your client company
Star Fisheries with a subject starting with
Incident, the workflow will create a new incident in ServiceNow. In this case, only the email of interest in Outlook will result in the action performed inside ServiceNow.