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":1410,"date":"2020-10-05T22:59:00","date_gmt":"2020-10-05T22:59:00","guid":{"rendered":"http:\/\/www.salesforcenextgen.com\/?p=1410"},"modified":"2020-12-28T19:32:08","modified_gmt":"2020-12-28T19:32:08","slug":"send-custom-notification-using-a-process-builder","status":"publish","type":"post","link":"https:\/\/salesforcenextgen.com\/send-custom-notification-using-a-process-builder\/","title":{"rendered":"Send Custom Notification using a Process Builder"},"content":{"rendered":"\n

Similar to sending an Email alert, salesforce provides another way to notify its user in its own platform. Suppose there is a business process where you do not want to send an email,but instead you want to send them a notification on desktop\/Mobile. For this, Salesforce has provided a tool which is custom notification. <\/p>\n\n\n\n

Custom notification can be automated to send to the intended user\/group using process builder, for that you would have to do the following. <\/p>\n\n\n\n

  1. Create a Custom Notification in Salesforce.<\/li>
  2. Create a process which sends the notification.<\/li><\/ol>\n\n\n\n

    To create a custom notification you have to do the following. <\/p>\n\n\n\n

    1. Click on the Gear icon on the right hand top corner and click on setup<\/li>
    2. Type Custom notifications in the quick find box and click on custom notification<\/li><\/ol>\n\n\n\n
      \"\"\/<\/figure>\n\n\n\n
      1. Click on the new button and fill in the information given below.
        1. Custom Notification Name: Opportunity Closed Lost<\/li>
        2. API Name: Opportunity_Closed_Lost<\/li>
        3. Desktop: checked<\/li>
        4. Mobile: checked<\/li><\/ol><\/li><\/ol>\n\n\n\n
          \"\"\/<\/figure>\n\n\n\n
          1. Click on save<\/li><\/ol>\n\n\n\n

            You have now created a custom notification that you can be used in the process builder.<\/p>\n\n\n\n

            To trigger this notification we now need to create a process builder and define a criteria i.e when to send this notification to the intended user. In our case we would use an existing process builder that we have used to send an email alert. <\/p>\n\n\n\n

            1. Click on the gear icon on the top right hand corner and click on setup.<\/li>
            2. Type process builder in the quick find box and click on the process builder. <\/li>
            3. Select the previously created process: \u2018 Opportunity won\u2019<\/li>
            4. Click on clone and enter the description: \u2018Custom notification on closed lost\u2019 and click on save. This will make a new version of the existing process and you can activate and deactivate older versions of the process if required. <\/li><\/ol>\n\n\n\n
              \"\"\/<\/figure>\n\n\n\n
              1. Click on the next Criteria node and Define the Criteria with the following details.
                1. Criteria Name: Opportunity Closed Lost<\/li>
                2. Criteria for Executing Actions: Conditions are met<\/li>
                3. Set Considitions: 
                  1. Field = stage<\/li>
                  2. Operator = Equals<\/li>
                  3. Type = Picklist<\/li>
                  4. Value = Closed Lost<\/li><\/ol><\/li><\/ol><\/li><\/ol>\n\n\n\n
                    \"\"\/<\/figure>\n\n\n\n
                    \"\"\/<\/figure>\n\n\n\n
                    1. Select Conditions:  All of the conditions are met (AND)<\/li>
                    2. Click on save.<\/li><\/ol>\n\n\n\n
                      \"\"\/<\/figure>\n\n\n\n
                      1.  After saving the Criteria, click on the immediate action and select Action type:Send Custom Notification<\/li>
                      2. Enter the following details in the action.
                        1. Action Name: Account Owner Notified<\/li>
                        2. Notification Type: Opportunity Closed Lost<\/li>
                        3. Notification Recipient: Owner >[Opportunity].Account.OwnerId<\/li>
                        4. Notification Title: {![Opportunity].Account.Name}<\/li>
                        5. Notification Body: <\/li><\/ol><\/li><\/ol>\n\n\n\n

                          Opportunity with Account {![Opportunity].Account.Name} was closed lost<\/p>\n\n\n\n

                          Amount: {![Opportunity].Amount}<\/p>\n\n\n\n

                          1. Target Object:  Opportunity Object that started the process.<\/li><\/ol>\n\n\n\n
                            \"\"\/<\/figure>\n\n\n\n
                            1. Click on save <\/li>
                            2. Activate the process by clicking on the activate button.<\/li><\/ol>\n\n\n\n

                              Below are the test result <\/p>\n\n\n\n

                              When an Opportunity is closed lost, the account owner receives a notification.<\/p>\n\n\n\n

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

                              Below is the Notification body.<\/p>\n\n\n\n

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

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

                              Similar to sending an Email alert, salesforce provides another way to notify its user in its own platform. Suppose there is a business process where you do not want to send an email,but instead you want to send them a notification on desktop\/Mobile. For this, Salesforce has provided a tool which is custom notification.  Custom …
                              Continue reading Send Custom Notification using a Process Builder<\/span><\/a><\/p>\n","protected":false},"author":1,"featured_media":1411,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[391],"tags":[419,412,411,414,420,422,421,417,418,416,415],"_links":{"self":[{"href":"https:\/\/salesforcenextgen.com\/wp-json\/wp\/v2\/posts\/1410"}],"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=1410"}],"version-history":[{"count":2,"href":"https:\/\/salesforcenextgen.com\/wp-json\/wp\/v2\/posts\/1410\/revisions"}],"predecessor-version":[{"id":2164,"href":"https:\/\/salesforcenextgen.com\/wp-json\/wp\/v2\/posts\/1410\/revisions\/2164"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/salesforcenextgen.com\/wp-json\/wp\/v2\/media\/1411"}],"wp:attachment":[{"href":"https:\/\/salesforcenextgen.com\/wp-json\/wp\/v2\/media?parent=1410"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/salesforcenextgen.com\/wp-json\/wp\/v2\/categories?post=1410"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/salesforcenextgen.com\/wp-json\/wp\/v2\/tags?post=1410"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}