Conditionals or Execution Conditions give you the power to decide if a particular action on NetSuite 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 the actions that 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.
To illustrate processing of Conditionals, we will take a scenario where you are using NetSuite as the trigger application.
There could be multiple application actions that can be invoked upon receiving a NetSuite trigger event.
Each of these actions in the flow could use different conditions as per the data attributes available in the NetSuite trigger event. This allows each action to execute based on its defined execution conditions.
In this example, the workflow is triggered when a new customer has been created in NetSuite. It has two actions, the first is a Microsoft Dynamics 365 action and the second is a Coupa action.
When using NetSuite as the trigger application, the following attributes will be available to you in all your application actions:
- First Name - The first name of the representative of the vendor in NetSuite
- Last Name - The last name of the representative of the vendor in NetSuite
- Subsidiary / Name - The subsidiary of the vendor
- Is 1099 Eligible - If the vendor is 1099 eligible
- Company Name - The name of the company that the vendor is apart of
- Labor Cost - Cost of the labor for this vendor
- Many more attributes
In Figure 1 below, the action on Microsoft Dynamics will only be performed if the Company Name of the new Vendor created in NetSuite is "Onyx Research Laboratories".
Similarly, in Figure 2 below, in the same workflow, an action on Coupa will only be performed if the
Representing Subsidiary of the Vendor created in NetSuite equals "Reach Research Laboratories".