When a customer support agent updates a Case record, several automated processes and validation mechanisms are triggered. Place the following automation events in the exact sequence in which Salesforce processes them during the record save operation.
- 1Before-Save Record-Triggered Flows update field values on the record.
- 2Custom Validation Rules evaluate field criteria against current values.
- 3Case Assignment Rules evaluate criteria to reassign record ownership.
- 4After-Save Record-Triggered Flows process post-save logic and related record updates.
- 5Parent record Roll-Up Summary fields are recalculated.
Answer
The correct order of execution is: 1) Before-Save Record-Triggered Flows, 2) Custom Validation Rules, 3) Case Assignment Rules, 4) After-Save Record-Triggered Flows, 5) Parent record Roll-Up Summary updates.
Salesforce processes save operations in a strict sequence: Before-Save Record-Triggered Flows execute first, followed by Custom Validation Rules. After the initial database save, Case Assignment Rules execute, followed by After-Save Record-Triggered Flows. Finally, parent record Roll-Up Summary fields are recalculated near the end of the transaction.
Step-by-Step Solution
Key Concept
Salesforce Order of Execution during record save operations