Configure Decision Tables
Updated
This article explains how to access, create, and configure Decision Tables in Sprinklr. Decision Tables help you define reusable business logic in a structured format and apply it consistently across workflows.
Prerequisites and Permissions
Note: Access to this feature is controlled by the dynamic property DECISION_TABLE_ENABLED.
To enable this feature in your environment, contact your Success Manager. Alternatively, you can submit a request at tickets@sprinklr.com.
To access Decision Tables, your administrator must enable the required permissions. You can find these settings at All Settings → User Management → Global Roles. Click the three‑dot menu next to the role and select Edit. Then scroll to the Role Permissions section, expand Decision Table, and enable the permissions.
Permission | Definition |
View | Allows users to view decision tables and review their rules, conditions, and outputs. Users with this permission cannot modify, delete, or manage decision tables. |
Edit | Allows users to create and modify decision tables, including adding, updating, or removing rules, conditions, and outputs. Users can save changes to existing decision tables. |
Delete | Allows users to permanently delete decision tables that are no longer required. Deleted decision tables cannot be used in associated workflows or configurations. |
Access Decision Tables
Click Launchpad
or New Tab . Under Platform Modules, select All Settings within Settings.
From the left pane, select General Settings.
From the left pane, scroll to Decision Tables.
Create a Decision Table
Click Create Decision Table.
Enter a name and an optional description.
Select one or more Custom Entities that provide data for conditions. These entities are used to add fields to the Decision Table.
Save the table.
The Decision Table is created in Draft status. When ready, use the toggle to Publish the Decision Table.
Define Decisions
Conditions columns determine when a decision row matches. Each condition column represents one input that the Decision Table evaluates when it is called from a workflow.
Conditions are typically based on:
Customer attributes
Case fields
Data stored in Custom Entities
Add Condition Columns
Click Add Condition Column.
Select the following:
Entity
Field
Operator (for example, Equals, Greater Than, Contains)
Repeat these steps to add additional condition columns.
Supported field types include String, Number, Boolean, Date/Time, and Lookup.
Example: Condition Columns (Standard Example Used Throughout)
Condition Columns
Lead Stage
Lead Product
Customer Category
Example Rule
If Lead Stage = Work in Progress (WIP), Lead Product = Home Insurance, and Customer Category = Wealth, then return the configured results.
This means the decision row matches only when all three conditions are true.
Define Result Columns
Result columns determine what happens when conditions match.
Add Result Columns
Click Add Result Column.
Select a field or reference (for example, Priority or Team).
(Optional) Define a default value.
Default values are returned when no decision rows match the input conditions.
Example: Using Multiple Entities in Conditions and Results
In this example, the Decision Table evaluates conditions using fields from multiple entities:
Lead Stage
Lead Product
Customer Category
Each condition column references a different entity field. Based on the selected combination of values—WIP, Home Insurance, and Wealth—the Decision Table returns corresponding results such as Priority and Assigned Team.
If none of the condition combinations match, the configured default values in the result columns are applied.
This approach allows you to centralize logic that depends on multiple data sources and return consistent outcomes across workflows.
Default Results
If none of the configured condition combinations match, the Decision Table returns the default values defined in the result columns.
Example default behavior
Priority: Medium
Team: General Insurance
Default results ensure that workflows always receive an output, even when no specific condition is met.
Manage Logic Rows
Each row represents one decision rule.
You can:
Add rows above or below
Duplicate rows
Delete rows
Drag and drop rows to control the evaluation order
Decision rows are evaluated top to bottom, in the order they appear.
Decision Table Output Format
When a Decision Table is evaluated in a workflow, the output includes:
The conditions that were evaluated, and
The result values returned for the matching row (or the default row)
Including both conditions and results makes it easier to understand why a specific outcome was returned and allows workflows or scripts to use whichever part of the output is required.
Example: Default Result Behavior
Lead Stage | Lead Product | Customer Category | Priority (Result) | Team (Result) |
WIP | Home Insurance | Wealth | High | Home_Insurance_HP |
Fresh | Home Insurance | Wealth | High | Home_Insurance_HP |
Default | -- | -- | Medium | General Insurance |
Publish the Decision Table
Decision Tables in Draft status are not usable in workflows.
Click Publish when the configuration is complete.
Published tables become available for use in workflows.
Share Settings
Use Share Settings to control who can access the Decision Table.
Choose whether the Decision Table is visible in all workspaces or only selected workspaces.
Select the users or user groups who can view and use the Decision Table in workflows.
Sharing ensures that only the appropriate teams can access and apply the Decision Table.
