Working with decisions
In this workflow, we will see how decisions can be implemented with Orchestrator. You will learn how to create basic and custom decisions.
Getting ready
We just need a working Orchestrator, and you will need the rights to create new workflows and run them. We will work with the Orchestrator Client.
We need a new workflow where we can add a decision. You also should know how to work with logs.
For the Decision Activity element, we will be reusing the workflow we created in the Workflow basics recipe in this chapter (3.01 in the example package).
How to do it...
There are three decisions that can be used in Orchestrator; we will discuss each in the following sections.
Basic decision
The basic decision lets you check a single variable against a condition. A condition is always something that is either true or false. For example, the condition 5 > 3 is true, whereas the condition "Team" contains "i" is false.
Create a new workflow and define an in-parameter of the
String
type...