In this session we will talk talk about Order of Execution in Salesforce. Let see why we need to learn about Order of Execution in Salesforce. Clicks-not-code automations make building applications on the Lightning platform fast and easy. But as your org grows and covers increasingly more business processes, robustness, scale and reliability become your key concerns.
In this session, we will guide you through logic flow, or “Save Order of Execution?, the most important factor in designing sustainable and scalable applications . There’s a lot more to know than ‘triggers run before workflows’. Dig deeper, understand the logic flow and your apps will scale better and run more reliably.
Become an Order of Execution hero and walk away with an understanding of how to design robust apps optimized for scale and how to control recursion and remedy typical problems.
Here is some keynote of session
Order of Execution.
When you save a record with an insert, update, or upsert statement, Salesforce performs the following events in order. Here is cheat-sheet of Order of execution.
Order of Execution
- Loads Initial record.
- If the request came from a standard UI edit page, Salesforce runs system validation to check the record for page layout specific rules, field definition, Maximum field length.
- Executes flows that make before-save update. (New Change in Winter 20)
- Executes all before triggers.
- Runs most Custom validation.
- Executes duplicate rules.
- Saves the record to the database, but doesn’t commit yet.
- Executes all after triggers.
- Executes assignment rules.
- Executes auto-response rules.
- Executes workflow rules.
- If there are workflow field updates, updates the record again.
- If workflow field updates introduced new duplicate field values, executes duplicate rules again. If the record was updated with workflow field updates, fires before update triggers and after update triggers one more time (and only one more time), in addition to standard validations. Custom validation rules are not run again.
- Executes processes and flow.
- Executes escalation rules.
- Executes entitlement rules.
- If the record contains a roll-up summary field or is part of a cross-object workflow, performs calculations and updates the roll-up summary field in the parent record. Parent record goes through save procedure.
- If the parent record is updated, and a grandparent record contains a roll-up summary field or is part of a cross-object workflow, performs calculations and updates the roll-up summary field in the grandparent record. Grandparent record goes through save procedure.
- Executes Criteria Based Sharing evaluation.
- Commits all DML operations to the database.
- Executes all after-commit logic, such as sending email.
What is part of the after commit logic?
- All email sends
- Asynchronous Apex: @future methods
- Async Sharing Rule processing (for >25,000 records)
- Outbound Messages placed on queue
- Calculate Index, such as Search Index
- Render File Previews
- Publication of Platform Events (if configured)
- Check documentation with each release.
Understand the fine print.
- Rule of thumb: One trigger, one Process per object.
- Know how to use the Debug Log (or know someone who knows).
- Watch out for “***CLOSE TO LIMIT***” debug log entries.
- Avoid situations that could loop (or know what you are doing).
- Handle trigger.old with care.
- Test, test, test – and remember to test with all packages and enough data
Please note that we have limit of 300 attendees that can join the online sessions. However, recording will be posted on our YouTube channel. Make sure to subscribe our YouTube channel to get notification for video upload.
Bookmarks our “Session in 2020” page for all upcoming and old sessions of 2020. Let us know which topic you want learn next in ApexHours.
Sharing is Caring so Share with your friends
Salesforce Apex Hours