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":1414,"date":"2020-10-05T23:07:52","date_gmt":"2020-10-05T23:07:52","guid":{"rendered":"http:\/\/www.salesforcenextgen.com\/?p=1414"},"modified":"2020-12-28T19:31:56","modified_gmt":"2020-12-28T19:31:56","slug":"post-to-chatter-using-process-builder","status":"publish","type":"post","link":"https:\/\/salesforcenextgen.com\/post-to-chatter-using-process-builder\/","title":{"rendered":"Post to Chatter using Process Builder"},"content":{"rendered":"\n

To post chatter, your organization needs to have chatter enabled in the environment. Once it is enabled this action can be used to post on the chatter, the feed will appear as soon as the user who started the process, by creating or editing the record. <\/p>\n\n\n\n

The feed can be posted on user\u2019s feed, to a group in chatter or the record\u2019s feed that started the process. <\/p>\n\n\n\n

To post to the user\u2019s chatter feed we have to do the following. <\/p>\n\n\n\n

For this example we will use the process builder that we previously created : Opportunity won<\/p>\n\n\n\n

  1. Clone the existing Process and create a new version.<\/li>
  2. On the First Criteria node \u2018Opportunity Won\u2019, click on the \u2018+ Add Action\u2019 button. <\/li>
  3. Select Post to chatter as the action type.<\/li>
  4. Define the Name of the Action :\u2019Post to User\u2019<\/li>
  5. In the picklist \u2018Post To\u2019 select: User<\/li><\/ol>\n\n\n\n
    \"\"\/<\/figure>\n\n\n\n
    1. Then use the selection to define which user should the feed be posted to, in this case we chose the user Id of the last ,modified by user. <\/li>
    2. Fill out the message body that you want to post to the feed, here you can also use the merge field to display value from the record that is getting created or edited.<\/li><\/ol>\n\n\n\n
      \"\"\/<\/figure>\n\n\n\n
      1. Once the above changes are made, then save the action and activate the process builder. <\/li>
      2. Below is the feed on the user\u2019s page. <\/li><\/ol>\n\n\n\n
        \"\"\/<\/figure>\n\n\n\n

        To Post to a chatter group, you have to select the Chatter group in the Post TO selection picklist and do the same as above. <\/p>\n\n\n\n

        To Post to a records feed you have to below. <\/p>\n\n\n\n

        1. Clone the existing Process and create a new version.<\/li>
        2. On the First Criteria node \u2018Opportunity Won\u2019, click on the \u2018+ Add Action\u2019 button. <\/li>
        3. Select Post to chatter as the action type.<\/li>
        4. Define the Name of the Action :\u2019Post to User\u2019<\/li>
        5. In the picklist \u2018Post To\u2019 select: This Record<\/li>
        6. Then next all you have to do is define the body of the feed. <\/li>
        7. The overall action should look as below. <\/li><\/ol>\n\n\n\n
          \"\"\/<\/figure>\n\n\n\n
          1. Below is how the feed appears on the record\u2019s page. <\/li><\/ol>\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":"

            To post chatter, your organization needs to have chatter enabled in the environment. Once it is enabled this action can be used to post on the chatter, the feed will appear as soon as the user who started the process, by creating or editing the record.  The feed can be posted on user\u2019s feed, to …
            Continue reading Post to Chatter using Process Builder<\/span><\/a><\/p>\n","protected":false},"author":1,"featured_media":1415,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[391],"tags":[426,427,428,425,424,423,429],"_links":{"self":[{"href":"https:\/\/salesforcenextgen.com\/wp-json\/wp\/v2\/posts\/1414"}],"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=1414"}],"version-history":[{"count":2,"href":"https:\/\/salesforcenextgen.com\/wp-json\/wp\/v2\/posts\/1414\/revisions"}],"predecessor-version":[{"id":2162,"href":"https:\/\/salesforcenextgen.com\/wp-json\/wp\/v2\/posts\/1414\/revisions\/2162"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/salesforcenextgen.com\/wp-json\/wp\/v2\/media\/1415"}],"wp:attachment":[{"href":"https:\/\/salesforcenextgen.com\/wp-json\/wp\/v2\/media?parent=1414"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/salesforcenextgen.com\/wp-json\/wp\/v2\/categories?post=1414"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/salesforcenextgen.com\/wp-json\/wp\/v2\/tags?post=1414"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}