Blog post

Triggers,Workflow and Order of Execution in Salesforce

Posted on Dec 13, 2014
by Pradip Shukla
in Technology
with 0 comments

When you save a record with an insertupdate, or upsert statement, Salesforce performs the following events in order.Note
Before Salesforce executes these events on the server, the browser runs JavaScript validation if the record contains any dependent picklist fields. The validation limits each dependent picklist field to its available values. No other validation occurs on the client side.
On the server, Salesforce:
  1. Loads the original record from the database or initializes the record for an upsert statement.
  2. Loads the new record field values from the request and overwrites the old values.
    If the request came from a standard UI edit page, Salesforce runs system validation to check the record for:
    • Compliance with layout-specific rules
    • Required values at the layout level and field-definition level
    • Valid field formats
    • Maximum field length
    Salesforce doesn't perform system validation in this step when the request comes from other sources, such as an Apex application or a SOAP API call.

    Salesforce runs user-defined validation rules if multiline items were created, such as quote line items and opportunity line items.

  3. Executes all before triggers.
  4. 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. The only system validation that Salesforce doesn't run a second time (when the request comes from a standard UI edit page) is the enforcement of layout-specific rules.
  5. Executes duplicate rules, which is currently available as a beta feature. If the duplicate rule identifies the record as a duplicate and uses the block action, the record is not saved and no further steps, such as aftertriggers and workflow rules, are taken.
  6. Saves the record to the database, but doesn't commit yet.
  7. Executes all after triggers.
  8. Executes assignment rules.
  9. Executes auto-response rules.
  10. Executes workflow rules.
  11. If there are workflow field updates, updates the record again.
  12. If workflow field updates introduced new duplicate field values, executes duplicate rules again.
  13. 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.
  14. Executes processes.

    Processes are currently available through a private beta program. For information on enabling this feature in your organization, contact Salesforce.

    If there are workflow flow triggers, executes the flows.

    Flow trigger workflow actions, formerly available in a pilot program, have been superseded by the Process Builder. Organizations that are using flow trigger workflow actions may continue to create and edit them, but flow trigger workflow actions aren’t available for new organizations. For information on enabling the Process Builder (beta) in your organization, contact Salesforce.

  15. Executes escalation rules.
  16. Executes entitlement rules.
  17. 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.
  18. 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.
  19. Executes Criteria Based Sharing evaluation.
  20. Commits all DML operations to the database.
  21. Executes post-commit logic, such as sending email.
Note
During a recursive save, Salesforce skips steps 8 (assignment rules) through 18 (roll-up summary field in the grandparent record).

Additional Considerations

Please note the following when working with triggers.

  • The order of execution isn’t guaranteed when having multiple triggers for the same object due to the same event. For example, if you have two before insert triggers for Case, and a new Case record is inserted that fires the two triggers, the order in which these triggers fire isn’t guaranteed.
  • When a DML call is made with partial success allowed, up to three attempts can be made to save the records. Triggers are fired during the first attempt and are re-fired during subsequent attempts. DML calls allow partial success when you set the allOrNone parameter of a Database DML method to false or when you call the SOAP API with default settings. For more details, see Bulk DML Exception Handling.
  • When Enable Validation and Triggers from Lead Convert is selected, if the lead conversion creates an opportunity and the opportunity has Apex before triggers associated with it, the triggers run immediately after the opportunity is created, before the opportunity contact role is created. For more information, see “Customizing Lead Settings” in the Salesforce online help.
  • If you are using before triggers to set Stage and Forecast Category for an opportunity record, the behavior is as follows:
    • If you set Stage and Forecast Category, the opportunity record contains those exact values.
    • If you set Stage but not Forecast Category, the Forecast Category value on the opportunity record defaults to the one associated with trigger Stage.
    • If you reset Stage to a value specified in an API call or incoming from the user interface, the Forecast Category value should also come from the API call or user interface. If no value for Forecast Category is specified and the incoming Stage is different than the trigger Stage, the Forecast Category defaults to the one associated with trigger Stage. If the trigger Stage and incoming Stage are the same, the Forecast Category is not defaulted.
  • If you are cloning an opportunity with products, the following events occur in order:
    1. The parent opportunity is saved according to the list of events shown above.
    2. The opportunity products are saved according to the list of events shown above.
    Note
    If errors occur on an opportunity product, you must return to the opportunity and fix the errors before cloning. s

    If any opportunity products contain unique custom fields, you must null them out before cloning the opportunity.

  • Trigger.old contains a version of the objects before the specific update that fired the trigger. However, there is an exception. When a record is updated and subsequently triggers a workflow rule field update,Trigger.old in the last update trigger won’t contain the version of the object immediately prior to the workflow update, but the object before the initial update was made. For example, suppose an existing record has a number field with an initial value of 1. A user updates this field to 10, and a workflow rule field update fires and increments it to 11. In the update trigger that fires after the workflow field update, the field value of the object obtained from Trigger.old is the original value of 1, rather than 10, as would typically be the case.


0

Leave your comment

Leave your comment