Skip to content

Business Central Conditionals

Conditional Processing or Execution Conditions gives you the power to decide if a particular action on DocuSign 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 or 123), number (123), boolean (true/false) etc. Read here to find more about Conditional Processing.

Example Scenario

We will take a scenario where you are using Business Central as the trigger application. There could be multiple application actions invoked upon receiving a Business Central trigger. Each of the actions in the flow would apply its own execution condition based on the data attributes of the Business Central 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 a new entry for Customer is added in Business Central. It has two actions, a ServiceNow action and an Outlook send email action.

When using Business Central as the trigger application, the following attributes will be available to you in all your application actions for the entity Customers:

  • Name - Name of the Customer
  • Phone Number - Phone Number for the Customer
  • Email - Email address of the Customer
  • Website - Website URL of a Customer
  • Tax Liable - Specifies if the customer or vendor is liable for sales tax
  • Tax Area code - Specifies the tax area that is used to calculate and post sales tax
  • Tax Area Display Name - This is the display name of the area where the customer is established
  • Tax Registration Number - Specifies the customer's tax registration number for customers in EU countries/regions
  • Currency ID - This is a country currency code which will specify in what currency the transaction of money will happen
  • Shipment Method ID - Specifies which shipment method to use when you ship items to the customer
  • Payment Method ID - Specifies a code that indicates the payment terms that you require of the customer
  • Blocked - Specifies which transactions with the customer that cannot be blocked, for example, because the customer is insolvent
  • Last Modified Date Time - Specifies the last time stamp of data being modified

In Figure 1, the action on ServiceNow will only be performed if the Name of the Customer starts with "John".

Conditional Processing in Connect iPaaS

Figure 1. Conditional Processing in Connect iPaaS

Similarly in Figure 2 below, in the same workflow, an email from Microsoft Outlook will only be sent if the Email ends with robomq.io.

Conditional Processing in Connect iPaaS

Figure 2. Conditional Processing in Connect iPaaS