---
sourceDocument: Yokohama Build workflows
sourceDocumentLink: https://www.servicenow.com/docs/r/yokohama/build-workflows
Release :
- yokohama
ft:locale :
- en-US
ft:publication_title :
- Yokohama Build workflows
ft:clusterId :
- crworkflow
bundleId :
- crworkflow
workflow :
- Creator
---
# Make a decision flow logic
# Make a decision flow logic {#ariaid-title1}
* Release version: Yokohama
*
* Updated January 30, 2025
*
*  4 minutes to read
Summarize
 Summarized using AI
This content was generated using new OpenAI-powered functionality. Results are provided on an as is basis and are not guaranteed to be accurate or complete.
## Summary of Make a decision flow logic
The Make a decision flow logic in ServiceNow enables you to implement multiple conditional paths within a flow by using an external decision table.
This approach serves as a more readable and maintainable alternative to nested If, Else If, or Else statements, especially when dealing with complex decision criteria.
For example, you can determine the appropriate car insurance coverage by inputting factors like age, accident history, and car model into a decision table, which then guides the flow through different branches based on the decision outcomes.
Show full answer Show less
## Key Features
* **Decision Table Integration:** Requires an external decision table that defines inputs and possible answers, allowing any number of inputs and decisions.
* **Branching Options:** You can configure the flow to use branches, where each decision answer creates a separate branch in the flow, or to return the answers as data pills without branching.
* **Execution Modes:** Choose to run either the first matching decision answer or all matching answers, which affects outputs and flow behavior.
* **Data Pills and Scope:** Data pill values set inside an answer branch are only accessible within that branch; referencing them outside returns null.
* **Include Otherwise Branch:** When branches are enabled, you can add an "Otherwise" branch to handle cases where no decision table answers match, similar to an Else condition.
* **Decision Table Inputs:** The flow dynamically displays input parameters based on the decision table configuration, which can be populated manually or via data pills.
* **Execution Details:** Runtime information shows flow logic state, inputs, and branch evaluation results, highlighting which branches executed successfully.
## Practical Use and Considerations
This flow logic is ideal for scenarios requiring complex decision-making with multiple conditions and outcomes, such as determining insurance coverage levels based on several criteria. By using decision tables, you gain a clear, maintainable structure and can easily extend or modify decision criteria without altering flow logic.
When enabling branches, each decision answer gets its own flow branch, allowing tailored actions per outcome. Disabling branches returns answers as data pills, useful when you want to process results collectively rather than separately. Be aware that turning off branches removes existing branch logic and cannot be undone automatically.
Remember that data pills set within branches are confined to those branches; to share data across the flow, set values outside branch scopes or design accordingly.
## Outputs and Integration
* **Answer Table:** Contains records matching decision answers.
* **Ordered IDs:** Provides a sorted list of answer record IDs when running all matching decisions without branches, useful for iterating with other flow logic.
* **Answer Records:** Returns either a single record or multiple records depending on execution mode.
* **Count:** Shows the number of matched answers when running all matches.
## Next Steps
To implement this logic, create or select an appropriate decision table reflecting your decision criteria, configure inputs accordingly, and decide on branching options based on how you want to handle the results in your flow. Use the flow execution details to monitor and troubleshoot decision logic during runtime.
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://www.servicenow.com/docs/hu20dfMCOswADYr5EA9HFA "Decision tables in Workflow Studio enable developers to decouple decision logic from their code by creating and maintaining decision rules.").
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.
{#flow-logic-make-decision__ul_l31_pjp_3mb}
## Inputs {#flow-logic-make-decision__section_k2q_fhm_r2b}
{#flow-logic-make-decision__table_m3l_b5l_p2b__entry__2}
| 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 (![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 {#flow-logic-make-decision__ul_p4s_ndr_bpb} * Run all decisions that match: Run all matching decision answers. This option produces these outputs. * Answer table * Ordered IDs * Answer records * Count {#flow-logic-make-decision__ul_gb4_xdr_bpb} {#flow-logic-make-decision__ul_h4r_mdf_ffb} 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. |
[ ]
{#flow-logic-make-decision__table_m3l_b5l_p2b}
## Outputs {#flow-logic-make-decision__section_yzd_hg5_w2b}
{#flow-logic-make-decision__table_oy4_hdy_1fb__entry__3}
| Field | Description | Data Type |
|-|-|-|
| Answer table | Table containing the answer records. Each decision \[sys_decision_question\] table record refers to a matching answer record. | Table Name |
| Ordered IDs | List of matching answer record sys_id values generated by the decision table. Your flow only generates this output when the Use Branches option is false and the Execution option is Run all decisions that match. You can use this output as the input for a For Each flow logic block or a Look Up Record action. Your flow sorts the list by the Order value listed in the Decision \[sys_decision_question\] table. | List |
| Answer records | Answer records returned by the decision table. Returns a single record when Execution is First decision that matches. Returns a list of records when Execution is Run all decisions that match. | Record or Records |
| Count | The number of answer records returned by the decision table. Only displayed when Execution is Run all decisions that match. | Integer |
[ ]
{#flow-logic-make-decision__table_oy4_hdy_1fb}
## 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. These inputs can be entered manually, or by dragging data pills into the inputs from the data panel on the right side of the screen. Below this section, the branches
for each answer are shown in the decision table.
## Execution details {#flow-logic-make-decision__section_pqc_2qt_w2b}
Figure 1. Make a decision flow execution details
The Flow execution details tab provides runtime information about the flow logic.
1. The header shows the state, start time, and runtime for the flow logic.
2. The action shows details about the decision table configuration and inputs.
3. 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.
{#flow-logic-make-decision__ol_wtt_scs_r2b}
**Related concepts**
* [Assign subflow outputs flow logic](https://www.servicenow.com/docs/BPYImTV9HJoIPPnwGPh~fg "Specify the data the subflow returns when it completes running. Use subflow output as data for a parent flow or as input for another process.")
* [Call a workflow flow logic](https://www.servicenow.com/docs/qZcmPZCegzFAHnd31j7heA "Run a published and active workflow from your flow. You can use the flow data as a workflow input. For example, you can specify the current record as a workflow input.")
* [Do the following until flow logic](https://www.servicenow.com/docs/eSbS7MMbSBu30a8dSjMBng "Apply one or more actions repeatedly until an end condition is met. You can use the flow data to specify the end conditions.")
* [Do the following in parallel flow logic](https://www.servicenow.com/docs/7PJmWFojwFDIqu9dkF7_lw "Run actions and subflows in separate paths within an isolated flow logic block.")
* [Dynamic flows flow logic](https://www.servicenow.com/docs/ubno_xW91uUeFZuVIQaySg "Identify and run a flow or subflow dynamically by using runtime data. Build templates to provide expected inputs for dynamically called flows or subflows.")
* [End Flow flow logic](https://www.servicenow.com/docs/Sp7jPg4NNYSwqRP8XOZouA "Stop running the current flow. Use End Flow within a branch of the flow to specify an exit condition. For example, end the flow when it reaches a specific If flow logic block.")
* [For Each flow logic](https://www.servicenow.com/docs/sXDICSCto7~hbNZyHxR6lQ "Apply one or more actions to each record in a list of records.")
* [If flow logic](https://www.servicenow.com/docs/TjnRtaiEgKxX4PD0DUqfcA "Selectively apply one or more actions only when a list of conditions is met.")
* [Set Flow Variables flow logic](https://www.servicenow.com/docs/~PbDvIgeB82CFqu~11nGvQ "Assign a value to one or more flow variables, which store flow data as data pills. Access flow variable values by referring to their data pill.")
* [Try flow logic](https://www.servicenow.com/docs/bmLWueso8VCOr_035PJQKg "Allow a flow to continue running when an error occurs within a flow logic block. Run a sequence of actions in response to errors within the flow logic block.")
* [Wait for a duration flow logic](https://www.servicenow.com/docs/ucONIbAnUeCKaCUOpk~Hlw "Use this flow logic to give your users time to act during automated processes or to wait for a specific date and time to complete actions.")
**Related reference**
* [Exit Loop flow logic](https://www.servicenow.com/docs/9FuSmMLS5Ub2t8ypV_xJOQ "Exit from a flow logic loop when the conditions of an If flow logic are met. Continue running the flow from the next step after the flow logic loop. This flow logic is also known as break.")
* [Get Flow Outputs flow logic](https://www.servicenow.com/docs/AmvE1SZ0P8d_clYXtrrUgw "Retrieve output values generated by dynamic flows or subflows.")
* [Go back to flow logic](https://www.servicenow.com/docs/bhUS9xEo2lNvyY9~JY5mqA "Return to a prior step in the flow to repeat a sequence of actions.")
* [Skip Iteration flow logic](https://www.servicenow.com/docs/F2ltfoIaBnP~iH3UFz9hiw "Skip the current iteration of a flow logic loop when the conditions of an If flow logic are met. Continue running the flow logic loop with the next item in the list. This flow logic is also known as continue.")