Get weekly updates
straight to your inbox
Submit your email address to subscribe.
Chatter is a great Salesforce feature that provides a forum for anyone to share insights and propose new ideas. Teams can connect using Chatter to drive productivity and accelerate innovation, and with Composer you can automatically post your documents and merge activity to Chatter. In order to do so you’ll need to add a few, simple parameters to your Composer solution.
There are two different ways you can set up your solution to post to Chatter depending on how much flexibility you want to give to running users.
1. Save a Copy
The &SC0 parameter arranges the file attachment options for Composer. When a “1” is added after the “=” symbol this tells Composer to “Save a Copy” of the document being generated. The &SC1 parameter directs where the copy of the merged document will be stored. In this case, using “Chatter” as the value tells Composer to store the copy in your Chatter feed. Though the Save a Copy feature is defaulted to Chatter, the end-user still has the option to change where the copy is saved.
The &DS7 parameter,known as Background Mode, lets you bypass the classic Conga Composer dialog. The value of “401” tells Composer to enable Background Mode and automatically post to Chatter. In other words, the end-user of Composer will only have to click once on the Composer button to instantly merge and post the document to Chatter. Unlike the Save a Copy parameter, this option gives the end-user no other choice but to save a copy in Chatter.
Your merged document that is saved to Chatter will look similar to this:
Now employees who follow you in Chatter are able to see what document you merged for which related object, and are able to download the file as a PDF.
Why does it matter?
Anyone following that record will see it in their feed and be able to access the document. This helps enhance communication internally within the company so that employees are able to track activities that are occurring, who is executing them and note what other projects need to be accomplished.
Want to get more advanced?
You can even have Composer post to the parent record. For example, you can have any documents/merge activity post to Chatter from an Opportunity and also have Composer post to the Opportunity’s Account . This parameter gives you that access:
If this parameter is placed before the “Post to Chatter” parameters, it tells Composer to attach the Chatter update to a Parent ID – In this case, to post in the Account record.
This is useful because not only is your activity being documented on Chatter, but it also provides another method to visually track and manage which documents are generated, with the option to open the final document right there at the top of the page.
Check out more about the Attachment Parent ID parameter here, and get more active on Chatter!