Tibco Spotfire Conditions

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

To better illustrate Conditional Processing, we will use the use-case where a business wants to capture the analytics of when a service outage has occurred based on the incidents that were created in ServiceNow (Privileged) and put this data in Tibco Spotfire to generate a report. To have a more robust way of controlling what service outage is reported in Spotfire, Execution Conditions can be placed on the Tibco Spotfire action.

There could be multiple application actions attached to your workflow to be invoked upon receiving the service outage incident ticket, but each of the actions in the flow would apply its own execution condition based on the ServiceNow incident ticket. This will allow each of the actions to independently choose to execute based on the defined execution conditions.

Figure 1. Conditional Processing for Tibco Spotfire in Connect iPaaS

In the example shown in Figure 1, the configured action will only be executed if conditions for the incident Impact is "High" and is currently Active. Since these are ServiceNow (Privileged) Trigger fields, you can learn more about Trigger events here.