Deprecated: Optional parameter $list declared before required parameter $is_script is implicitly treated as a required parameter in /home1/oijoiv2f/public_html/wp-content/plugins/apus-framework/libs/redux/ReduxCore/inc/class.redux_cdn.php on line 21

Deprecated: Optional parameter $register declared before required parameter $footer_or_media is implicitly treated as a required parameter in /home1/oijoiv2f/public_html/wp-content/plugins/apus-framework/libs/redux/ReduxCore/inc/class.redux_cdn.php on line 45

Deprecated: Optional parameter $register declared before required parameter $footer_or_media is implicitly treated as a required parameter in /home1/oijoiv2f/public_html/wp-content/plugins/apus-framework/libs/redux/ReduxCore/inc/class.redux_cdn.php on line 104

Deprecated: Optional parameter $expire declared before required parameter $path is implicitly treated as a required parameter in /home1/oijoiv2f/public_html/wp-content/plugins/apus-framework/libs/redux/ReduxCore/inc/class.redux_functions.php on line 54

Deprecated: Optional parameter $depth declared before required parameter $output is implicitly treated as a required parameter in /home1/oijoiv2f/public_html/wp-content/themes/entaro/inc/classes/megamenu.php on line 155

Deprecated: Optional parameter $depth declared before required parameter $output is implicitly treated as a required parameter in /home1/oijoiv2f/public_html/wp-content/themes/entaro/inc/classes/mobilemenu.php on line 147

Deprecated: Optional parameter $args declared before required parameter $wp_customize is implicitly treated as a required parameter in /home1/oijoiv2f/public_html/wp-content/plugins/apus-framework/libs/redux/ReduxCore/inc/extensions/customizer/extension_customizer.php on line 583

Deprecated: Optional parameter $args declared before required parameter $wp_customize is implicitly treated as a required parameter in /home1/oijoiv2f/public_html/wp-content/plugins/apus-framework/libs/redux/ReduxCore/inc/extensions/customizer/extension_customizer.php on line 606

Warning: Cannot modify header information - headers already sent by (output started at /home1/oijoiv2f/public_html/wp-content/plugins/apus-framework/libs/redux/ReduxCore/inc/class.redux_cdn.php:21) in /home1/oijoiv2f/public_html/wp-includes/rest-api/class-wp-rest-server.php on line 1831

Warning: Cannot modify header information - headers already sent by (output started at /home1/oijoiv2f/public_html/wp-content/plugins/apus-framework/libs/redux/ReduxCore/inc/class.redux_cdn.php:21) in /home1/oijoiv2f/public_html/wp-includes/rest-api/class-wp-rest-server.php on line 1831

Warning: Cannot modify header information - headers already sent by (output started at /home1/oijoiv2f/public_html/wp-content/plugins/apus-framework/libs/redux/ReduxCore/inc/class.redux_cdn.php:21) in /home1/oijoiv2f/public_html/wp-includes/rest-api/class-wp-rest-server.php on line 1831

Warning: Cannot modify header information - headers already sent by (output started at /home1/oijoiv2f/public_html/wp-content/plugins/apus-framework/libs/redux/ReduxCore/inc/class.redux_cdn.php:21) in /home1/oijoiv2f/public_html/wp-includes/rest-api/class-wp-rest-server.php on line 1831

Warning: Cannot modify header information - headers already sent by (output started at /home1/oijoiv2f/public_html/wp-content/plugins/apus-framework/libs/redux/ReduxCore/inc/class.redux_cdn.php:21) in /home1/oijoiv2f/public_html/wp-includes/rest-api/class-wp-rest-server.php on line 1831

Warning: Cannot modify header information - headers already sent by (output started at /home1/oijoiv2f/public_html/wp-content/plugins/apus-framework/libs/redux/ReduxCore/inc/class.redux_cdn.php:21) in /home1/oijoiv2f/public_html/wp-includes/rest-api/class-wp-rest-server.php on line 1831

Warning: Cannot modify header information - headers already sent by (output started at /home1/oijoiv2f/public_html/wp-content/plugins/apus-framework/libs/redux/ReduxCore/inc/class.redux_cdn.php:21) in /home1/oijoiv2f/public_html/wp-includes/rest-api/class-wp-rest-server.php on line 1831

