Creating Validation Rules
Updated
This article outlines the steps to create Validation Rules.
Accessing the Validation Rules
From the Launchpad, click Sprinklr Service tab, and under Persona App, click Entity Studio. The Entity Manager page appears.
Search for the desired entity for which you want to create validation rule. Click on the 3 dots and then click the View button next to the entity name.
Click Validation Rules from the left pane.
Click on the Create Validation Rule in the top right corner.
You can later enable/disable rules using the toggle in the Validation Rules list.
Form Fields
Name: A clear, action-oriented title (e.g., “Cap Discount for Deals”).
Description: What the rule enforces and why.
Rule Conditions: One or more conditions that must evaluate to true to block the save.
Error Message to be displayed: The error shown to users.
Overrides: Users/Groups/Teams/Roles that bypass the rule.
Building Conditions
Each condition includes:
Where: Choose the field to evaluate.
Function: How to evaluate the field (New Value, Old Value, Is Changed, Is Not Changed).
Operator: Equals, Not Equals, Greater Than, Less Than, Contains, In, etc.
Value: The comparator value(s).
Add multiple conditions with AND/OR logic by using Add Condition and Add Condition Group.
Examples
Example A — Cap Discount for Deals
Goal: If Discount > 20%, block the update.
Conditions
Discount — New Value — Greater Than — 20
Error Message
“Discount cannot exceed 20% for Deals”
Overrides (optional)
Add the “Director of Sales” role to allow exceptions.
Example B — Lock Converted/Rejected Leads
Goal: Once a lead is Converted or Rejected, prevent any further edits.
Conditions
Lead Status — Old Value — In — [Converted, Rejected]
Error Message
“This lead is locked and cannot be modified.”
Notes
Using the Old Value ensures the lock applies after the record reached that status previously.
Example C — Prevent Owner Change in WIP
Goal: When Lead Status is Contacted, the Lead Owner must not change.
Conditions
Lead Status — New Value — Contains — Contacted
AND Lead Owner — Is Changed
Error Message
“Lead Owner cannot be changed while the lead is in Contacted Stage.”
Overrides
Allow Team Leads or Managers to change the owner in exceptional cases.
Example D — Require Updated Approval Comments for “Final Review” Stage
Goal: When moving a Deal to the “Final Review” stage, the user must update the “Approval Comment” field in the same save.
Conditions
Deal Stage — New Value — Equals — Final Review
AND Approval Comments — Is Not Changed
Error Message
“Please update Approval Comments before moving to Final Review.”
For Example, we have built the validation rule that Discount Percentage cannot be greater than 20% for a Lead.
On Consumption, while trying to create/update the Record with Discount Percentage as 21, the error message configured is reflected in the snack bar which is displayed in the following screenshot.
Writing Effective Error Messages
Be specific and actionable.
Mention the exact constraint.
Avoid internal jargon.
Good: “Discount cannot exceed 20% for deals.”
Poor: “Invalid discount.”
Managing and Toggling Rules
After saving, return to the Validation Rules list.
Use the toggle to enable/disable rules without deleting them.
Edit a rule to refine conditions, message, or overrides.