When a record is saved in salesforce with insert, update or upsert statement, salesforce performs below event in sequence behind the scene.
- Runs Client side validations: The browser runs javascript to check if there is any dependent picklist field is present. If yes then it prompts user to fill the value or throws error on UI.
- Loading/Initializing: Loads the original record from the database or initializes the record for an upsert statement.
- Loads the new record field values from the request and overwrites the old values: Say Account’s shipping address is being changed from Pune to Mumbai, then Pune is retrieved from database and its overwritten with value Mumbai
- Executes all before triggers.
- Runs most system validation steps again: Such as verifying that all required fields have a non-null value, and runs any user-defined validation rules(Say Account’s billing country can’t be left blank).
- Execute Duplicate rules: Duplicate rules are implemented to reduce the potential insertion of Account with the same name.
- Saves the record to the database, but doesn’t commit yet: Soft save, not available for SOQL yet.
- Executes all after triggers.
- Executes assignment rules: Assignment rule is created on Case and Lead object. An assignment rule dictates to whom a lead or case is assigned based on criteria that is specified within Salesforce.
- Execute auto-response rules: An auto-response rule is a set of conditions for sending automatic email responses to lead or case submissions based on the attributes of the submitted record.
- Executes workflow rules: Workflow lets you automate standard internal procedures and processes to save time across your org. A workflow rule is the main container for a set of workflow instructions. These instructions can always be summed up in an if/then statement.
- If there are workflow field updates, updates the record 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, duplicate rules, and escalation rules are not run again.
- Executes processes and flows launched via processes and flow trigger workflow actions.
- Executes escalation rules: are used to escalate cases automatically when they meet the criteria which are defined in rule entry. We create rule entries where criteria is defined to escalate a case.
- 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.
- Executes Criteria Based Sharing evaluation.
- Commits all DML operations: Here the record will be actually saved to database and the transaction will complete.
- Executes post logic: Once the record is saved to database, some post logic will be performed like sending mail to customers, updating a formula field etc
It?s hard to find knowledgeable people on this topic, but you sound like you know what you?re talking about! Thanks
Subscription Enabled! you can subscribe now!!
This is the right blog for anyone who wants to find out about this topic. You realize so much its almost hard to argue with you (not that I actually would want?HaHa). You definitely put a new spin on a topic thats been written about for years. Great stuff, just great!
Hello! I just would like to give a huge thumbs up for the great info you have here on this post. I will be coming back to your blog for more soon.
Subscription Enabled! you can subscribe now!!