LEARN. PRACTICE. GROW.Concept and mechanism
A formula computes a result from reference values and has a return type. It should not be confused with a snapshot of the moment approval occurred. If the current rate can change, evidence of the approved rate needs its own persistence. Choose return type by contract: an eligibility decision can be a Boolean represented by Checkbox, avoiding textual translations as logic. Roll-up summaries combine an operation, a field, and filters over eligible details. COUNT does not replace SUM of amounts, and hiding cancelled details on a layout does not automatically exclude them from an unfiltered aggregate.
Guided application
A validation rule returns true for the state that should block saving. Translating the business rule into a condition table helps avoid OR where AND was needed and recognizes legitimate exceptions. Test allowed and rejected cases, including boundaries and combinations with an approved exception. Fixing only an operator without rereading requirements can retain another error. Editing authorization must also be addressed through field-level security and effective grants; a validation message is not a complete access model. During business review, distinguish calculated values, preserved evidence, who may change source data, and which states must be rejected.
Justification is required for urgent requests without an approved exception. The invalid condition combines urgency, missing justification, and absence of exception. Checking all eight Boolean combinations helps identify wrongful blocks and excessive permission to maintain the exception.
Common pitfalls
Formula treated as immutable history; true treated as valid state in a validation rule; OR used for simultaneous requirements; layout treated as field security.
Related topics: Requirements, access, and platform extensions · Relationships, lifecycle, and reporting · Fields, migrations, and external data
Model calculation, persistence, validation, and access separately. Demonstrate logic using expected outcomes.
Reference: Validation Rules · Platform App Builder guide SU 26