--- title: Make a decision flow logic description: 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. locale: en-US canonical_url: https://www.servicenow.com/docs/r/australia/build-workflows/workflow-studio/flow-logic-make-decision.html release: australia product: Workflow Studio classification: workflow-studio topic_type: concept last_updated: "2026-03-12" reading_time_minutes: 7 breadcrumb: [Flow logic, Flows, subflows, and actions reference, Flows, subflows, and actions, Workflow Studio, Build workflows] --- # 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 decision table answer produces a separate branch path within your flow. Decision tables accept any number of inputs and support any number of decisions. You can configure the Make a decision flow logic to return a single or multiple answers and to display the answers as branch paths or record data pills. For more information on decision tables, see [Exploring decision tables](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/build-workflows/workflow-studio/decision-designer-overview.md). **Note:** - When the **Use Branches** check box is cleared, the Make a decision data pills in other flow components is supported only if there are no branches. - The Make a decision data pill can be used in the answer branches only when the **Use Branches** check box is selected. - When you set a data pill value from inside an answer branch of Make a decision flow logic, the data pill value is only available to other actions in the same branch. Referencing a data pill value that was set inside an answer branch from outside of the flow logic branch produces a null value. ## 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. To create a new decision table, select the create new record icon \(\[Omitted image "add-record-button.png"\] Alt text: Create new record icon\). |
| Execution | Decision answers you want the flow to run. - **First decision that matches**: Run only the first matching decision answer. This option produces these outputs. - Answer record - Answer table - **Run all decisions that match**: Run all matching decision answers. This option produces these outputs. - Answer table - Ordered IDs - Answer records - Count **Note:** Set the **Use Branches** option to specify how your flow displays matching decision answers. |
| Use Branches | Option to display each possible decision answer in its own branch flow logic block. Use the branch flow logic block to specify what content to run where the condition matches a specific decision table answer. Each branch flow logic block is equivalent to an If flow logic block for each answer. Disable branches when you want to return one or more answer records instead of branch flow logic blocks. **Warning:** When you clear and confirm the **Use Branches** option, your flow removes the flow logic blocks for each branch and removes the **Include Otherwise** check box. Reselecting the **Use Branches** check box does not restore any removed branch flow logic blocks. |
| Include Otherwise | Option to add the **otherwise** branch to the list of available answers. This option is only available when **Use Branches** is selected. You can use this branch to specify the actions and subflows to run when the decision table does not generate an answer. An Otherwise branch is equivalent to an Else flow logic block. **Note:** If you specify a decision table default answer, this branch will never run because the decision table always selects an answer. |
| Decision table inputs | List of Decision Input \[sys\_decision\_input\] records that are associated with your decision table. Your flow 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. |