Skip to content

ServiceNow Conditionals

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

Example Scenario

We will take a scenario where you are using ServiceNow as the trigger application. There could be multiple application actions attached to be invoked upon receiving a ServiceNow trigger.

Each of the actions in the workflow would apply its execution condition based on the data attributes of the ServiceNow (Privileged) 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 incident is created in a ServiceNow account. The trigger events will be passed to PagerDuty "Create Incident" action and Microsoft CRM 365 "Create Object" action.

When using ServiceNow (Privileged) as the trigger application, various attributes depending upon your action selection will be available to you in all your application actions.

In Figure 1 below, the action on PagerDuty will be carried out if incident(s) Active flag is True and Incident State equals New.

Conditional Processing in Connect iPaaS

Figure 1. Conditional Processing in Connect iPaaS

Similarly in Figure 2 below, in the same workflow, the object in Microsoft CRM 365 will only be created if the incident Urgency level equals High.

Conditional Processing in Connect iPaaS

Figure 2. Conditional Processing in Connect iPaaS