---
sourceDocument: Yokohama Build workflows
sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/yokohama/build-workflows

 Release :

    - yokohama

ft:locale :

    - en-US

ft:publication_title :

    - Yokohama Build workflows

ft:clusterId :

    - crworkflow

bundleId :

    - crworkflow

workflow :

    - Creator


---

# Use decision tables

# Use decision tables {#ariaid-title1}

Release version: Yokohama  
Updated January 30, 2025  
![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 minute to read  
Decision tables built in Workflow Studio are executed in flows with flow logic or in scripts with API calls.

Although decision tables are built in Workflow Studio, the actual execution of the decision takes place in other applications. Keeping decision actions separate from these applications allows the decisions to be reused and called when needed.

## Decision tables in flows {#use-decision-tables__section_vb1_kj1_qyb}

In Workflow Studio, decisions are executed as part of the Make a decision flow logic. For more information, see [Make a decision flow logic](https://servicenow-prod.fluidtopics.net/Jglm9N3IKaFJ1mfoX8SX3Q "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.").

## Decision tables in APIs {#use-decision-tables__section_kj5_lj1_qyb}

In scripts, decision tables are executed using API calls to the decision table with the GetDecision() or GetDecisions() methods from the DecisionTableAPI. For more information, see [DecisionTableAPI - Scoped, Global](https://www.servicenow.com/docs/access?context=DecisionTableAPI&version=yokohama&pubname=yokohama-api-reference&ft:locale=en-US).