Make a decision flow logic

You can use the decision table branching logic in situations where multiple conditional paths are required, as an alternative to nested If, Else If, or Else flow logic. For example, if you want to determine what kind of car insurance you need, you can add inputs such as your age accident history, and car model to the decision table to determine a level of insurance coverage. This logic can save you time and present a more readable format than nested if conditions or switch case statements.

The Make a decision flow logic requires that you create an external decision table for its branch paths. Each answer that is defined in the decision table results in a branch path within Flow Designer. Decision tables accept any number of inputs, include any number of decisions, and result in a finite set of decision paths. You can configure a decision table to determine a single path or multiple paths. For more information on decision tables, see Decision Tables.

Inputs


Input	Description
Decision Label	Descriptive label for the decision that you want to make. For example, you can create the `Recommended Insurance Policy` label if you want to determine the level of insurance coverage that you need. This value overrides the default action label.
Decision table	Reference to a Decision Table [sys_decision] record. This record provides the decision input answers that are available to the flow.
Execution approach	Approach that you select to execute your decision. First decision that matches: Runs only the branch for the first matching decision answer. Run all decisions that match: Runs all branches with a matching decision answer.
Include otherwise	Option to add the otherwise branch. The flow only runs this branch when no other branch runs.
Decision table inputs	List of Decision Input [sys_decision_input] records that are associated with your decision table. Flow Designer displays a separate input for each record. For example, if you have decision inputs for `Units Ordered` and `Location of Sale`, an input displays for each record.

Outputs


Output	Description
Decision answer record	Record that was created after the decision inputs were evaluated.

Example: Use make a decision flow logic to determine insurance coverage

In this example, the flow uses a decision from the Insurance Coverage decision table, which an administrator had configured to determine the insurance coverage that was based on three inputs. The flow displays all the inputs that were used by the decision table in Flow Designer. These inputs can be entered manually, or by dragging data pills into the inputs from the Data pane on the right side of the screen. Below this section, the branches for each answer are shown in the decision table.

Execution details

The Flow execution details tab provides runtime information about the flow logic.

The header shows the state, start time, and runtime for the flow logic.
The action shows details about the decision table configuration and inputs.
Each possible answer for the decision table is represented as a branch. The state field indicates whether the branch was evaluated and the evaluation result. This section also displays details about the actions that are taken within a branch. Branches that evaluate to true are highlighted in green.

Make a decision flow logic

Inputs


Input	Description
Decision Label	Descriptive label for the decision that you want to make. For example, you can create the `Recommended Insurance Policy` label if you want to determine the level of insurance coverage that you need. This value overrides the default action label.
Decision table	Reference to a Decision Table [sys_decision] record. This record provides the decision input answers that are available to the flow.
Execution approach	Approach that you select to execute your decision. First decision that matches: Runs only the branch for the first matching decision answer. Run all decisions that match: Runs all branches with a matching decision answer.
Include otherwise	Option to add the otherwise branch. The flow only runs this branch when no other branch runs.
Decision table inputs	List of Decision Input [sys_decision_input] records that are associated with your decision table. Flow Designer displays a separate input for each record. For example, if you have decision inputs for `Units Ordered` and `Location of Sale`, an input displays for each record.

Outputs


Output	Description
Decision answer record	Record that was created after the decision inputs were evaluated.

Example: Use make a decision flow logic to determine insurance coverage

Execution details

The Flow execution details tab provides runtime information about the flow logic.

The header shows the state, start time, and runtime for the flow logic.
The action shows details about the decision table configuration and inputs.
Each possible answer for the decision table is represented as a branch. The state field indicates whether the branch was evaluated and the evaluation result. This section also displays details about the actions that are taken within a branch. Branches that evaluate to true are highlighted in green.

How search works:

Topics are ranked in search results by how closely they match your search terms

Make a decision flow logic

Make a decision flow logic

Inputs

Outputs

Example: Use make a decision flow logic to determine insurance coverage

Execution details

On this page

Make a decision flow logic

Make a decision flow logic

Inputs

Outputs

Example: Use make a decision flow logic to determine insurance coverage

Execution details

Log in to personalize your search results and subscribe to topics