5 Parameters to Pump Up Your Proposal Solution

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.

Looking to take your proposal solution to the next level? Why not combine multiple templates into a single output? Or throw in further automation with background mode? Check out this post for parameters that can add some more pizzazz to your proposal solution.

Select multiple templates

Maybe you would like to feature a couple of new products in your proposals, but the products don’t always apply to every prospect every time. In some situations, both products should be included, sometimes only one product should be included, and other times none of the additional products should be included. So what to do when creating your proposals? Rather than maintaining multiple versions of the template to satisfy the different scenarios, you could break up the proposal templates into pieces. Each new product could be featured in its own document. Then use a Composer parameter to select multiple templates. How do we do this?



Additional steps:

If you break up your proposal template into pieces, you’ll need to create a new Conga Template record for each “piece” of the template and upload the document template(s).

select 10 templates


When users go to select multiple templates in the Composer dialog box, you can narrow down the list of templates they choose from by adding another parameter (&TemplateGroup) and making slight modifications to the related Conga Template records.


For each Conga Template you want displayed in the Composer dialog box, you will need to add a value to the Template Group field on the Conga Template record.

CMT 00003


If you split up your template into separate pieces, what if you could stitch all of the separate pieces together? No problem. Throw in an additional parameter (&AWD for Word documents and &APF for PowerPoint documents).


This results in one single Word document for the final output with a new page section break between document files. Each document template starts on a new page in the final output.


This option results in one single Word document for the final output as well, but with a continuous section break between document files. Each document template begins immediately following the end of the prior document template.


This results in a single PowerPoint document for the final output.

Automatic dynamic template selection

Do you have multiple versions of your proposal template? Maybe customers of a certain size or type receive proposal template A and customers of another size or type need to receive proposal template B. Wish Composer would select the appropriate template by default for the end user? No problem. Let’s take a look at what you’ll need.



Additional steps:

Create a formula field with an IF statement and reference that field in the button/link URL.

End result:


Create a single click solution

Save your users additional time and selections by implementing background mode. If you have a proposal broken into multiple templates, users don’t need to worry about selecting the correct templates to combine. Users simply click the Composer button/link and bypass the Composer dialog box. Predefine the proposal template and choose from a variety of options for background mode behavior – attach the document to the record, automatically email the document, etc. You’ll need just the one parameter listed below.



Additional steps:

Depending on the desired background mode behavior, additional prerequisites may need to be met. See this article for a complete list of all background mode options and the corresponding parameter value.

End result:

Ex: &DS7=3 (Setting the parameter equal to a value of “3” will instruct Conga to merge the document and prompt the end user to download the merged document after he/she clicks the Composer button/link )


Add an additional parameter (&BML) to display a message in the Background Mode dialog box.


This will display the message, “Proposal for NAME_OF_RELATED_ACCOUNT” in the Background Mode dialog box.

LW Dentistry

Save a copy

Keep track of when proposals were sent, what content was included, and who generated the proposal by saving a copy of the merged proposal document. So where can you save your proposal? Choose from Notes & Attachments, Chatter, Content, Google Drive or SpringCM. To save a copy, you’ll actually need two parameters.




Additional steps:

Be certain your end users have access to the location where the copies of the proposal will be saved (Content, Google Drive, etc.).

End result:

&SC0=1 (This parameter turns on the ability to save a copy of the merged document)

&SC1=Chatter (Setting this parameter equal to a value of “Chatter” will instruct Conga to save a copy of the merged document in Chatter. This article defines the other value options for &SC1.)

Customize the document output name

Quickly identify the date the proposal was generated and the related account or some other naming convention by incorporating the output file name parameter in your solution. By default (on standard objects), Composer appends the record name to the name of your template when generating the merged output. So, if your template is named “Proposal – May2015” and you are on an opportunity titled, “Addt’l Licenses” the final merged document will be named “Proposal – May2015 – Addt’l Licenses.” To customize this behavior, add in the parameter below and you’re all set!


&OFN=[desired file name]

Additional steps:

Be sure to exclude symbols unsupported in file names and keep in mind the limit of 245 characters. To create a literal space in the output file name, use a plus sign (+).

End result:

&OFN= Proposal+for+{!Opportunity.Account}+-+{!TODAY()} (This results in an output file name of “Proposal for ACCOUNTNAME – TODAY’SDATE”)


Let us know what parameters you include in your proposal solution!


Leave a Reply

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