Order Of Execution in Salesforce related Scenarios

Question

Accepted Answer

Order of execution in Salesforce determines the sequence in which various operations are performed.

The order of execution is as follows: Validation rules, before triggers, after triggers, assignment rules, auto-response rules, workflow rules, processes, escalation rules, and finally, the commit.
Validation rules are checked first to ensure data integrity.
Before triggers are executed before the record is saved to the database.
After triggers are executed after the record is saved to the database.
Assignment rules determine the owner of the record.
Auto-response rules send automatic email responses.
Workflow rules automate standard internal procedures and processes.
Processes are similar to workflow rules but with additional capabilities.
Escalation rules escalate records to a higher level of support.
Finally, the commit saves the record to the database.

Accepted Answer

A Salesforce, this is the order in which actions execute:

System Validation Rules.
Apex Before Triggers.
Custom Validation Rules.
Duplicate Rules.
Apex After Triggers.
Assignment Rules.
Auto-Response Rules.
Workflow Rules.

Accepted Answer

The original record is loaded from the database.

System Validation Rules.

Executes all before triggers.

Custom Validation rules.

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 the record was updated with workflow field updates, fires before and after triggers one more time. 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.

Executes entitlement rules.

If the record contains a roll-up summary field or is part of a cross-object workflow, perform calculations and updates the roll-up summary field in the parent record. The parent record goes through the 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 the save procedure.

Executes Criteria Based Sharing evaluation.

Commits all DML operations to the database.

Executes post-commit logic, such as sending an email.

Order Of Execution in Salesforce related Scenarios

Top IBM Package Consultant interview questions & answers

Top HR questions asked in IBM Package Consultant