If Else Processor

Modified on Tue, 30 Nov 2021 at 02:41 PM

Overview

Evalutates a boolean SQL query and forwards the first processor input to the left output if all result rows are true or to the right output if at least one result row was false.


Please note that Integrated Workflow Execution Processors under this processor will still be expanded, and all parts of the integrated workflow not relying on one of the inputs will still be executed.


Input

The If Else processor has two input ports corresponding to two input datasets. The first dataset will be delivered by one of the output ports depending on the processor configuration.


Note that the second input port is not necessarily used in the processor configuration. Yet it has to be connected to a predecessor, even an empty dataset.


Configuration


Output

The processor has two output ports: the first output port corresponds to the True Output, the second one corresponds to the False Output.

If any of the values in this column is false or zero the assertion fails and the first processor input will be forwarded to the second output. If the all values in the column are true, the first input will be forwarded to the first output. 


Example

In this example, we will use the row count of the inner join of both input datasets as a condition in the processor configuration. Both input tables along with the join result are presented in the following figures.


Example First Input


Example Second Input



Join Result


Workflow



First Example Configuration


In this configuration, comparing to what was already mentioned, the row count is correct (we have two rows in the inner join table). Therefore the first input table is forwarded to the first output port.


First Example Result



Second Example Configuration


In this configuration, the row count is incorrect (we have two rows in the inner join table). Therefore the first input table is forwarded to the second output port.


Second Example Result

Further information and troubleshoot

The following error may occur when executing the workflow:

A solution to this problem is to delete the workflow links and connect the "If Else" processor again.

The workflow can now be normally executed.


Related Articles

Assert Processor

Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select atleast one of the reasons

Feedback sent

We appreciate your effort and will try to fix the article