Skip to main content

Automatically adding user into Chatter group using Process Builder

I am looking for solution to automatically add user to Chatter group and found this interesting solution using Flow Trigger and Workflow rule.However I am not able to implement it because Flow Trigger is pilot feature not GA feature.If I really want it, I can just call Salesforce Support to enable it but I m kinda of lazy.

But I just tweak this solution by using Process Builder.I think the solution is available out there but let me just update mine.

Please vote for this idea : Automatically add individuals to Chatter Group upon provisioning new user

If you are enabling namespace you might face this issue : Workflow Action Failed to Trigger Flow when triggering Flow created after enabling a namespace , and this solution might not work for you.

Step 1 : Create a Chatter Group
Step 2: Create custom field datatype checkbox in User object.
This is depending on how you want to implement logic to add user.In my case, if this               checkbox is false it will add user to the group.My custom field name is 'Sales Info Center Group'.

Step 3 : Create Flow
  • Create a variable to receive user id parameter.

  • Drag a Record Create to the Canvas
    • At the Assignment > Create > Standard>CollaborationGroupMember
    • At field choose Standard > CollaborationGroupId > and also add another field MemberId which is referring to the variable UserId that you created just now.The click OK.
  • Set Element as Start Element by clicking the green icon on Record Create 

  • Save your flow and activate it.

Step 4:Create Process Builder

  • Choose User object, for my case I start the process when a record is created or edited.
  • Add criteria like below .My condition is if user is Active and Sales Info Center Group is true.Save

  • I add two action , first it will call the Flow that we created previously.Second, it will update checkbox field to true like picture below.Don't forget to save your Process Builder and activate it.
Step 5: Testing

Choose one active user, update the record.Check out the group member.

Share with me if you have any idea or comment.Thanks.


Popular posts from this blog

Search Solution Basics

When is it a good time to create a customized search solution? You're developing an external knowledge base for user support. You're in the mood for a fun Friday night. The sales reps just started using the Sales Cloud in Lightning Experience. You want to put your company branding in the search bar. What differentiates SOSL from SOQL? Syntax SOSL searches the search index instead of the org database. SOSL searches more efficiently when you don't know in which object the data resides. All of the above. SOSL works with: REST only SOAP only REST, SOAP, and Apex SOQL only What does a search for a single object look like in SOSL? FIND {cloud} RETURNING Account FIND in ACCOUNT RETURNING "cloud" FIND "cloud" in ACCOUNT FIND (cloud) RIGHT NOW! What does a search for multiple objects look like in SOSL? FIND {sneakers} RETURNING ALL ARTICLES FIND {sneakers} in ALL OBJECTS FIND {sneakers} RETURNING Product2, Content

Process Builder is not fired when field update is called from Approval Process

Scenario In Final Approvals section ; in Approval Process we have field update to update Status field. In Process Builder , we have some action that need to be done when Status field is updated in Approval Process.However this process builder is not fired. Solution To handle this, in Field Update in Approval Process , check Re-evaluated Workflow Rules after Field Change as picture below. What happen if field updated from Approval Process. Workflow - does not fires untill Re-evaluate workflow checkbox is ticked on your field update Process Builder - does not fires untill Re-evaluate workflow checkbox is ticked on your field update Trigger - will fire if conditions are matched This is explained in article here  . Field Updates That Re-evaluate Workflow Rules If  Re-evaluate Workflow Rules After Field Change  is enabled for a field update action, Salesforce  re-evaluates all workflow rules on the object if the field update results in a change to the value of the fi

Tips and Tricks : Test class for Invocable method

Issue : I got 100% coverage in my sandbox but when run validation for deployment it returns 0% coverage It turn out that in my sandbox, I am depending on Process Builder to Invocable Apex class, as long I manipulate test data that fire Process Builder it will call Invocable class. This is not useful when deploying it to Production although it gets deployed together with Process Builder. The correct way is to direct call Invocable method inside test class itself. Example of class : 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 global class MyCustomObject_StatusUpdate_Util { @InvocableMethod ( label = ' Update Quote Status ' ) public static void updateQuote ( Request [] requests ) { Set < Id > setOppId = new Set < Id >(); List < SBQQ__Quote__c > listQuoteToUpdate = new List < SBQQ__Quote__c >(); for ( Request request : requests ) {