Decision Table
A Decision Table is a Business Rules Engine table that maps input conditions to output actions in a structured, spreadsheet-like format.
Definition
A Decision Table is a Business Rules Engine table that maps input conditions to output actions in a structured, spreadsheet-like format. Each row represents a rule that defines what should happen when certain conditions are met, allowing non-developers to configure complex conditional logic without code.
In plain English
“A Decision Table is a way to express business rules in a spreadsheet-like format. Each row says 'when these conditions are true, do this'. Non-developers can configure complex conditional logic by editing rows in a table instead of writing code or building branching flows.”
Worked example
Brookford Insurance uses a Decision Table to encode their pricing-tier rules: rows specify combinations of customer-segment + product-line + region, with each row's output being the applicable discount tier and approval threshold. A business analyst maintains the Decision Table by editing rows in a spreadsheet-like UI (no Apex). When the rules change (say, a new region launches), she adds a row; when a row's conditions are met by an incoming quote, the engine returns the configured outputs. Decision Tables turn what would be a complex Flow with dozens of branches into editable rule rows.
Why Decision Table matters
A Decision Table is a Business Rules Engine feature that maps input conditions to output actions in a structured, table-based format. Each row represents a rule: a set of conditions in the input columns and the corresponding outputs. When the engine evaluates the table at runtime, it finds the row whose conditions match the input data and returns the configured outputs. This format is well-suited for complex conditional logic that would be unwieldy as nested if-statements or branching flows.
Decision Tables are part of Salesforce's Business Rules Engine, which supports declarative business logic for industries like Financial Services Cloud and Health Cloud. The table format makes rules approachable for business analysts and SMEs who don't write code but understand the rules in their domain. Common use cases include eligibility determinations, pricing tiers, routing decisions, and compliance checks. The Business Rules Engine handles execution efficiently and supports versioning, so rule changes can be deployed and audited like any other configuration.
How organizations use Decision Table
Built loan eligibility rules as Decision Tables. Business analysts maintain the rules as new products and policies roll out, without needing developer involvement for every change.
Uses Decision Tables for care pathway routing based on patient conditions and insurance type. Clinical SMEs maintain the logic in a format they can read and edit themselves.
Replaced an Apex-based pricing engine with Decision Tables. The migration cut maintenance time significantly because pricing changes no longer required code deployments.
Test your knowledge
Q1. What is a Decision Table?
Q2. Who is the Decision Table format designed for?
Q3. What are common Decision Table use cases?
Discussion
Loading discussion…