5 Customizations Every New Conga Admin Should Know

Subscribe to Our Blog

Get weekly updates
straight to your inbox

Submit your email address to subscribe.

By submitting this form you confirm that you agree to the storing and processing of your personal data by Conga as described in our Privacy Statement.

Greetings from a new Conganeer! Since joining the Conga team I have gained an incredible amount of knowledge about this innovative tool, and have had fun along the way. On my first day of Conga University, I was overwhelmed by how many ways there were to build Conga Composer buttons – but I am here to tell you it’s not as scary as it first seems. Despite having zero developer or coding experience, I found that the Conga parameters are indeed easy to comprehend and fascinating in how they customize and predefine certain behaviors. The quirky parameters are actually the coolest part about Conga; they give admins an incredible amount of opportunities to modify, alter and adapt their Conga solutions.

My advice? Start small. Below are the five parameters that every new Conga admin should know. Once you’ve mastered these you can explore additional ways to customize your solutions. You can find detailed information on how to use these in the Conga Composer Configuration Guide.

1. &SC1

Saving a copy of your output document is usually a smart move and can be enabled with this parameter. The available locations to store your copy are Attachments, Content, Chatter, SpringCM and Google Drive. Though a generally basic parameter, SC1 is crucial for keeping organized and authenticating the documents, presentations and reports you create. So by entering &SC1=Attachments, for example, this says “Conga, save a copy of my document in the Notes and Attachments section of the record.”

A helpful hint for us newbies: &SC1 requires &SC0. In other words &SC0=1 turns on &SC1. Make sense?

2. &OFN

Your output file should have a name, shouldn’t it? This parameter is great not only because it gives the ability to assign names, but also allows you to make the name dynamic by using merge fields. For example, the parameter value could be &OFN={!Account.Name}+Quote. What’s really cool is that you can include specific items such as “Quote” or today’s date after the name. The plus signs tell Conga to put a space in the file same. So if a user runs a Composer solution with &OFN={!Account.Name}+Quote from the ABC Corp record, the resulting file name would appear as ABC Corp Quote. Pretty neat!

3. &DS7

When you click on a Composer button, you typically land on a screen that gives you a variety of options (i.e. picking a template, enabling activity logging, previewing the document, etc.). DS7, aka “background mode”, allows you to bypass that screen. This makes the process much easier and more efficient for the end user. It’s similar to ordering a sandwich at Jimmy Johns – instead of saying “I’d like a sandwich with ham, cheese, some mayo – and oh! Could you hold the bread? I’d like it just on lettuce because I’m watching my figure,” you could simply say “I’d like the Unwich,” which is a premade, bread-free sandwich. Background mode eliminates extra steps and generates the document for end users faster.

4. &DC

DC stands for “disable Conga.” Now, why would you want to do that? Let’s say you don’t want your users to be able to send out quotes if they gave the customer a large discount. You can use DC to tell Conga “when a user clicks the Quote button, make sure the field discount doesn’t exceed 18%. If it does exceed 18%, don’t let the user generate the quote.” If certain criteria are not met, DC allows you to automatically shut off the Conga button.

When the value of the DC parameter is 1 Composer won’t run, and when the value is 0 Composer will run. However, you wouldn’t want DC to always equal 1 because then no one would be able to use Composer.  Therefore, the value of the DC parameter is typically determined by an “IF statement” structure, meaning that whether DC equals 0 or 1 is dependent on what the IF statement returns. An example would be DC={!IF(Opportunity.StageName = “Closed Won”, “0”, “1”) }. That parameter value is a bit frightening, so let’s break it down. In this example, if the Opportunity Stage is “Closed Won,” then DC=0, and Composer will be enabled. If the Opportunity Stage is anything other than “Closed Won,” then DC=1, and Composer will be disabled. Get it?

5. &MFTS

This parameter tells Conga to update the value of up to three fields. For example, the Opportunity record contains a field called “Stage.” MFTS allows you to say to Conga “after I click my ‘Send Quote’ Composer button, go and change the value of the “Stage” field to “Closed Unacknowledged.” This saves the end user time when updating a field because it now updates automatically. To do this you need two parameters – one to tell Composer which field to update and a second to tell Composer what the new value would be. For my example, it would look like:



You could also consider using the updated fields to activate Salesforce Workflow Rules. Pretty fancy!


Leave a Reply

Your email address will not be published. Required fields are marked *