Skip to content

Conga Composer

samanthashain edited this page Apr 15, 2022 · 2 revisions

Basics

App Name: Conga Composer

Link to Download: https://appexchange.salesforce.com/appxListingDetail?listingId=a0N300000016b7FEAQ

Cost: $20/user/month

Nonprofit discount?: Yes

Ease of use: Complex to get started, but with very powerful outcomes

Support responsiveness: Medium/poor - used to be fantastic, hopefully they will improve again

Ability to handle bulk merges: Yes, but in some cases you need to use a different product (Conga Batch) which is costly. There are workarounds available in a feature called Global Merge (which is complementary (free) with Conga Composer.

Overall statement of functionality:

Conga Composer is a powerful mail merge "document automation" suite. The way it works is combining a series of queries (in a language called SOQL, similar to Salesforce report filters) with a template where the data from the queries will show up based on your design specifications. Templates can be in almost any format (Word, Powerpoint, Excel, etc) and can be customized with a variety of "parameters" (ie document output name, file storage location, ability to update fields in SF, save as PDF, send to Docusign, etc). Templates are stored in SF as an attachment to a custom record. The whole "solution" sits in a custom Button which can be added to any record page. Salesforce users click the button to initiate the merge action.

Unpacking the "anatomy" of a Conga Composer solution

Read on Conga's Documentation site

What is a Conga Composer Solution (philosophically)

In order to make the magic of mail merge come alive with Salesforce and Conga Composer, you need a way to gather data (to be merged), templates (to merge into), a button (to start the process), and some special instructions (e.g. download format). It's convenient to keep all of these pieces in the same place, so that you don't have to reset them every time you do a merge. A Conga Composer Solution is what we call the unique combination of elements that makes a specific merge work.

Each "Solution" represents a different Mail Merge output. So, you might have;

  • one Solution for donation receipts,
  • another Solution for envelope labels, and
  • another Solution for tax letters (etc etc etc!)

The sky's the limit!

You can think of a Solution as all of the technical instructions for whatever you pick up from your printer tray when your merge is complete.

What is a Conga Composer Solution (technologically)

In it's simplest form, a Solution is code that is executed from a button on a Salesforce object. Yep, a plain, old button!

At some point along the way, the folks at Conga made it easier to create solutions. Instead of going to the button and adding/removing bits of code, they created a page where we can click buttons to add specific details to a Solution-in-progress. This is called the Solution Manager and it's made life so much easier for admins of Conga Composer!

A Conga Solution consists of the following elements:

  • A Button (unless the solution is a Global Merge, but we'll cover those elsewhere)
  • Conga code snippet
  • At least one SOQL query to gather data into the solution
  • At least one template (technically optional, but if you don't do this, you'll always need to upload fresh ones)
  • Parameters (optional) - very useful for customizing download behavior and other custom aspects