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

  1. Place the mouse pointer on a decision element to link it to two other elements that define two possible branches in the workflow.
    A blue arrow and a red arrow appear on the element's right.
  2. Place the pointer on the blue arrow, and while keeping the left mouse button pressed, move the pointer to the target element.
    A green arrow appears between the two elements and the target element turns green. The green arrow represents the true path the workflow takes if the input parameter or variable received by the decision element matches the decision statement.
  3. Release the left mouse button.
    The green arrow remains between the two elements. You have defined the path the workflow takes when the decision element receives the expected value.
  4. Place the pointer on the decision element, hold down the left mouse button, and move the pointer to the target element.
    A dotted red arrow appears between the two elements and the target element turns green. The red arrow represents the false path that the workflow takes if the input parameter or variable received by the decision element does not match the decision statement.
  5. Release the left mouse button.
    The dotted red arrow remains between the two elements. You have defined the path the workflow takes when the decision element receives unexpected input.

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.