Storing Merge
Templates
Release 8
This template guide is an overview of how to use Conga Workflow to automate Conga Composer® solutions.
Contact Support: support@congamerge.com
Americas EMEA APAC
(866) 502-3334 (toll free) +44 20 3608 0165 +61 28 417 2399
Contents
General Disclaimer ... 3
Upgrading from Conga Composer Release 7? ... 4
Storing Merge Templates... 4
Conga Template Manager ... 4
To create a Conga Template Record: ... 5
Salesforce Mail Merge Template Repository... 6
Your local drive or network directory ... 8
General Disclaimer
Conga Composer solutions depend on and leverage technology from a multitude of software and hardware vendors including but not limited to salesforce.com, Microsoft, Google, and the providers of various Internet browsers (“Third Party Technology”). Output from Conga
Composer solutions can be impacted by these and numerous other factors beyond the control of Conga, including:
• Template design errors in Microsoft Word, Excel, PowerPoint templates, PDF Forms or Conga HTML email templates
• The nature and scope of data and/or images being retrieved for merging into templates • Individual user’s browser, network, ISP and/or hardware settings (see Conga Composer
Installation and Administration Guide for additional details)
• The use of any encryption gateways or appliances that require any re-direct of Conga Composer traffic
• The availability and performance of the salesforce.com service and other software-as-a-service solutions such as eSignature, eCommerce and other AppExchange products, and periodic updates, enhancements or other changes to such services made by their respective vendors
• Salesforce.com security settings including User Profiles and Permissions, folder and object access and field-level security
• Internet performance, regional and even global outages
For these reasons, Conga cannot guarantee that your particular implementation of Third Party Technology and Conga technologies – even if configured based on Conga
documentation and/or guidance offered by Conga Support personnel – will perform consistent with your expectations or requirements, or provide the output you require. Accordingly, Conga disclaims any and all liability resulting from, or related to,
performance issues associated with Conga products to the extent arising from your implementation, configuration, or the behavior of Third Party Technology.
508 Compliance
Conga Composer is an installable package from the Salesforce AppExchange, which integrates with an individual customer's existing implementation of Salesforce. When properly configured, Conga Composer will run within an existing Salesforce instance without the need to view, manipulate or configure the application outside of the Salesforce user interface.
The use of Conga solutions is entirely represented by standard Salesforce user interface components when properly configured. Therefore, customers seeking the 508 Compliance VPAT documentation are referred to Salesforce.
Upgrading from Conga Composer Release 7?
While Conga has made every effort to make Conga Composer Release 8 backwards compatible with Conga Composer Release 7, a small number of cases have been reported where the behavior of and/or output from Conga Composer Release 8 varies in content or appearance from Composer Release 7. It is the Customer’s responsibility to thoroughly test all existing solutions with Composer Release 8 to ensure they perform as desired, and to make any necessary adjustments to templates, queries, reports or other components.
Storing Merge Templates
A file-based merge template, regardless of type (Word, Excel, PowerPoint or PDF), may be stored in either of these locations:
• The Conga Template Manager (recommended) • The Salesforce Mail Merge Template Repository • Your local hard drive or network drive
Conga Email Templates must be stored in the: • The Conga Email Template Manager
Conga Template Manager
The Conga Template Manager (“CTM”) is a custom object, included with Conga Composer, in which merge templates can be stored.
The CTM has many advantages: • Attach any kind of
template (Word, Excel, PowerPoint or PDF) without having to alter the file extension • Use Salesforce security
You must enable the Conga Template Manager on the Conga Setup page. Salesforce Setup | View Installed Packages | Configure for Conga Composer.
• Specify up to three fields in Salesforce to update after a merge operation – helpful in advancing a workflow status field
• Change the attachment related to a Template Record, without changing its Salesforce Id, which is beneficial if you’ve referenced the Id in a Conga Composer URL
Access the Template Repository by viewing the Conga Templates tab in Salesforce.
To create a Conga Template Record:
1. Ensure that you’ve enabled the Conga Template Manager on the Setup page (see above) 2. Open the Conga Templates Tab.
3. Click New to start a new Template record 4. Enter a name and description.
5. Click Save.
6. Upload your template by clicking Attach File.
7. If you want to reference this template from a Conga Composer button, copy its Record Id to the clipboard and paste it into a Conga Composer Button URL after the &TemplateId= parameter.
While you can attach multiple files to the Conga Template record under Notes and Attachments – which some customers prefer to keep track of historic versions of the template – Conga Composer will only use the most recent attachment according to the Last Modified Date.
Salesforce Mail Merge Template Repository
The Salesforce Mail Merge Template repository can be found at:
Setup | Administration Setup | Communication Templates | Mail Merge Templates
To load a Word template into this repository, click New Template, enter a descriptive name and attach the file.
To attach an Excel or PDF file, however, you must alter the file extension of your template because the Salesforce repository only allows files that have a “.doc” extension to be uploaded.
• The Communication Templates is enabled by default on the Conga Setup page. • We highly recommend that you enable the Conga Template Manager and
de-activate Communication Templates.
You can work-around the restriction in this way:
1. Start Windows Explorer (right-click My Computer, then choose Explore).
2. In Windows Explorer, disable Hide File Extensions by choosing Tools | Folder Options then View (tab), uncheck Hide extensions for known file types, then OK 3. Rename the template and enter
.doc after its regular extension, resulting in a file that ends in either “.xls.doc” or “.pdf.doc”.
4. Upload the renamed file to the Salesforce repository
Example:
A template named “Quote Template.xls” would become “Quote Template.xls.doc”. A template named “Quote Template.xlsx” would become “Quote Template.xlsx.doc”.
Do not use “.docx” as the faux file extension -- use “.doc”
To re-open the local file, you’ll need to either remove the “.doc” extension or open the backup copy
Your local drive or network directory
You can select a file from your local drive or a network directory.
Conga Email Template Manager
The Conga Email Template Manager custom object is a significant addition to Conga Composer. With this new custom object, you can create Conga Email Templates that work a lot like Conga templates built in Microsoft Word. For more information about designing Conga Email Templates, please see the Template Guide on creating Conga Email Templates.
This option is very convenient particularly when designing Conga Composer templates because you can perform a merge and observe the results. If changes are necessary, tweak the template and save it, then switch back to Conga Composer and click Merge again. You can bypass the tedious operation of uploading the template to the
