• #43357
     Anjali #23

    How are lead assignment rules executed in Salesforce?

    How are lead assignment rules executed?



    Hi Anjali,

    Lead assignment rules allow us to automatically assign Leads to the appropriate queue or user. A Lead assignment rule consists of multiple rule entries that define the conditions and order for assigning cases. From a Salesforce User interface, a user can trigger assignment rules by simply checking the Assign using active assignment rules checkbox under the optional section. The problem arises when you need to insert or update the Leads from Process Builder and wants to trigger assignment rules. Using the Process Builder, a Lead will be inserted or updated but assignment rule will not be triggered as there is no check box to use the organization’s assignment rule or a prompt to assign using the active assignment rule.

    Salesforce | Vince Vince #225

    Dear all on this post,

    Often overlooked is the need to create a “catchall” step after activating an assignment rule (either Lead or Case) meant to address records that may escape the criteria mentioned in your rules. If not, the default Lead or Case Owner (both in Setup) will be assigned. This Default Owner often ends up being the first user created on the org.

    Just a handy insight from previous experience.

     William #1

    Lead Assignment Rules – An assignment rule dictates to users or queues is assigned based on criteria that are specified within Salesforce. Lead they are created manually, captured from the web, or imported via the lead import wizards.

    To set up a lead assignment rule, navigate to Set Up -> Build -> Leads -> Assignment Rules, and click “New.” Enter a descriptive Rule Name, check “Active,” and click “Save.”

    Salesforce | Jade Jade #2

    Hi Anjali,

    Now you should be able to understand that how lead assignment rules work in Salesforce.

    Let us understand that when lead assignment rules get executed in Salesforce :

    1. The original record is loaded from the database (or initialized for an insert statement)
      2. The new record field values are loaded from the request and overwrite the old values
      3. All before triggers execute (TRIGGERS)
      4. System validation occurs, such as verifying that all required fields have a non-null value, and running any user-defined validation rules (VALIDATIONS)
      5. The record is saved to the database, but not yet committed
      6. All after triggers execute
      7. Assignment rules execute
      8. Auto-response rules execute
      9. Workflow rules execute (WORKFLOW)
      10. If there are workflow field updates, the record is updated again
      11. If the record was updated with workflow field updates, before and after triggers fire one more time (and only one more time)
      12. Escalation rules execute
      13. All DML operations are committed to the database
      14. Post-commit logic executes, such as sending email


Viewing 5 posts - 1 through 5 (of 5 total)

Please to reply to this topic.


We're not around right now. But you can send us an email and we'll get back to you, asap.


About Us

Forcetalks is a Salesforce collaboration platform for coders & developers, geeks & nerds, consultants & business heads, admins & architects, managers & marketers and of course the business owners. A community where you can learn from, where you can contribute to. For you. For Salesforce. Read More...

Copyright 2019 Forcetalks. All Right Reserved.

Log in with your credentials


Forgot your details?