Triggers and Order of Execution

  1. Loads the original record from the database or initializes the record for an upsert
  2. Loads the new record field values from the request and overwrites the old values.Database.com doesn’t perform system validation in this step when the request comes from other sources, such as an Apex application or a Web services API call.
  3. Executes all before
  4. Runs most system validation steps again, such as verifying that all required fields have a non-nullvalue, and runs any user-defined validation rules. The only system validation that Database.com doesn’t run a second time (when the request comes from a standard UI edit page) is the enforcement of layout-specific rules.
  5. Saves the record to the database, but doesn’t commit yet.
  6. Executes all after
  7. Executes assignment rules.
  8. Executes auto-response rules.
  9. Executes workflow rules.
  10. If there are workflow field updates, updates the record again.
  11. If the record was updated with workflow field updates, fires beforeand after triggers one more time (and only one more time), in addition to standard validations. Custom validation rules are not run again.Note
  12. 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.
  13. If the parent record is updated, and a grand-parent 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. Grand-parent record goes through save procedure.
  14. Executes Criteria Based Sharing evaluation.
  15. Commits all DML operations to the database.
  16. Executes post-commit logic, such as sending email.
Print Friendly, PDF & Email
This entry was posted in Development and tagged . Bookmark the permalink.