Workflows can implement decision functions that define different courses of action according to a Boolean true or false statement.
Decisions are forks in the workflow. Workflow decisions are made according to inputs provided by you, by other workflows, by applications, or by the environment in which the workflow is running. The value of the input parameter that the decision element receives determines which branch of the fork the workflow takes. For example, a workflow decision might receive the power status of a given virtual machine as its input. If the virtual machine is powered on, the workflow takes a certain path through its logical flow. If the virtual machine is powered off, the workflow takes a different path.
Decisions are always Boolean functions. The only possible outcomes for each decision are true or false.
Custom Decisions
Custom decisions differ from standard decisions in that you define the decision statement in a script. Custom decisions return true or false according to the statement you define, as the following example shows.
if (decision_statement){ return true; }else{ return false; }
Create Decision Element Links
Decision elements differ from other elements in a workflow. They have only true or false output parameters. Decision elements have no exception linking.
Prerequisites
Verify that the Schema tab of the workflow editor contains elements, including at least one decision element that is not linked to other elements.
Procedure
Results
You have defined the possible true or false paths that the workflow takes depending on the input parameter or variable the decision element receives.