12 - Order of Execution

Order 

(Hint : Execution can restart for few records at few points . For more check : Reference - 166 / U /SDC)

In Salesforce, the order of execution is important as it determines how records are processed and what actions are performed in response to different types of operations (insert, update, delete, etc.). Here’s a summary of the main steps in Salesforce's order of execution:

  1. System Validation Rules: Salesforce verifies that required fields have non-null values and that field formats are valid.

  2. Before Triggers: Executes "before" triggers, which allow you to set or modify values before the record is saved.

  3. System Validation Rules Again: Runs custom validation rules if the record is modified by a before trigger.

  4. Duplicate Rules: Checks for duplicates based on configured duplicate rules.

  5. Save Record (But Not Committed): Saves the record to the database but does not commit.

  6. After Triggers: Executes "after" triggers, which allow for actions based on record values after they have been saved.

  7. Assignment Rules: Runs assignment rules if they are defined (only for leads and cases).

  8. Auto-Response Rules: Executes auto-response rules (only for leads and cases).

  9. Workflow Rules: Evaluates and executes any workflow rules that meet criteria. If workflow rules modify fields, before and after triggers are re-evaluated.

  10. Processes: Executes process builder flows, which may update fields or trigger other actions.

  11. Escalation Rules: Escalates cases if any escalation rules are configured.

  12. Entitlement Rules: Applies any entitlement rules if configured (only for cases).

  13. Roll-Up Summary Fields: Updates roll-up summary fields if the current record impacts any roll-ups.

  14. Parent Roll-Up Summary Fields: Updates roll-up summary fields on parent records if needed.

  15. Criteria-Based Sharing: Evaluates and applies criteria-based sharing rules.

  16. Commit: Finally, Salesforce commits the record to the database.

  17. Post-Commit Logic:

    • After Commit Actions: Executes actions that require a committed record, such as sending emails, firing platform events, and performing post-commit operations.

Understanding these steps is crucial for preventing recursion and managing performance when developing in Salesforce.







Comments

Post a Comment

Popular posts from this blog

API Names in Salesforce

 In Salesforce, an API Name is a unique identifier for metadata components like fields, objects, or custom settings that enables external systems, scripts, and integrations to reference Salesforce data programmatically. The API name remains consistent, even if the label displayed in the user interface changes, making it essential for maintaining integration stability. Key Characteristics of API Names Field and Object API Names : Standard object and field API names generally mirror their label names, but with spaces removed. Custom fields and objects have the suffix __c , denoting them as custom. Example: A custom object called "Project" would have an API name of Project__c . A custom field called "Start Date" on the Project object would have an API name of Start_Date__c . Case-Sensitivity : API names in Salesforce are case-sensitive , so it’s essential to match them exactly when using them in code or integrations. Usage : API names are used in SOQL queries, Apex co...
Read more

18 - LWC - BEST PRACTICES - For accessing HTML elements and their values in JavaScript

 In Lightning Web Components (LWC) , best practices for accessing HTML elements and their values in JavaScript involve using template.querySelector , template.querySelectorAll , and data-* attributes. Here’s a guide to help you follow these best practices effectively: 1. Use template.querySelector and template.querySelectorAll Since IDs can be unpredictable in LWC , the template.querySelector method is generally preferred. You can use CSS selectors , including class names, tag names, and data-* attributes, to locate elements. html Copy code <!-- template.html --> < lightning-input class = "my-input" data-id = "specialInput" value = "Sample Value" > </ lightning-input > javascript Copy code // component.js // Accessing the element const inputElement = this . template . querySelector ( '.my-input' ); // Getting the value const inputValue = inputElement. value ; 2. Use data-* Attributes for Specific Identifiers For ele...
Read more

6 - Object Relationships (Lookup and Master-Detail and Junction Objects)

 Here's a tabular comparison of the Lookup and Master-Detail relationship types in Salesforce: Feature Lookup Relationship Master-Detail Relationship Definition and Usage Loosely coupled; records are linked but can exist independently Tightly coupled; child record depends on the parent for existence Data Integrity and Ownership Child record does not inherit parent’s sharing or ownership Child inherits sharing, permissions, and ownership from the parent Roll-up Summary Fields Not available Available; aggregates values from child to parent Required Field Optional; child can exist without a parent Required; child must have a parent Cascade Delete Optional (not automatic) Automatic; deleting parent deletes all related child records Security and Access Child has independent sharing settings Child inherits sharing settings from the parent Hierarchy Depth Flexible; supports multi-level relationships Limited to strict parent-child hierarchy with up to two relationships This structure pro...
Read more