Warning: Cannot modify header information - headers already sent by (output started at /home1/oijoiv2f/public_html/wp-content/plugins/apus-framework/libs/redux/ReduxCore/inc/class.redux_cdn.php:21) in /home1/oijoiv2f/public_html/wp-includes/rest-api/class-wp-rest-server.php on line 1831
{"id":1375,"date":"2020-10-05T15:05:14","date_gmt":"2020-10-05T15:05:14","guid":{"rendered":"http:\/\/www.salesforcenextgen.com\/?p=1375"},"modified":"2020-12-28T19:31:55","modified_gmt":"2020-12-28T19:31:55","slug":"send-email-using-lightning-process-builder","status":"publish","type":"post","link":"https:\/\/salesforcenextgen.com\/send-email-using-lightning-process-builder\/","title":{"rendered":"Send Email Using Lightning Process Builder"},"content":{"rendered":"\n

Your Business has a process that when an opportunity is won, an email has to be sent to the account owner. You want to automate this process and reduce one redundant task from your executives. To Automate this requirement you would do the following. <\/p>\n\n\n\n

To Send an email from process builder you need the following components to work together<\/p>\n\n\n\n

  1. An email template – (This has to be done in Salesforce classic)<\/li>
  2. An Email Alert <\/li>
  3. A Process Builder<\/li><\/ol>\n\n\n\n

    To create an email template, switch Salesforce Classic if you are in lightning experience. <\/p>\n\n\n\n

    1. Click on setup<\/li>
    2. Type \u2018Email Template\u2019 in quick find\/search and click on \u2018Classic Email Template\u2019<\/li><\/ol>\n\n\n\n
      \"\"\/<\/figure><\/div>\n\n\n\n
      1. There are 4 types of email template type but for this scenario we will select \u2018Text\u2019.<\/li><\/ol>\n\n\n\n
        \"\"\/<\/figure><\/div>\n\n\n\n
        1. On the new email template page, you will see two sections. Top section, where you can find the merge fields of the related record and Email template information where you can enter the below information.<\/li>
        2. Folder – Unified public Classic Email Template<\/li>
        3. Available for use : checked<\/strong><\/li>
        4. Email Template name: AccountOwner<\/li>
        5. Template Unique Name: AccountOwner<\/li>
        6. Encoding: General US & Western Europe (iso-8859-1 iso-latin-1)<\/li>
        7. Description: (optional)<\/li>
        8. Subject: Opportunity Closed Won for Account: {!Account.Name}<\/li>
        9. Email Body: <\/li><\/ol>\n\n\n\n

          Hi {!Account.OwnerFullName}<\/p>\n\n\n\n

          Congratulations, we have just won an opportunity for the Account: {!Account.Name}<\/p>\n\n\n\n

          Please Follow the next steps in the process.<\/p>\n\n\n\n

          Regards<\/p>\n\n\n\n

          As shown in the image below<\/p>\n\n\n\n

          \"\"\/<\/figure><\/div>\n\n\n\n

          Create An Email Alert<\/h2>\n\n\n\n

          Next in the process we need to create an Email Alert, which we can call from the process builder.<\/p>\n\n\n\n

          For this do the following steps. <\/p>\n\n\n\n

          1. Click on setup <\/li>
          2. Type Email Alert in the quick find\/ Search. And click on Email Alert<\/li><\/ol>\n\n\n\n
            \"\"\/<\/figure><\/div>\n\n\n\n
            1. Click on the new email alert button on the email alert list view screen.<\/li><\/ol>\n\n\n\n
              \"\"\/<\/figure>\n\n\n\n
              1. On the new email alert page enter the below information.
                1. Description: Send Email to Account Owner of Opportunity<\/li>
                2. Unique Name: Send_Email_to_Account_Owner_of_Opportunity<\/li>
                3. Object: Opportunity<\/li>
                4. Email Template: AccountOwner<\/li>
                5. Recipient type: Account Owner and from recipient select Account Owner<\/li>
                6. From Email Address. <\/li>
                7. Additional Email: Leave this blank<\/li><\/ol><\/li><\/ol>\n\n\n\n
                  \"\"\/<\/figure>\n\n\n\n
                  1. Click save<\/li><\/ol>\n\n\n\n

                    Until now you have made an email template and an email alert. Now it’s time to wire these two individual components to a process which will trigger it on the required event. <\/p>\n\n\n\n

                    Create Process<\/h2>\n\n\n\n

                    To create a process builder, switch to lightning experience and follow these steps. <\/p>\n\n\n\n

                    1. Click on the gear icon on the right hand top corner and click on setup. <\/li>
                    2. Then in quick find box type process builder and click on process builder. <\/li>
                    3. Click on the new button and fill out the new process details as below. 
                      1. Process name: Opportunity won<\/li>
                      2. API Name: Opportunity_won<\/li>
                      3. The process starts when* : A record changes<\/li><\/ol><\/li>
                      4. Click on save<\/li><\/ol>\n\n\n\n
                        \"\"\/<\/figure>\n\n\n\n
                        1. Click on the object button to select the object on which you want this process to be triggered. In this case we select Opportunity and select option when a record is created or edited. <\/li><\/ol>\n\n\n\n
                          \"\"\/<\/figure>\n\n\n\n
                          1. Next you will click on criteria and define the condition when you want to execute this process. Give criteria name: Opportunity Closed Won, and select the criteria for executing Actions, there are three options, in this case select Conditions are met. <\/li>
                          2. Next you define the set conditions. This is where our business logic will come into the picture, we want to send an email to the account owner when the opportunity reaches the stage closed won. For this select the field for the criteria by clicking on the field text box, this will open another modal box, in this modal box type \u2018stage\u2019 and select stage. <\/li><\/ol>\n\n\n\n
                            \"\"\/<\/figure>\n\n\n\n
                            1. Set operator : Equals and type: Picklist , these values will come by default but if not then select what is mentioned. <\/li>
                            2. Select value : closed won <\/li>
                            3. In conditions let the option All of the conditions are met (AND) selected. <\/li><\/ol>\n\n\n\n
                              \"\"\/<\/figure>\n\n\n\n
                              1. Click on save.<\/li>
                              2. Now click on the immediate action next to the criteria node you just created and select email alert from the Action Type picklist. <\/li>
                              3. Set Action Name: Send Email to Account Owner<\/li>
                              4. Find the Email alert that you created earlier using the unique name: Send_Email_to_Account_Owner_of_Opportunity<\/li>
                              5. Click on save <\/li><\/ol>\n\n\n\n
                                \"\"\/<\/figure>\n\n\n\n
                                1. Click on the Activate button to activate the process. <\/li><\/ol>\n\n\n\n

                                  Consideration:<\/p>\n\n\n\n

                                  1. Email template, available for use checkbox should be checked to use the email template<\/li>
                                  2. Object select in Email Alert should be the same on which the process is created, in this case both were on opportunity. <\/li><\/ol>\n\n\n\n

                                    For More Examples refer : Automate you Business Process<\/a><\/strong><\/p>\n","protected":false},"excerpt":{"rendered":"

                                    Your Business has a process that when an opportunity is won, an email has to be sent to the account owner. You want to automate this process and reduce one redundant task from your executives. To Automate this requirement you would do the following.  To Send an email from process builder you need the following …
                                    Continue reading Send Email Using Lightning Process Builder<\/span><\/a><\/p>\n","protected":false},"author":1,"featured_media":1380,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[391],"tags":[401,402,392,398,395,403,399,404,400,405],"_links":{"self":[{"href":"https:\/\/salesforcenextgen.com\/wp-json\/wp\/v2\/posts\/1375"}],"collection":[{"href":"https:\/\/salesforcenextgen.com\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/salesforcenextgen.com\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/salesforcenextgen.com\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/salesforcenextgen.com\/wp-json\/wp\/v2\/comments?post=1375"}],"version-history":[{"count":4,"href":"https:\/\/salesforcenextgen.com\/wp-json\/wp\/v2\/posts\/1375\/revisions"}],"predecessor-version":[{"id":2163,"href":"https:\/\/salesforcenextgen.com\/wp-json\/wp\/v2\/posts\/1375\/revisions\/2163"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/salesforcenextgen.com\/wp-json\/wp\/v2\/media\/1380"}],"wp:attachment":[{"href":"https:\/\/salesforcenextgen.com\/wp-json\/wp\/v2\/media?parent=1375"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/salesforcenextgen.com\/wp-json\/wp\/v2\/categories?post=1375"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/salesforcenextgen.com\/wp-json\/wp\/v2\/tags?post=1375"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}