Release 7 - Winter 13

Transcription

1 Conga Conga Composer Configuration Guide Release 7 - Winter 13 Welcome Conga Composer lets you generate documents and spreadsheets by gathering data from Salesforce and merging to a template. The resulting file(s) can be printed or ed and you can log the actions you ve taken in Salesforce. Conga Composer solutions let you create individual documents by clicking a button from a record in Salesforce. Contacting Conga Conga is a leading provider of software solutions to enrich your Salesforce experience, specializing in document creation tools that integrate data from Salesforce. Founded in 2006, Conga has since built a substantial market presence with thousands of customers worldwide. Technical Support At Conga, we are committed to providing you with timely answers to your technical support questions. We provide support to system administrators for our products via or telephone. Generally, we re available weekdays, during the following hours: North America Support Hours: 8 a.m. 8 p.m. Eastern Time Tech Support [email protected] Telephone: or (866) Europe, Middle East, Africa (EMEA) Support Hours: 9 a.m. 5 p.m. British Time Tech Support [email protected] Telephone: Asia / Pacific (APAC) Support Hours: 9 a.m. 5 p.m. Eastern Time Tech Support [email protected] Telephone: Sales For information on other products from Conga, please contact our New Business team: Sales Information [email protected] Telephone: Conga. All Rights Reserved. Conga, Conga Suite and Conga Composer are all trademarks or registered trademarks of Conga, as are other names and marks. All other trademarks or registered trademarks are the properties of their respective owners.

2 Resources Examples: For detailed examples, including sample templates, report designs and sample output, please visit the knowledgebase article on our Conga Starter Template Library. Articles and Videos: Conga provides an online knowledge base and YouTube channel that are available 24X7 to help you answer questions. QuickStarts: Want to get started right away? Our QuickStart library will help you quickly generate your first Conga Composer solutions. The topics in the QuickStart library include: Creating a Simple Document Creating Your First Custom Solution Creating a Complete Solution Conga Composer Winter 13 Release Page 2

3 Table of Contents 1. What is Conga Composer? Create a Conga Composer button... 6 Create the button... 6 Adjust the Window Open Properties... 7 Add the button to a Page Layout Gather Salesforce Data... 9 What fields are available for merging? What if I need data from an object related to the Master Object? Using Salesforce Reports with Conga Composer Using Conga Queries with Conga Composer Create and Store a Merge Template Refine Conga Composer Solutions with Parameters Basic Configuration Parameters Data-Gathering Parameters Template Selection Parameters Parameters Activity Logging Parameters Conga Window Appearance Background Mode Parameters Output File Parameters General Output File Parameters PDF (Output File) Parameters Excel Parameters PowerPoint Parameters Word Parameters Template Parameters Integration Parameters DocuSign Integration Parameters EchoSign Integration Parameters Salesforce Chatter Integration Parameters Salesforce Content Integration Parameters SendGrid Integration Parameters Sertifi Integration Parameters SpringCM Integration Parameters Advanced Parameters Advanced Data Gathering Parameters Advanced Template Selection Parameters Advanced Data-Formatting Parameters Advanced Control Parameters Formula-Driven Parameters Conga Composer URL Examples Conga Template Manager Know Your Limits Other Parameters Supported Culture Codes Index of Conga Composer Parameters Conga Composer Winter 13 Release Page 3

4 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 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-aservice 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. Conga Composer Winter 13 Release Page 4

5 Conga Composer 1. What is Conga Composer? Conga Composer allows you to create an individual document from a button or link placed on a standard or custom object page layout. With Conga Composer, you can retrieve data from multiple Salesforce objects using specially configured Salesforce reports (or other search requests), and then merge the data into a Word, Excel, PowerPoint, PDF template or HTML . This chapter provides guidance on building Conga Composer solutions that leverage Salesforce Reports as a data source. The following illustration depicts a common business scenario in which Conga Composer retrieves data from multiple reports to produce a sophisticated document. Conga Composer Winter 13 Release Page 5

6 2. Create a Conga Composer button Create the button You ll need to create a button (or link) from which you will invoke Conga Composer. 1. Choose Setup App Setup Customize [Object] Buttons and Links 2. Click New in the Custom Buttons and Links section 3. For the Label, enter something that will describe the kind of document you will create with Conga Composer, or simply enter Conga Composer. 4. For the Display type, choose Detail Page Button 5. In the URL text box, type or paste the Conga Composer Base URL: &ServerUrl={!API.Partner_Server_URL_210} &Id= 6. Append your object s Id to the end of the URL (after Id=) using the Insert Merge Field list. For example, a Contact would require {!Contact.Id}, an Account would require {!Account.Id} and a custom object would require {!Record.Id}. Tip! Always use the Insert Merge Field list to locate the desired Id field. This id is the Master Object Id. Tip! Your button URL must not contain spaces, particularly at the ends of lines 7. Click Save. Tip! Conga Composer will retrieve all fields from the Master Object, automatically making them available for merging. Conga Composer Winter 13 Release Page 6

7 Adjust the Window Open Properties 1. Choose Setup App Setup Customize [Object] Buttons and Links 2. Click the name of the button you created (not the Edit link) 3. Click Window Open Properties 4. Set the Height to Clear the checkbox on #6 Show Scrollbars 6. Click Save Conga Composer Winter 13 Release Page 7

8 Add the button to a Page Layout 1. Choose Setup App Setup Customize [Object] Page Layouts and edit the desired Page Layout. From the Page Layout Properties screen, click Buttons or Custom Links. 2. Drag your new button to the appropriate region on the page layout. 3. Click Save. Tip! The button you have created is ready for use. Open a record of this type in Salesforce and click your new button to see Conga Composer in action! Note: The Preview As button will not work. Watch a Video This video demonstrates how to create a basic Conga Composer button Conga Composer Winter 13 Release Page 8

9 3. Gather Salesforce Data The process of gathering the correct data from Salesforce is iterative. Generally, you start by examining the fields that Conga Composer has automatically retrieved. If those fields are sufficient for your solution, you re ready to build your template. If not, you ll need to add as many Reports or Queries necessary to retrieve whatever data is required for your solution. (1) Examine the Template Builder window (2) Add or modify Salesforce Reports (3) Modify Conga Composer Button URL How do you know which fields are available to you? To answer that question, let s discover the power of the Template Builder. Conga Composer Winter 13 Release Page 9

10 What fields are available for merging? An essential tool in the development of Conga Composer solutions is the Template Builder. The Template Builder is located at the lower-left corner of the Conga Composer page. Tip! You ll use the Template Builder frequently in the upcoming sections. The Template Builder exposes the data retrieved by Conga Composer from the Master Object, and from any Salesforce Reports or Conga Queries referenced in the Conga Composer URL. (The use of Salesforce Reports and Conga Queries is described later in this chapter.) Select the desired dataset to view the available merge field names. The field names listed in the left column indicate the field names you must use in your templates. Filter the list of fields by entering search criteria in the Live Search box. You may search the field names or the sample data (drawn from the first row of data available). Click the field name to copy it to the clipboard, then switch to your template (in Word, Excel, PowerPoint or a PDF Form) and paste the field name into the appropriate location (see the template-specific guides for information on how to create a merge field). See the next page for several tips on how to best use the Template Builder. Conga Composer Winter 13 Release Page 10

11 Tip! If an Opportunity is your Master Object, Conga Composer will automatically make the Opportunity Line Items available for merging in the OppLineItems dataset. Tip! If a Quote is your Master Object, Conga Composer will automatically make the Quote Line Items available for merging in the QuoteLineItems dataset. Tip! The View Data link allows you to download the available data as an Excel workbook. Tip! The User and Org datasets appear only if Track Activities is enabled for the Master Object Conga Composer Winter 13 Release Page 11

12 What if I need data from an object related to the Master Object? To gather information from Salesforce that isn t contained in the Master Object, you may use: One or more Salesforce Reports One or more Conga Queries The benefit of using Salesforce Reports to gather additional data for Conga Composer is that creating reports and linking them to Conga Composer is quick and easy, but they re somewhat limited in the information you can access. Conga Queries, on the other hand, are more powerful in that they can access most objects in Salesforce, but they re more complicated to set up. Let s examine each method. Conga Composer Winter 13 Release Page 12

13 Using Salesforce Reports with Conga Composer You can use a Salesforce report to retrieve data related to your Master Object. Conga Composer will automatically filter the report by passing the Master Object Id into the report s Advanced Filters. (You may override the default behavior and instead use other information to filter the report.) Conga Composer filters the report by passing the Master Object Id into the first cell of the value column in the report when the merge begins Example: Let s say your Conga Composer button is located on an Account and you d like to use a report to retrieve all Contacts related to that Account so you can print a phone directory. 1. Create a Conga Composer button and place it on your Account page layout 2. Create a report based on Contacts & Accounts 3. Drag and drop the fields you re interested in from Fields to Preview 4. In the Filters section, set the following: a. Show: View drop-down list to All Accounts b. Date Field: Clear any values in Start Date and End Date c. Add Field Filter: Field drop-down list to Account Id 5. Save the report into any publicly accessible folder, we recommend Conga Composer Reports. (See Best Practice: Report Naming Conventions for advice about report names and folders.) Conga Composer Winter 13 Release Page 13

14 This report is now ready to receive the Master Object Id (which is the Account Id) from Conga Composer. Next, we ll explore how to include the report in the Conga Composer button. Tip! Test your report by pasting sample data into the Advanced Filters and choose Run Report. Don t save the report with the sample data. (In our example, you would paste an Account Id.) Tip! Focus the scope of each Conga Composer report to pull only the objects and fields necessary. Tip! Conga Composer will retrieve a report that contains a maximum of 1,500 rows and contains less than 5 Mb of total data. Additionally, each Conga Composer solution has a combined row limit of 25,000. Tip! If you include an Id column in your report, position it as the last (right-most) column. Referencing the Report in the Conga Composer button To include the new report in the Conga Composer button, do the following: 1. Open the Reports Tab 2. Run the report by clicking the report name 3. Select the report s Id in the browser s URL and copy it to the clipboard (the 15- character value after the last / (slash)) 4. Edit the Conga Composer button: Setup App Setup Customize [Object] Buttons and Links Edit 5. Move to the end of the URL and enter the following parameters: &ReportId= 6. Paste the Report Id from the clipboard 7. Save the button Tip! After including a report in the Conga Composer button, click the Conga Composer button and then open the Template Builder to test whether Conga Composer has retrieved the correct data. Tip! You may use up to 50 reports in a Conga Composer button. Create another report (as directed above) and include its Id after the previous Report Id, separated by a comma. Watch a Video This video demonstrates how to include a Salesforce report in a Conga Composer button Conga Composer Winter 13 Release Page 14

15 Frequently Asked Questions about using Salesforce Reports in Conga Composer FAQ: How can I filter the report on something other than the Master Object Id? Although Conga Composer will use the Master Object Id as the default filter value in the report s Advanced Filters, you may override this behavior and use any field from the master object. Tip! You can also use a field from a parent of the master object, like an Account field related to a Contact. To use a different field, you ll need to do the following: Configure your report to receive the desired value Update your Conga Composer button to send the desired value Configure your report to receive some other field value: 1. Edit the report 2. In the Filters section, Add a Field Filter and select the field you d like to use in the field drop-down list 3. Leave the Value field empty (This cell is known as pv0) 4. Save the report Example: Let s extend our example from earlier. Instead of creating a directory of Contacts at a given Account, let s say we want all Contacts who are in the same state as the Account (but not necessarily affiliated with the Account). In the image above, the Account Id field has been replaced with Contact s Mailing State/Province so that we can search for Contacts who are in the same State/Province as the Account. Update your Conga Composer button to send the desired value: 1. Edit the Conga Composer button: Setup App Setup Customize [Object] Buttons and Links Edit 2. Move to the end of the URL and add the following to the ReportId parameter:?pv0= 3. Select the field that contains the desired search criteria from the Insert Merge Field drop-down list. Example: Change the Report Id parameter so that it uses the Account s Billing State as the search criteria. The parameter would appear as: &ReportId=00O LNBd?pv0={!Account.BillingState} Tip! When including a?pv0= parameter, the pv must be lowercase. Tip! Don t use fields that might contain commas or ampersands to filter reports. Best practice: Use Id fields to ensure correct results. Conga Composer Winter 13 Release Page 15

16 Tip! When passing numeric date values to a report, you must pass them in the US date format, mm/dd/yyyy. You can ensure the correct format by using a Salesforce formula field to parse a Date field. Conga Composer Winter 13 Release Page 16

17 FAQ: How can I filter the report with criteria from two or more fields? For even more demanding situations, you can pass a second, a third and even as many as five parameters to the same report. The values for those parameters are numbered sequentially: pv0, pv1, pv2, etc. Each pv parameter must be separated with a tilde symbol (~). Example: Extending the example from above, let s say we want a list of all Contacts in the same State/Province as the Account and who are also doctors. The selection criteria of the report would need to be: The Report Id parameter Conga Composer button URL would need to be: Conga Composer Winter 13 Release Page 17

18 FAQ: How can I filter the report with two or more values from one field? You may use multiple values in a single pv value by separating each value with a pipe symbol ( ). Example: Again, extending the previous example, let s say we want a list of all Contacts in the same State/Province, who are either doctors or professors. In this case, the report is already ready to receive the filter criteria. We only need to change the Report Id parameter of the Conga Composer button: Conga Composer Winter 13 Release Page 18

19 FAQ: My report already has filter criteria under Advanced Filters. Can Conga Composer filter the report using subsequent rows in Advanced Filters? Yes. If you want Conga Composer to filter your report with a value in, say, the pv1 position, you may define the ReportId parameter in your button to use any combination of pv positions. Example: Let s say your report has filter criteria in the first row of the Advanced Filters (i.e., the pv0 position) and you want Conga Composer to supply filter criteria for the second row (pv1). You could specify that as: &ReportId=00O LNBd?pv1={!Account.BillingState} FAQ: What if I don t want to dynamically filter the report? I just want the report contents as-is. You can retrieve the contents of a report without applying any dynamic filtering by passing an empty value for pv0 : &ReportId=00O LNBd?pv0= FAQ: How can I gather data from multiple reports? Conga Composer Winter 13 Release Page 19

20 You may include up to 50 ReportId parameters in a Conga Composer URL, thus making 50 reports accessible in a single merge operation. To do so, enter a comma, then the next Id as shown below. Example: Here, we have Conga Composer configured to pull data from four reports: &ServerURL={!API.Partner_Server_URL_210} &Id={!Contact.Id} &ReportID=00O NGuW, 00O O2gr, 00O NGv5?pv1={!Contact.MailingState}, 00O NGvL Each of these reports would be visible through the Template Builder window as a separate dataset. Conga Composer automatically assigns the worksheet names based on the sequence of report IDs included in a Conga Composer URL. You may also use Report Aliases to name the worksheets. See Using Report Aliases for details. Conga Composer Winter 13 Release Page 20

21 FAQ: How can I control the sort-order of the data retrieved from a report? You can control the sort-order of the information Conga Composer retrieves from a report: 1. From the Reports Tab, run the Report by clicking its name 2. Click the column-header label of the desired column to sort by 3. Save the report Example: Say your report shows a list of Contacts related to an Account and you d like the list of contacts sorted by Last Name. To set the sort-order, you would run the report, click on the Last Name column (even though the report may have zero rows of information currently on it), then save the report. When Conga Composer interacts with the report, the data it gathers is sorted according to your sort-order choice. Tip! You can sort on multiple columns by changing the report to a Summary Report and summarizing on another field. Conga Composer doesn t use the summary information, but will adhere to the sort-order of the report. Conga Composer Winter 13 Release Page 21

22 FAQ: I m creating Quotes (or Invoices) from an Opportunity and its related Opportunity Line Items. Do I need a report to retrieve the Opportunity Line Items? No, in this particular case, you don t. Conga Composer automatically makes Opportunity Line Items available to you without any reports because the master object is an Opportunity. Opportunity Line Items appear as a separate dataset ( OppLineItems ) in the Template Builder window: Tip! Conga Composer will automatically retrieve the line items from a Salesforce Quote record, too. Conga Composer Winter 13 Release Page 22

23 FAQ: How can I use my own label for a data sheet? You may supply an alias for a Report (or Query) to override the default name. Please follow these guidelines: The alias must precede the Salesforce Report (or Query) Id It must be enclosed in square brackets ( [ and ] ) It may contain only alphanumeric characters; punctuation marks and other special characters are not permitted It must contain at least 2 characters and but not more than 20 characters It must be unique within the entire Conga Composer URL Spaces are not permitted within an alias, or between the brackets and the Report Id Reserved sheet names ( Master, Org, User, ReportData, etc.) may not be used as an alias Example: In this example, an alias has been added to each Report Id. The resulting datasets in the Template Builder window appear as: The field names in your template must then refer to the alias name. For example, in Microsoft Word would you create a field for { TableStart:Contacts } and { TableEnd:Contacts }. Conga Composer Winter 13 Release Page 23

24 Best Practice: Report Naming Conventions When naming reports created for use with Conga Composer, we suggest you adopt a naming convention that reflects: The Conga Composer solution the reports are intended to support (Account Plan, Custom Invoice, etc.) The sequence in which the reports are listed in the Conga Composer URL (ReportData, ReportData1, ReportData2, etc.) or the Report Alias (see FAQ: How can I use my own label for a data sheet? above for further details) A description of the data being retrieved The Salesforce Report Type In the example below, four Salesforce reports called from a Conga Composer solution titled Executive Brief on a Contact page layout might be named as follows: By following this guidance, you will find it much easier to locate the Salesforce report responsible for the tables revealed on the Template Builder window. Tip! If you follow this guidance and for some reason change the order of the report IDs in the URL, or insert or delete one, remember to update the impacted Salesforce Report Names to ensure they reflect their position(s) in the URL. You can avoid having to make this update by using Report Aliases instead. Conga Composer Winter 13 Release Page 24

25 Using Report Fields in Templates Fields retrieved from Conga Composer reports require special attention in templates. This is true of Word, Excel and PDF templates, though the conventions differ from one to the other. For complete details about designing templates, please see the various guides on the Documentation page of our support website: Microsoft Word Merge Templates Microsoft Excel Merge Templates Microsoft PowerPoint Merge Templates PDF Templates Conga HTML Templates Storing Merge Templates Conga Composer Winter 13 Release Page 25

26 Using Conga Queries with Conga Composer In addition to using Salesforce reports to gather information from Salesforce, you may also use Conga Queries, records stored in the Conga Query Manager. The link to this private listing is located on our website. Locate Conga Query Manager, click Get It Now for your appropriate Salesforce edition and then follow the instructions to install the additional component. This custom object stores Salesforce Object Query Language (SOQL) statements that will retrieve data related to the Master Object. Complete details on the installation and use of the Conga Query Manager are provided on the Support page from our website. Using Queries instead of Reports Conga Queries have certain strengths over the use of Salesforce Reports for gathering data: Queries are slightly faster and more reliable than Salesforce Reports Queries can access objects that cannot be displayed in Salesforce Reports (Notes, Approval History) Queries reduce clutter on the Reports Tab Queries have tighter security and visibility controls than Salesforce Reports Queries are more reliable when multiple queries (say, over 10) are including in Conga Composer solution Using Salesforce reports remains a viable option for basic requirements. Warning! Conga Composer will retrieve a report (or query) that contains a maximum of 1,500 rows and contains less than 5 Mb of total data. Additionally, each Conga Composer solution has a combined row limit of 25,000. For complete details on how to use Conga Queries, please visit our Documentation page, and look for the Conga Query Manager link. Conga Composer Winter 13 Release Page 26

27 Create and Store a Merge Template Now that your Conga Composer button is configured to retrieve the desired data from Salesforce, your next task is to create a merge template using Word, Excel, PowerPoint, HTML , or PDF form. Each type of template has its own benefits and naming conventions regarding merge fields, so please refer to the appropriate guide for your template type: Microsoft Word Merge Templates Microsoft Excel Merge Templates Microsoft PowerPoint Merge Templates PDF Templates HTML Templates Finally, after designing a template you may store your template in any of three locations: The Conga Template Manager The Salesforce template repository Your local hard drive or network drive Each of these is discussed in Storing Merge Templates. Conga Composer Winter 13 Release Page 27

28 4. Refine Conga Composer Solutions with Parameters Conga Composer solutions can be highly customized to enhance the user experience. If desired, you may include any of the following parameters in your Conga Composer URL. Append each parameter to the URL value in your Conga Composer button. A few caveats: 1. Each parameter/value pair must be entered with the following convention: &Parameter=Value 2. Each parameter must begin with an ampersand (&) 3. Spaces are not permitted anywhere in Conga Composer URLs, including parameter/value pairs. If your Value requires spaces, replace them with plus signs (+). Quotes ( ) are not permitted anywhere in URLs either. 4. Parameter names are not case-sensitive, but the values you set them to may be, so it s a best practice to observe case closely 5. Parameters may be appended to the Conga Composer URL in any order 6. Several complete examples are available in the last section of this chapter 7. The Conga Composer URL should not exceed 1750 characters We invite you to explore the following categories: 1. Basic Configuration 2. Dialog Box Appearance 3. Output File Parameters 4. Integration Parameters Conga Composer Winter 13 Release Page 28

29 Basic Configuration Parameters The Basic Configuration Group lists the most popular parameters for Conga Composer. These parameters define: How data is gathered Which templates are presented to users How to address outbound messages How activity logging should take place Data-Gathering Parameters The following parameters affect how Conga Composer gathers data from Salesforce. PARAMETER Id=[id] Sets the master object. All fields are retrieved from this object. ** Note: A Conga Composer URL must contain one (and only one) instance of this parameter ** A Salesforce Id of any record (Contact, Lead, Account, Custom Object, etc.) or a field that contains an Id Conga Composer Winter 13 Release Page 29

30 PARAMETER ReportId=[id] Retrieves the contents of the specified report(s) (identified by its 15- character Salesforce id) and makes the report contents available through a ReportData dataset as seen on the Template Builder window. You may include up to 50 ReportId values in a Conga Composer URL, thus making 50 reports accessible in a single merge operation. Conga Composer will retrieve a report that contains a maximum of 1,500 rows. A 15-character Salesforce Id of a Report. May optionally include filter criteria. Example 1: &ReportId= dg3A Example 2: (two reports) &ReportId=00O dg3A,00O dgF2 Report Aliases: An optional report alias may precede the report id: Enclose the alias in square brackets Minimum 2 characters, maximum 20 Alphanumeric characters only Reserved sheet names may not be used ( Master, Org, etc.) The alias must be unique within the button URL Example 1: &ReportId=[MyContacts] dg3A Example 2: (two reports) &ReportId=[MyAccounts]00O dg3A, [MyCases]00O dgF2 For more options and a complete discussion of using Reports with Conga Composer, please see Using Salesforce Reports with Conga Composer, page 13 Conga Composer Winter 13 Release Page 30

31 PARAMETER QueryId=[id] Retrieves the SOQL query stored in the specified Salesforce record(s), executes the SOQL query and makes the SOQL query results available through a QueryData dataset as seen on the Template Builder window. You may include up to 50 QueryId values in a Conga Composer URL, thus making 50 queries accessible in a single merge operation. Conga Composer will retrieve a query that contains a maximum of 1,500 rows. A 15-character Salesforce Id of a Query record. May optionally include filter criteria. Example 1: &QueryId=a dg3 Example 2: (two queries) &QueryId=a dg32, dgF2 Query Aliases: An optional query alias may precede the query id: Enclose the alias in square brackets Minimum 2 characters, maximum 20 Alphanumeric characters only Reserved sheet names may not be used ( Master, Org, etc.) The alias must be unique within the button URL Example 1: &QueryId=[MyContacts]a dg3 Example 2: (two queries) &QueryId=[MyAccounts]a dg32, [MyCases]a dgF2 For more options and a complete discussion of using Queries with Conga Composer, please see Using Conga Queries with Conga Composer, page 26 You can find other, more advanced parameters for Data Gathering in the Advanced Parameters section. Conga Composer Winter 13 Release Page 31

32 Template Selection Parameters The following parameters pertain to merge templates. PARAMETER TemplateId=[id] Pre-selects the template(s) specified in the File Template list box You may include up to 10 TemplateIds. Additional limitations apply. With multiple templates specified and the output format set to Adobe PDF, the system will convert each output files to PDF, join the collection and return a single PDF. With multiple templates specified and the output format set to Same as Template, the system will return a zipped file containing each output file. To return a zipped collection of PDFs, include the parameter &ZipPDFs=1 (see below). A 15-character Salesforce Id of a Template record Example 1: &TemplateId= dg3B Example 2 (multiple templates): &TemplateId= dg3B, Example 3 (referencing a field that contains the template id): &TemplateId={!Contact.TemplateId} TemplateGroup=[value] Filters the list of file templates that appear on the Conga Composer dialog box to those that match this criteria. May include one or more values, separated by commas. Templates must be stored in Conga Template Manager Template Group value set on each Template Manager record Each record in the Conga Template Manager can be set with one or more Template Group values, separated by commas. This parameter filters the available templates using this field. Conga Composer Winter 13 Release Page 32

33 PARAMETER SelectTemplates=[0 or 1] Displays the Multiple Template Selection dialog box which allows users to select and arrange up to 10 templates from any of the following template sources: Conga Template Manager Salesforce Content Salesforce Documents Tab The Salesforce Content Title and Description fields are searchable through the dialog box. At this time, the attachments are not indexed. Salesforce Content may be suppressed by including the &HideContent=1 parameter. Salesforce Content can be set as the default option by including the &DefaultPane=1 parameter. Tips: This parameter works especially well with the TemplateGroup parameter, which can be used to ensure that each template has appropriate merge fields. This parameter also works especially well as an inline window, rather than as a traditional pop-up window. If Background Mode (DS7) is also included, a template must be selected This parameter won t work with a QVar that results in a list of template ids. You can find other, more advanced parameters for Template Selection in the Advanced Parameters section. Conga Composer Winter 13 Release Page 33

34 FAQ: Pre-Selecting a Merge Template for Conga Composer Solution For most Conga Composer solutions, it s often desirable to pre-select the template that you ve intended to use with this particular merge operation. You may do so by including the TemplateId parameter in the URL that calls Conga Composer. Example: &ServerURL={!API.Partner_Server_URL_210} &Id={!Contact.Id} &TemplateId=01H tMS The Id of the desired template is found by navigating to the template, stored in either the Salesforce template repository or the Conga Template Manager. Click the name of the template and select the id from the template s URL. Tip! The id required is from the Template Manager record, not the attachment stored with the record Conga Composer Winter 13 Release Page 34

35 This page intentionally left blank Conga Composer Winter 13 Release Page 35

36 Parameters The standard Conga Composer dialog includes the option to generate the desired merge output and attach it directly to an outbound Salesforce message. This feature can greatly reduce the time required to otherwise generate a merge file, save it to disk, launch an message and attach the file a great productivity tool. Tip! The Parameters work with Conga's integration with SendGrid. Conga Composer Winter 13 Release Page 36

37 PARAMETER ToId=[id] Sets the value of the To field. A Salesforce Id of a Contact or Lead, or a field that contains the Id of a Contact or Lead. Note: If using a Lead Id with Conga Templates, must use SendGrid integration, Leads and Conga Templates do not work with Salesforce . If the Conga Composer Master Object is an Opportunity, the To field is automatically set to the Primary Contact, without the use of this parameter. To override this behavior from an Opportunity, set the parameter to +, e.g., & ToId=+ If the Conga Composer Master Object is a Quote, the To field is automatically set to the Contact on the Quote, without the use of this parameter. Example 1: & ToId={!Contact.Id} Example 2: & ToId= dg3C NOTE: This parameter will not work when the master object is a Lead and you are using Conga templates, there is a Salesforce limitation concerning Leads. It will however work when using standard Salesforce templates. RelatedToId=[id] Sets the value of the Related To field. The Salesforce ID of an Account, Opportunity or other Salesforce object, or a field that contains this kind of ID. The Related To field causes the sent to appear in the Activity History related list of the object identified. In the absence of this parameter, Conga defaults the Related To field to the Master Object. The supported objects for the Related To field are: Account, Asset, Campaign, Case, Contract, Opportunity, Order, Product, Solution, custom objects with track activities enabled. Example 1: & RelatedToId={!Opportunity.Id} Example 2: & RelatedToId= dg3D AdditionalTo=[text] Sets the value of the Additional To field. An address or a field that contains one or more addresses. Example 1: & [email protected] Example 2: & [email protected], [email protected] Example 3: & AdditionalTo={!Contact.Other Address} Conga Composer Winter 13 Release Page 37

38 PARAMETER CC=[text] Sets the value of the CC field. An address or a field that contains one or more addresses. Example 1: & CC [email protected] Example 2: & CC={!Contact.Other Address} BCC=[text] Sets the value of the BCC field. An address or a field that contains one or more addresses. Example 1: & BCC [email protected] Example 2: & BCC={!Contact.Other Address} TemplateId=[id] Loads the subject and body fields from a Salesforce template. ** Note: Attachments stored directly in the template are not applied unless TemplateAttachments is set to 1 ** A 15-character Salesforce Id of an template stored in Setup Communication Templates Templates RelatedToId parameter or ToId parameter must be set Example: & TemplateId= dg7A Subject=[text] Sets the value of the Subject field. If you set this parameter and use TemplateId, this value will override the value of the Template s Subject. Any text. Use + to indicate spaces. Example 1: & Subject=Thank+You Example 2: & Subject=Account+Brief+for+{!Account.Name} TemplateAttachments= [0 or 1] Indicates to preserve attachments stored with the Template. If set to 0, attachments stored on the Template are ignored If set to 1, attachments stored on the Template are preserved TemplateId parameter must be set Conga Composer Winter 13 Release Page 38

39 PARAMETER FromId=[id] Indicates an Organization-Wide Address as the From identity of the . Requires A 15-character Salesforce Id of an Organization-Wide Address as defined in Setup Administration Organization-Wide Addresses Tip After setting up the Org-Wide Address, edit the record to locate the Salesforce Id. It will begin with 0D2 Each Org-Wide Address may be restricted by Profile ReplyToId=[id] Changes the apparent sender of an by setting the message's ReplyTo and DisplayName properties to those of the specified User. Requires A 15-character Salesforce User Id Important This parameter only affects that is delivered in an unattended manner, e.g., Background Mode (DS7=12), Conga Conductor and Conga Workflow. UseSignature=[0 or 1] Indicates whether to include or exclude the sending user's signature from appearing in the body. If set to 0, the signature block is excluded If set to 1, the signature block is included (default) Important This parameter only affects that is delivered in an unattended manner, e.g., Background Mode (DS7=12), Conga Conductor and Conga Workflow. FAQ: Detailed example of using the parameters Here s an example that would be applicable to a Conga Composer button contained on a Case. It specifies who to address the to, establishes the Related object, specifies the Additional To and CC fields, and then specifies an Template. &ServerURL={!API.Partner_Server_URL_210} &Id={!Contact.Id} &TemplateId=01H t & ToId={!Contact.Id} & RelatedToId={!Case.Id} & AdditionalTo={!Case.Owner } & [email protected] & TemplateId=00X vrZ4 Conga Composer Winter 13 Release Page 39

40 Activity Logging Parameters The following parameters affect the Log Activity Options of the Conga Composer dialog box. Tip! For clarity, the following LG parameters are shown in uppercase, however they are not case-sensitive in practice. PARAMETER LG0=[0 or 1] Save Text Determines whether to store the text of the document (post-merge) to the body of the Task If set to 0, Save Text: is -None- If set to 1, Save Text: is Document Text (Word only) (default) ** Note: This feature only works with Microsoft Word templates ** LG1=[text] Activity Subject Sets the Subject to the text specified. Also used as in the subject of a Follow- Up Task, if one is created. If not specified and the Activity Subject is blank, the output filename is used for the Activity Subject. Important: Do not use the less than (<) or greater than symbol (>) with this parameter Example 1: &LG1=Quote+Generated Example 2: &LG1={!Opportunity. Subject} Conga Composer Winter 13 Release Page 40

41 PARAMETER LG2=[integer] Follow-Up Date Sets the follow-up date by using the integer to add days to today s date Example:...&LG2=14 would set a follow-up date 14 days from today LG3=[0, 1 or 2] Attach File Sets the file attachment options If set to 0, "Attach File:" is "-None-" (default) If set to 1, "Attach File:" is "Attach to [record]" where [record] would be the type of master object record, e.g., Opportunity If set to 2, "Attach File:" is "Attach only, No Task Record" LG4=[0, 1 or 2] Automatic Logging Sets whether to automatically log an activity after merging If set to 0, Automatic Logging is disabled (default) If set to 1, Automatic Logging is enabled If set to 2, Master Field to Set fields are updated but no Task record is created LG5=[id] Sets the Assigned To field in the Activity A Salesforce Id of a User or a field that contains this kind of Id. In the absence of this parameter, the Assigned To field is set to the current user. Example 1: &LG5={!Opportunity.Assistant c} Example 2: &LG5= dg3D LG6=[id] Sets the Assigned To field in the Follow-Up Activity A Salesforce Id of a User or a field that contains this kind of Id. In the absence of this parameter, the Assigned To field of a follow-up activity is set to the current user. Example 1: &LG6={!Opportunity.Assistant c} Example 2: &LG6= dg3D Conga Composer Winter 13 Release Page 41

42 PARAMETER LG7=[text] Sets the Activity Subject in the Follow-Up Activity Sets the Subject to the text specified. If not specified the Follow-Up Activity Subject is set to Follow-Up: and the Activity Subject value. Important: Do not use the less than (<) or greater than symbol (>) with this parameter Example 1: &LG7=Please+follow-up Example 2: &LG7={!Opportunity. Subject} LGAttachOption= [0, 1, 2 or 3] Sets the Salesforce object to which attachments generated during Activity Logging are stored If set to 0, attachments are saved to Notes & Attachments (default) If set to 1, attachments are saved to Salesforce Content If set to 2, attachments are saved to Salesforce Chatter If set to 3, attachments are saved to SpringCM &LG3=1 or 2 &LG4=1 or 2 Works with: AttachmentParentId (see below) AttachmentParentId=[id] Specifies the record in Salesforce to which the output file is attached, when requested. In the absence of this parameter, the default attachment parent record is the Master Object. A Salesforce Id of a object to which attachments are allowed. When used with LGAttachOption=2 (Chatter), this parameter may be set to a Chatter User Id or Chatter Group Id. LGParentId=[id] Overrides the default record against which a completed task is created. In the absence of this parameter, the task is created against the Master Object. A Salesforce Id of an object which allows Activity Tracking Example: &Id={!Opportunity.Id} &LGParentId={!Account.Id} LGWhoId=[id] Specifies the WhoId (the related Contact/Lead) when creating a Task record. A Salesforce Id of an object which allows Activity Tracking Conga Composer Winter 13 Release Page 42

43 PARAMETER MFTS0=[ApiFieldName] Also available: MFTS1, MFTS2 Master Field to Set The API Field Name of the field that should be set as part of the activity logging activity A value in the corresponding MFTSValue parameter (see below) As part of the Activity Logging family of parameters, this feature is usually triggered through Automatic Logging (&LG4=1 or 2) MFTSValue0=[text] Also available: MFTSValue1, MFTSValue2 Master Field to Set Value A value in the corresponding MFTS parameter Don t use with &, %, < or > or other special characters MFTSId0= Also available: MFTSId1, MFTSId2 Set a field on a non-master record For a long time Composer has allowed you to set a field on the Master Object. This behavior (known as Master Field to Set ) has been enhanced so that you may set a field on another record instead of the Master Object. This parameter must be used in conjunction with &MFTS0 and &MFTSValue0. Example: &id={!opportunity.id} &MFTSId0={!Account.Id} &MFTS0=Opportunity_Status c &MFTSValue0=Proposal+Created In this example, the Master Object is an Opportunity, however the Master Field to Set parameters are configured to set the Opportunity_Status c field on the related Account. The field would be set to Proposal Created. As is customary with Master Field to Set, fields are set as part of the Activity Logging options. Frequently, administrators choose to include the &LG4=1 or 2 parameter so that Activity Logging takes place automatically, and field updates are therefore automatically included. This parameter may be populated via a QVar query. Conga Composer Winter 13 Release Page 43

44 Conga Window Appearance The Conga Window Appearance Group lists the parameters that primarily affect the appearance of the Conga window. These parameters define: Interface Restriction Parameters Background Mode Parameters Interface Restriction Parameters For a variety of reasons, it may sometimes be desirable to pre-set certain settings on the Conga Composer dialog and restrict the user s ability to alter them. Note: This is a navigation/convenience feature, not a security feature. Though the parameters are deliberately cryptic to obscure their purpose, a determined user could potentially alter them in a URL and override the intended behavior. PARAMETER FP0=[0, 1 or 2] Locks the output file format If set to 0, Output Format is Same as template and the output format radio buttons are not locked (default) If set to 1, Output Format is Adobe Acrobat and the output format radio buttons are locked If set to 2, Output Format is Same as template and the output format radio buttons are locked DS0=[0 or 1] Disable Controls If set to 0, all controls in the Conga Composer dialog box (including buttons) are enabled (default) If set to 1, all controls in the Conga Composer dialog box (except the buttons) are disabled Conga Composer Winter 13 Release Page 44

45 PARAMETER DS1=[0 or 1] Disable Merge Button If set to 0, the Merge Button is enabled (default) If set to 1, the Merge Button is disabled DS2=[0 or 1] Disable Button If set to 0, the Button is enabled (default) If set to 1, the Button is disabled DS3=[0 or 1] Disable Log Activity Button If set to 0, the Log Activity Button is enabled (default) If set to 1, the Log Activity Button is disabled DS4=[0 or 1] Lock Template Choices If set to 0, the list of template choices is not locked (default) If set to 1, the selected template choice is locked TemplateId parameter must be configured In the absence of this parameter, the template indicated by the TemplateId parameter is pre-selected in the list, but the user may select a different template. This parameter prevents the user from selecting a different template. DS5=[0 or 1] Disable View Data link If set to 0, the View Data link is enabled (default) If set to 1, the View Data link is disabled DS6=[0 or 1] Disable View Template link If set to 0, the View Template link is enabled (default) If set to 1, the View Template link is disabled DS7=[code] Background Mode: Initiate Conga Composer without user intervention Complete details about Background Mode are contained in the next section, Background Mode Parameters DS8=[0 or 1] When enabled, makes the Choose a template from your local computer radio button visible, regardless of the corresponding setting on the Setup page If set to 0, the Local Templates radio button behaves according to the setting on the Setup page (default) If set to 1, the Local Templates radio button is displayed DS9=[0 or 1] Disable Template Builder link If set to 0, the Template Builder link is enabled (default) If set to 1, the Template Builder link is disabled You can find other, more advanced parameters for Conga Window Restrictions in the Advanced Parameters section. Conga Composer Winter 13 Release Page 45

46 Background Mode Parameters Background Mode parameters let you bypass the classic Conga Composer dialog box. In the following table, the various background mode (DS7) parameter values are summarized by the type of behavior desired. Once you ve located the desired behavior, please glance at the details for that mode to determine whether other prerequisites must be met. GENERAL BEHAVIOR DS7 VALUE Attach the output file to Salesforce 1 Master Object5 Master Object, No Refresh 6 Salesforce Content the output file Automatic Download the output file 3 Prompt for Download 13 Automatic Download Integrate with EchoSign 4 EchoSign Agreement 14 Auto-Deliver then Master Object 24 Auto-Deliver then Confirmation Integrate with DocuSign 7 DocuSign Envelope 17 Auto-Deliver Integrate with SpringCM 8 SpringCM folder PARAMETER BML=[text] Background Mode Label Displays a message on the Background Mode dialog box. Displays up to 50 characters. Background Mode (DS7) must be configured Example 1: &BML =Thank+You Example 2: &BML=Account+Brief+for+{!Account.Name} Conga Composer Winter 13 Release Page 46

47 PARAMETER DS7=[0, 1, 2, 3, 4, 5, 6, 7, 8, 12, 13, 14, 17 or 24] Background Mode: Initiate Conga Composer without user intervention TemplateId parameter must be set It is recommended that the Window Open Properties for the link or button be set to: Width: 300 Height: 150 ** Note: When using mode (ds7=2), Direct mode (ds7=3) or EchoSign mode (ds7=4), if you want to log activities or follow-up tasks, you must also enable Automatic Logging (lg4=1) since those settings fall under Log Activity Options. ** DS7=0 Background Mode is not enabled (default) DS7=1 Background Mode is enabled and the merged document is attached to the master object *** Warning *** &DS7=1 causes the output document to be attached to the Master Object AND created a completed Task. To suppress the Task record, include the &LG3=2 parameter. DS7=2 Background Mode is enabled and the merged document is attached to a Salesforce DS7=3 Background Mode is enabled and the merged document is delivered to browser to save or open DS7=4 Background Mode is enabled and the merged document is attached to a new EchoSign Agreement. (See EchoSign integration parameters) DS7=5 Background Mode is enabled and the merged document is attached to the master object (like ds7=1), except that the user can navigate away from the master object while the merge process occurs DS7=6 Background Mode is enabled and the merged document is attached to Salesforce Content DS7=7 Background Mode is enabled and the merged document is attached to a DocuSign Envelope DS7=8 Background Mode is enabled and the merged document is saved in a SpringCM folder DS7=12 Background Mode is enabled and the merged document is automatically delivered via . (Requires ToId and TemplateId) *** Warning *** No preview available before delivery. Please test your configuration thoroughly before using this value. Conga Composer Winter 13 Release Page 47

48 PARAMETER DS7=13 Background Mode is enabled and the merged document is automatically delivered to browser to save or open. *** Warning *** The behavior of this parameter varies by browser. Please test your solution thoroughly before releasing to your endusers. For Internet Explorer, we recommend the following browser configuration: (1) Add to Trusted Sites (2) Allow files to open from Trusted Sites (Custom Settings Downloads Enable) (3) Enable Protected Mode checkbox (or position the window to run Inline) DS7=14 Background Mode is enabled and the merged document is automatically delivered via EchoSign. *** Warning *** No preview available before delivery. Please test your configuration thoroughly before using this value. DS7=17 Background Mode is enabled and the merged document is attached to a DocuSign Envelope and automatically delivered. *** Warning *** No preview available before delivery. Please test your configuration thoroughly before using this value. DS7=24 Background Mode is enabled and the merged document is automatically delivered via EchoSign. The browser is redirected to the EchoSign Confirmation Page. EchoSign version 9.5+ *** Warning *** No preview available before delivery. Please test your configuration thoroughly before using this value. DS7Preview=[0 or 1] Background Mode Preview Allows the end-user to preview the merged PDF before delivering the file according to the specific DS7 mode Warning: Currently does not work with Conga Template Id FP0=1 or DefaultPDF=1 DS7 set to anything except 3 or 13 Conga Composer Winter 13 Release Page 48

49 Conga Composer error messages are still displayed on the dialog box, even when Background Mode is enabled. If you're using a pop-up window for a background mode dialog box, we recommend enabling the "Resizable" property so the window can be stretched in case an error message is displayed. Conga Composer Winter 13 Release Page 49

50 This page intentionally left blank Conga Composer Winter 13 Release Page 50

51 Output File Parameters The Output File Parameters Group lists the parameters that primarily affect the behavior of the merge templates used in a merge operation. These parameters define: General Output File Parameters PDF Output File Parameters Excel Parameters PowerPoint Parameters Word Parameters Template Parameters General Output File Parameters The following parameters affect the output file generated by Conga Composer. PARAMETER DefaultPDF=[0 or 1] Sets the default output type to Adobe Acrobat If set to 0, "Output Format" is "Same as template" (default) If set to 1, "Output Format" is "Adobe Acrobat" The user may override this choice unless the Lock Output to PDF parameter (fp0=1) is enabled. FP0=[0, 1 or 2] Locks the output file format If set to 0, "Output Format" is "Same as template" and not locked (default) If set to 1, "Output Format" is "Adobe Acrobat" If set to 2, Output Format is Same as template and the output format radio buttons are locked Then, the Output Format radio buttons are locked. Conga Composer Winter 13 Release Page 51

52 PARAMETER OFN=[text] Sets the Output File Name, overriding the default output file name. A text value to use for the output file name You may use static text or merge field names for the values to place in the filename. Use a plus sign (+) to represent literal spaces. Do not include symbols unsupported in filenames, \, /, >, <, etc. Example:...&OFN={!Account.Name}+-+Quote If the Account name is ABC Corp., the resulting file name would be: ABC Corp. Quote.doc Additionally, you may use a special field within the OFN parameter: {Template.Label} This can be used in a generic Conga Composer dialog box to refer to the template label (as defined in the Salesforce repository). If using a local template, the filename appears in place of the label. ** Note: Internet Explorer 7 will replace spaces in a filename with the characters %20 if the output file is opened before saving to disk. For example, the file above would appear as ABC%20Corp. %20-%20Quote.doc if the file is opened before saving to disk.** MTOFN=[text] Multi-template Output File Name sets the output file name when using multiple templates, affecting the file name of.zip files or consolidated PDFs. Example: &MTOFN={!Account.Name}+-+Invoice AttachmentParentId=[id] Specifies the record in Salesforce to which the output file is attached, when requested. In the absence of this parameter, the default attachment parent record is the Master Object. Also works with Conga Conductor (QMode=2) to control the behavior of the merge operation s primary output. A Salesforce Id of a object to which attachments are allowed. Conga Composer Winter 13 Release Page 52

53 PARAMETER AWD=[0, 1 or 2] Assemble Word Documents Assembles the output Word documents before the file is either converted to PDF or delivered to the specified output location. The benefit is unified page numbering and a "seamless" output document. All templates must be Microsoft Word. If set to 0, Word output files are not assembled, resulting in a ZIP file output (default) If set to 1, Word output files are assembled with a "New Page Section Break" between documents If set to 2, Word output files are assembled with a "Continuous Section Break" between documents Note: Embedded fonts only supported in first template, so the use of embedded fonts is not recommended Conga Composer Winter 13 Release Page 53

54 PDF (Output File) Parameters If the output file from the merge operation is a PDF, the following parameters affect the file generated by Conga Composer. PARAMETER FlattenPDFForms= [0 or 1] "Flattens" PDF Form fields from the output PDF. This parameter addresses a limitation in the iphone/ipad PDF Reader which does not display values in PDF form fields. By "flattening", the values of the fields are blended into the PDF background and are thus visible on ipads. If set to 0, the PDF form fields are not "flattened" (default) If set to 1, the PDF form fields are flattened A PDF Form Template. (Not for use with Word, Excel or PowerPoint templates) Note: Because this parameter flattens field contents, it is not comaptible with fields that contain code such as javascript PS0=[0 or 1] Enables PDF Encryption If set to 0, the PDF is not encrypted (default) If set to 1, the PDF is encrypted Output to a PDF Encrypts the output PDF and disables print, copy and form-fill. These settings apply to any PDF output, whether from a PDF form or after converting a Word or Excel template. PS1=[0 or 1] Allow PDF printing If set to 0, PDF printing is not permitted (default) If set to 1, PDF printing is permitted Output to a PDF and Enable PDF Encryption (ps0=1) enabled Enables printing options in the output PDF PS2=[0 or 1] Allow PDF copying If set to 0, PDF copying is not permitted (default) If set to 1, PDF copying is permitted Output to a PDF and Enable PDF Encryption (ps0=1) enabled Enables copying text to the clipboard from the output PDF PS3=[0 or 1] Allow PDF form fill-in If set to 0, PDF form fill-in is not permitted (default) If set to 1, PDF form fill-in is permitted Output to a PDF and Enable PDF Encryption (ps0=1) enabled Conga Composer Winter 13 Release Page 54

55 PARAMETER Enables form fields to be editable in the output PDF (for those fields not specified as read-only ) PSPW=[text] Sets the password to open the output PDF. Note: This parameter requires that &PS0=1 (PDF Security) be enabled. Example: &PSPW=OpenSesame PDFIQ=[5 to 100] Do Not Use PDF Image Quality Adjusts the quality of images in output PDF files. The quality scale ranges from 5 (low quality, small file size) to 100 (high quality, large file size). (Default value is 100.) PDFQR=[0 or 1] Do Not Use Enables Quick-Render mode on PDF output If set to 0, high-quality, low speed PDF rendering is enabled (default) If set to 1, low-quality, high speed PDF rendering is enabled Conga Composer Winter 13 Release Page 55

56 Excel Parameters The following parameters affect the behavior of Excel templates. PARAMETER ExcelAutoFitRows= [0 or 1] Automatically sizes the height of all rows in an Excel output document If set to 0, the height of the rows is not adjusted (default) If set to 1, the height of the rows is automatically adjusted ExcelAutoFitColumns= [0 or 1] Automatically sizes the width of all columns in an Excel output document If set to 0, the width of the columns is not adjusted (default) If set to 1, the width of the columns is automatically adjusted SCHP=[0, 1 or 2] Strips punctuation from merge field names This setting removes punctuation from merge field names, making it possible to refer to those fields in Excel templates. If set to 0, merge fields may contain parentheses If set to 1, parentheses are removed from merge field names If set to 2, all punctuation (including colons) are removed from merge field name PowerPoint Parameters The following parameters affect the behavior of PowerPoint templates. PARAMETER APF=[0 or 1] Assemble PPTX Files Assembles the output PPTX presentation files before the file is either converted to PDF or delivered to the specified output location. The benefit is unified slide numbering and a "seamless" output document. All templates must be PowerPoint PPTX. If set to 0, PPTX output files are not assembled, resulting in a ZIP file output (default) If set to 1, PPTX output files are assembled PPTPreserveRows= [0 or 1] Preserves the table size (rows) when merge fields are placed within a table. If set to 0, empty rows are removed (default) If set to 1, the table size is preserved whereby empty rows may appear Conga Composer Winter 13 Release Page 56

57 Word Parameters The following parameters affect the behavior of Word templates. PARAMETER AWD=[0, 1 or 2] Assemble Word Documents Assembles the output Word documents before the file is either converted to PDF or delivered to the specified output location. The benefit is unified page numbering and a "seamless" output document. All templates must be Microsoft Word. If set to 0, Word output files are not assembled, resulting in a ZIP file output (default) If set to 1, Word output files are assembled with a "New Page Section Break" between documents If set to 2, Word output files are assembled with a "Continuous Section Break" between documents Note: Embedded fonts only supported in first template, so the use of embedded fonts is not recommended WPD=[0 or 1] Enables Word Protect Documents behavior. The output Word document is locked to prevent editing, except for merge fields that contain the TEXTBOX: prefix. See the Microsoft Word Templates Guide for further details. Conga Composer Winter 13 Release Page 57

58 Template Parameters The following parameters affect the behavior of Conga templates. PARAMETER Conga TemplateId= [id] (or &CETID) Conga Template Id This parameter pre-selects the Conga Template specified in the Templates list on the Composer dialog box. Optionally, you may abbreviate this parameter to &CETId= You may specify only one Conga Template Id. This parameter may be populated via a QVAR query. Example 1: &Conga TemplateId=a0WG PNrS Example 2 (abbreviated): &CETId= a0wg pnrs Warning: Currently does not work with DS7Preview Conga Template Group=[text] (or &CETG) Conga Template Group This parameter filters the list of Conga Templates that appear in the Templates list on the Composer dialog box to those that match the specified criteria. The value may include one or more values, separated by commas. This parameter may be populated via a QVAR query. Example 1: &Conga TemplateGroup=Quotes Example 2 (abbreviated, multiple values specified): &CETG=USA,Contact Conga Composer Winter 13 Release Page 58

59 Integration Parameters The Integration Parameters Group lists the parameters that primarily affect how Conga integrates with a wide variety of electronic signature and document storage tools. These parameters define integrations with: DocuSign EchoSign Salesforce Chatter Salesforce Content SendGrid Sertifi SpringCM DocuSign Integration Parameters DocuSign delivers Conga Composer documents via , much like Salesforce itself, but adds the ability to acquire, track and file signatures. DocuSign lets you send documents electronically to collect electronic signatures and data from your Salesforce account. Your recipients sign, enter data, initial, and date your documents online and can update Salesforce automatically with signed documents and collected data. For more information visit the DocuSign AppExchange listing. DocuSign is available separately on the AppExchange. You must subscribe to that service to use these integration parameters. PARAMETER DocuSignVisible=[0 or 1] Makes the DocuSign button visible on the Conga Composer dialog box. DocuSign is available separately on the AppExchange. You must subscribe to that service to use this integration parameter. If set to 0, the DocuSign button is not visible (default) If set to 1, the DocuSign button is visible DocuSignR1Id=[id] Also available: The parameter with R2, R3, R4, R5 or R6 Sets the recipient of the document to be delivered A Salesforce Contact, Lead or User Id Example: &DocuSignR1Id=003ABCD12345 In the case of an Opportunity (as the master object) with Contact Roles, the contacts whose Contact Role values match the DocuSign Roles will automatically be included as document recipients DocuSignR1Role=[text] Also available: The parameter with R2, R3, R4, R5 or R6 Sets the recipient s role A valid DocuSign Role Name, as defined in Envelope Settings Example: &DocuSignR1Role=Signer+1 Conga Composer Winter 13 Release Page 59

60 PARAMETER DocuSignR1Type=[text] Also available: The parameter with R2, R3, R4, R5 or R6 Sets the recipient s type Example: &DocuSignR1Type=Signer DocuSignR1AccessCode= [text] Also available: The parameter with R2, R3, R4, R5 or R6 Sets the recipient s access code Example: &DocuSignR1AccessCode=ABC123 DocuSignR1RoutingOrder =[1,2 or 3] Sets the recipient s routing order Also available: The parameter with R2, R3, R4, R5 or R6 DocuSignRelatedAccount Id=[id] Sets the related Account field on the DocuSign Envelope. This parameter is used in establishing the relationship to the related Account on the DocuSign Status record. A Salesforce AccountId ID NOTE: This parameter only works when sending a DocuSign Envelope directly via the API using DS7=17 and QMode=7 Example: &DocuSignRelatedAccountId=001ABCDEFGH DocuSignCustomField= [ApiFieldName] Also available: DocuSignCustomField1 DocuSignCustomField2 DocuSignCustomField3 DocuSignCustomField4 DocuSignCustomField5 Sets the name of a custom field to set on the DocuSign Envelope Record created through the merge process. Use the Salesforce API name of the field on the DocuSign Envelope Custom Object. DocuSignCustomFieldValue Example: &DocuSignCustomField=Account c &DocuSignCustomFieldValue=001ABCEDFGHIJL DocuSignCustomField Value=[value] Also available: DocuSignCustom FieldValue1 DocuSignCustom FieldValue2 DocuSignCustom FieldValue3 DocuSignCustom FieldValue4 DocuSignCustom FieldValue5 Sets the value of the corresponding custom field DocuSignCustomField Conga Composer Winter 13 Release Page 60

61 PARAMETER DocuSign Body=[te xt] Populates the body of the DocuSign Because this value is transmitted through the Conga Composer window URL, we recommend that this value be brief (say, not more than 40 characters). DocuSignEndpoint=[Prod, Demo, Test, Preview] Used to configure a Conga Composer button to connect to a specific DocuSign endpoint. Note: We expect this parameter will be used by DocuSign account engineers rather than customers. DocuSignSendReminders =[0 or 1] Sends reminder s to recipients who have not yet completed their task If set to 0, reminders are not sent (default) If set to 1, reminders are sent DocuSignRemindIn =[0 to 999] Indicates how many days should pass before the first reminder is sent DocuSignRemindAgainIn =[0 to 999] Indicates how often (in days) the reminder should repeat until the transaction is complete DocuSignExpireIn =[0 to 999] Indicates the number of days until the transaction is expired DocuSignExpireVoidEnv =[0 or 1] Indicates whether to enable the envelope to automatically expire If set to 0, the envelope will not automatically expire If set to 1, the envelope will automatically expire (default) DocuSignWarnIn =[0 to 999] Indicates how many days prior to expiration you want an message to alert recipients that a deadline approaches for completion Conga Composer Winter 13 Release Page 61

62 PARAMETER DocuSignTag=[0 or 1] Enables the DocuSign Tag Mode After the merge operation is complete, the browser is redirected to the DocuSign Tag screen TemplateId must be set DocuSign Subject=[ text] Assign a custom subject By default, the subject sent through DocuSign is pulled from the DocuSign Admin Settings. With this parameter, you can override the Admin Settings and establish a custom value for the subject DocuSignIgnoreOCR=[0 or 1] Ignore Opportunity Contact Roles When Composer creates a DocuSign Envelope from an Opportunity, it automatically scans the list of Opportunity Contact Roles and attempts to match DocuSign Role Names with the Contact Roles. If they match, the Contact is automatically included as a signer. Now, you can choose to skip that behavior, forcing Composer to ignore the Opportunity Contact Roles. In using this parameter, it will be your responsibility to populate the explicit DocuSign Recipient parameters if you want to pre-address the Envelope DocuSignR1 Subject Also available: The parameter with R2, R3, R4, R5 or R6 Because this value is transmitted through the Conga Composer window URL, we recommend that this value be brief (say, not more than 40 characters). Note: This parameter only works when sending a DocuSign Envelope directly via the API using DS7=17 or QMode=7 DocuSignR1 Blurb Also available: The parameter with R2, R3, R4, R5 or R6 Because this value is transmitted through the Conga Composer window URL, we recommend that this value be brief (say, not more than 40 characters). Note: This parameter only works when sending a DocuSign Envelope directly via the API using DS7=17 or QMode=7 DocuSignR1 Langua ge Also available: The parameter with R2, R3, R4, R5 or R6 A 2 or 5-character DocuSign language code: Arabic (ar), Bulgarian (bg), Czech (cs), Chinese Simplified (zh-cn), Chinese Traditional (zh-tw), Croatian (hr), Danish (da), Dutch (nl), English US (en), English UK (en-gb), Estonian(et), Farsi (fa), Finnish (fi), French (fr), French Canada (fr-ca), German (de), Greek (el), Hebrew (he), Hindi (hi), Hungarian (hu), Bahasa Indonesia (id), Italian (it), Japanese (ja), Korean (ko), Latvian (lv), Lithuanian (lt), Bahasa Melayu (ms), Norwegian (no), Polish (pl), Portuguese (pt), Portuguese Brazil (pt-br), Romanian (ro), Russian (ru), Serbian (sr), Slovak (sk), Slovenian (sl), Spanish (es), Spanish Latin America (es-mx), Swedish (sv), Thai (th), Turkish (tr), Ukrainian (uk) and Vietnamese (vi). Note: This parameter only works when sending a DocuSign Envelope directly via the API using DS7=17 or QMode=7 Conga Composer Winter 13 Release Page 62

63 Automatic Role Assignment via Opportunity Contact Roles When using Conga Composer to generate a document from an Opportunity with Contact Roles, Conga Composer will scan the Contacts' role names, and use those values for the DocuSign Recipient role names if the roles exist on the DocuSign Administration Settings. Conga Composer Winter 13 Release Page 63

64 EchoSign Integration Parameters EchoSign delivers Conga Composer documents via , much like Salesforce itself, but adds the ability to acquire, track and file signatures. EchoSign allows you to use PDF forms to collect data from your signers, position signature fields in your documents, collect two-party information from both sender and signer and more. You can add EchoSign-specific form fields to Conga Composer PDF merge templates to enable those features. For more information visit the EchoSign AppExchange listing. EchoSign is available separately on the AppExchange. You must subscribe to that service to use these integration parameters. Setup: After installing EchoSign from the AppExchange, you must modify the EchoSign application by disabling the default value of the Signature Order field: IMPORTANT 1. Edit the Signature Order field by choosing Setup AppSetup Create Objects Agreement Signature Order field 2. In the Picklist Values section, Edit the choice Recipient signs, then I sign 3. Uncheck (disable) Make this value the default for the master picklist 4. Save your changes Each of the following parameters affects the field specified on an EchoSign Agreement record. This integration requires EchoSign for Salesforce, version 6.0. PARAMETER ESVisible=[0 or 1] Makes the EchoSign button visible on the Conga Composer dialog box Note: This parameter is required for all other EchoSign parameters If set to 0, the EchoSign button is not visible (default) If set to 1, the EchoSign button is visible Conga Composer Winter 13 Release Page 64

65 PARAMETER ESAdditionalTo=[text] (deprecated) **Parameter no longer recommended. Use the &ESCopyTo parameter instead.** Sets the value of the Additional Recipients field An address or a field that contains one or more addresses. Example 1: &[email protected] Example 2: &[email protected], [email protected] Example 3: &ESAdditionalTo={!Contact.Other Address} ESAgreementName= [text] Sets the Agreement Name If not set, the agreement name is set to the output file name Example 1:...&ESAgreementName={!Opportunity.AgreementName c} Example 2: &ESAgreementName=Contract+for+{!Account.Name} ESContactId=[id] Sets the value of the Contact field A Salesforce Id of a Contact, or a field that contains the Id of a Contact. If the Conga Composer Master Object is an Opportunity, the Contact field is automatically set to the Primary Contact, without the use of this parameter. If the Conga Composer Master Object is a Quote, the Contact field is automatically set to the Quote's Contact, without the use of this parameter. ** Note: Depending on your EchoSign Agreement Object s Page Layout, this parameter may be required ** Example 1: & ESContactId ={!Contact.Id} Example 2: & ESContactId = dg3C ESContactId1=[id] Also available: ESContactId2, ESContactId3 Sets an Additional Contact field(s) Requires A Salesforce Id of a Contact, or a field that contains the Id of a Contact. ESContractId=[id] Sets the value of the Contract field A Salesforce Id of a Contract, or a field that contains the Id of a Contract. Example 1: & ESContactId ={!Contact.Id} Example 2: & ESContactId = dg3C Conga Composer Winter 13 Release Page 65

66 PARAMETER ESCopyTo=[text] Sets the value of the a Copy To field An address or a field that contains one or more addresses. Example 1: &[email protected] Example 2: &[email protected], [email protected] Example 3: &ESCopyTo={!Contact.Other Address} ESCustomField= [ApiFieldName] Also available: ESCustomField1 ESCustomField2 ESCustomField3 ESCustomField4 ESCustomField5 Sets the name of a custom field to set on the EchoSign Agreement Record created through the merge process. Use the Salesforce API name of the field on the EchoSign Agreement Object. ESCustomFieldValue Example: &ESCustomField=Account c &ESCustomFieldValue=001ABCEDFGHIJL ESCustomFieldValue= [value] Also available: ESCustomFieldValue1 ESCustomFieldValue2 ESCustomFieldValue3 ESCustomFieldValue4 ESCustomFieldValue5 Sets the value of the corresponding custom field ESCustomField ESExpireInXDays= [value] Sets the Expire in X Days EchoSign 9.5+ ESLanguage=[text] Sets the Language field EchoSign 9.5+ ESLeadId=[id] Sets the value of the Lead field A Salesforce Id of a Lead, or a field that contains the Id of a Lead. Example 1: & ESLeadId ={!Lead.Id} Example 2: & ESLeadId =00Q dg3C ESLeadId1=[id] Also available: ESLeadId2, ESLeadId3 Sets an Additional Lead field(s) Requires A Salesforce Id of a Lead, or a field that contains the Id of a Lead. Conga Composer Winter 13 Release Page 66

67 PARAMETER ESMessage=[text] Sets the value of the Message field Example 1: &ESMessage=Please+sign+the+attached+document Example 2: &ESMessage={!Opportunity.AgreementMessage c} Can be populated via a QVar query. ESOpportunityId=[id] Sets the value of the Opportunity field A Salesforce Id of an Opportunity, or a field that contains the Id of an Opportunity. Example 1: & ESOpportunityId ={!Opportunity.Id} Example 2: & ESOpportunityId = dg3C ESPreview=[0 or 1] Sets the Preview Field EchoSign 9.5+ ESRequirePWSign= [0 or 1] Sets the Password Required to Sign field If set to 0, Password Required to Sign is disabled (default) If set to 1, Password Required to Sign is enabled ESRequirePWView= [0 or 1] Sets the Password Required to View field If set to 0, Password Required to View is disabled (default) If set to 1, Password Required to View is enabled ESRequireSelfSign= [0 or 1] Sets the I Also Need To Sign field ESSignatureOrder=[1 or 2] If set to 0, I Also Need To Sign is disabled (default) If set to 1, I Also Need To Sign is enabled ESSignatureType= [0, 1 or 2] Sets the Signature Type If set to 0, Signature Type is not set If set to 1, Signature Type is set to Written Signature If set to 2, Signature Type is set to e-signature ESSignatureOrder= [1 or 2] Sets the Signature Order field. IMPORTANT: Please see the Setup instructions at the beginning of this section. ESRequireSelfSign=1 If set to 1, Signature Order is set to Recipient signs, then I sign If set to 2, Signature Order is set to I sign, then the Recipient signs Conga Composer Winter 13 Release Page 67

68 PARAMETER ESRemindRecipient= [0, 1, 2 or 3] Sets the Remind Recipient to Sign field If set to 0, Remind Recipient is not set If set to 1, Remind Recipient is set to Never If set to 2, Remind Recipient is set to Every Day, Until Signed If set to 3, Remind Recipient is set to Every Week, Until Signed ESRecipient1=[id or address] Also available: The parameter with 2, 3, 4, 5, or 6 More flexible Recipients Allows you to specify the recipients of an EchoSign Agreement using the EchoSign Recipients Related List object. The benefit of using this object rather than the discrete Lookup fields is that you may specify the id of a Contact, User, Lead, Person Account or simply an address as a Recipient. This parameter requires EchoSign version ESSVBA=[0 or 1] Send Via Background Action enhanced automatic delivery When automatically sending an EchoSign Agreement through the API, you may elect to trigger EchoSign's built-in delivery mechanism. This parameter requires that API access is enabled for EchoSign and the EchoSign API Key is entered in EchoSign configuration settings. This parameter works with the &DS7=14 and &DS7Preview=1 parameters but won t work with the &DS7=24 parameter. Enhancement to Remind Recipient It's no longer necessary to use a custom field to enable the EchoSign Automatic Reminders checkbox Composer will populate the field automatically whenever the &ESRemindRecipient parameter is utilized. DS7=4 Background Mode for EchoSign See Conga Composer Background Mode, page 45. DS7=14 Background Mode for EchoSign (automatically-delivered, return to Master Object) See Conga Composer Background Mode, page 45. DS7=24 Background Mode for EchoSign (automatically-delivered, return to Confirmation) See Conga Composer Background Mode, page 45. Control the order in which EchoSign delivers files You can control the order in which EchoSign delivers files for electronic signature by creating a custom Text field (255 characters) on the EchoSign Agreement object with the Salesforce API name "Attachment_Order c". Conga Composer will automatically populate this field with a list of the ids of the attachments generated. EchoSign will deliver the attachments in the order specified. Conga Composer Winter 13 Release Page 68

69 Salesforce Chatter Integration Parameters Conga Composer can store output documents in Salesforce Chatter, rather than as attachments under the Notes & Attachments related list. Conga Composer saves files to Chatter as part of the Activity Logging functions. We recommend the following settings for integrating with Chatter: &LG4=1 (Enables Automatic Logging) &LGAttachOption=2 (Enables File Attachments to log to Chatter) If you wish to override the default behavior where files are saved on the Chatter Feed for the master object, you may use the &AttachmentParentId parameter to identify the record on which the file should be posted. You may set AttachmentParentId to a User Id, Group Id or record Id. PARAMETER LG4=[0, 1 or 2] Automatic Logging Sets whether to automatically log an activity after merging If set to 0, Automatic Logging is disabled (default) If set to 1, Automatic Logging is enabled If set to 2, Master Field to Set fields are automatically updated and no Task record is created LGAttachOption= [0, 1 or 2] Sets the Salesforce object to which attachments generated during Activity Logging are stored If set to 0, attachments are saved to Notes & Attachments (default) If set to 1, attachments are saved to Salesforce Content If set to 2, attachments are saved to Salesforce Chatter LG3=1 or 2 Works with: AttachmentParentId (see below) Conga Composer Winter 13 Release Page 69

70 PARAMETER AttachmentParentId=[id] Specifies the record in Salesforce to which the output file is attached, when requested. In the absence of this parameter, the default attachment parent record is the Master Object. A Salesforce Id of a object to which attachments are allowed. When used with LGAttachOption=2 (Chatter), this parameter may be set to a Chatter User Id or Chatter Group Id. Salesforce Content Integration Parameters Conga Composer can store output documents in Salesforce Content, rather than as attachments under the Notes & Attachments related list. IMPORTANT Setup: We recommend that you create a Lookup Relationship field on Salesforce Content for your Master Object type so that you can relate new Content records to the object from which Conga Composer is initiated. 1. Customize Salesforce Content by choosing Setup Customize Salesforce CRM Content 2. Create a new Lookup Relationship field for the type of field from which Conga Composer will be called 3. Save your changes 4. Refer to this field using the ContentCustomFieldName and ContentCustomFieldValue parameters (see below). You must also specify a ContentWorkspaceId. PARAMETER ContentVisible=[0 or 1] Makes the Salesforce Content button visible on the Conga Composer dialog box. If set to 0, the Salesforce Content button is not visible (default) If set to 1, the Salesforce Content button is visible ContentWorkspaceId= [id] Sets the Salesforce Id of the Content Workspace under which attachments will be stored. A Salesforce Id of a Content Workspace. The Id must begin with the prefix "058". Example: &ContentWorkspaceId=058a ab Conga Composer Winter 13 Release Page 70

71 PARAMETER ContentCustom FieldName=[value] This parameter is displayed above on two lines, but should be on one line in actual use. Sets the name of a custom field to set on the Salesforce Content Record created through the merge process. Use the Salesforce API name of the field on the Salesforce Content Object. ContentWorkspaceId ContentCustomFieldValue Example: &ContentCustomFieldName=Account c &ContentCustomFieldValue=001ABCEDFGHIJL ContentCustom FieldValue=[value] This parameter is displayed above on two lines, but should be on one line in actual use. Sets the value of the corresponding custom field ContentCustomFieldName DefaultPane=[0 or 1] Sets Salesforce Content as the default option in the Select Templates view of the Composer dialog box If set to 0, Conga Templates is the default option (default) If set to 1, Salesforce Content & Documents is the default option &SelectTemplates=1 DS7=6 Background Mode to Salesforce Content If set to 6, Background Mode is enabled and the merged document is attached to Salesforce Content See Conga Composer Background Mode, page 45. HideContent=[0 or 1] Suppresses Salesforce Content from being displayed in the Select Templates view of the Composer dialog box If set to 0, Salesforce Content & Documents is visible (default) If set to 1, Salesforce Content & Documents is not displayed &SelectTemplates=1 LGAttachOption= [0, 1 or 2] Sets the Salesforce object to which attachments generated during Activity Logging are stored If set to 0, attachments are saved to Notes & Attachments (default) If set to 1, attachments are saved to Salesforce Content If set to 2, attachments are saved to Salesforce Chatter Works with: AttachmentParentId (see below) Conga Composer Winter 13 Release Page 71

72 PARAMETER LGContentEnabled= [0 or 1] Do not use. Replaced with LGAttachOption. Indicates whether Activity Logging should attach files to Salesforce Content If set to 0, files attached as a result of Activity Logging are stored in Notes & Attachments (default) If set to 1, files attached as a result of Activity Logging are stored in Salesforce Content Note: ContentWorkspaceId, ContentCustomFieldName and ContentCustomFieldValue are also used in conjunction with this setting. Conga Composer Winter 13 Release Page 72

73 SendGrid Integration Parameters SendGrid is an delivery service with features that assure customers an extremely high deliverability rate at a low cost. Delivering s via SendGrid means customers can circumvent Salesforce limits and can still use Salesforce templates. SendGrid is available separately from their website. You must subscribe to that service to use this integration. Setup: IMPORTANT 1. Subscribe to a plan on the SendGrid website. Configure your SendGrid account according to their instructions. 2. Open the Conga Setup page (located on the lower-right corner of the Conga Composer dialog box). On the "Integration Partners" tab, paste your SendGrid username and password. The credentials are encrypted and stored securely. 3. Save your changes. 4. Once Conga is configured with your SendGrid credentials, all generated through Conga will be delivered via SendGrid. Conga Composer will automatically create a completed Task record for each sent through SendGrid. From the Conga Composer dialog box, when the button is clicked, Conga Composer generates the output document (as usual) and then presents a editable , pre-addressed to the address configured in the Conga Composer button. Conga Composer's Parameters work with SendGrid. Tip! While Salesforce templates generally work with SendGrid, we don't recommend the use of Salesforce Letterhead templates. Instead, you may configure a SendGrid Template (from their website) to achieve the same result as a Salesforce Letterhead template. In other words, use either a SendGrid Template (recommended) or a Salesforce template, not both. Conga Composer Winter 13 Release Page 73

74 Sertifi Integration Parameters Sertifi delivers Conga Composer documents via , much like Salesforce itself, but adds the ability to acquire, track and file signatures. You can learn more about Sertifi for Salesforce here: Sertifi is available separately on the AppExchange. You must subscribe to that service to use this integration parameter. PARAMETER SertifiVisible=[0 or 1] Makes the Sertifi button visible on the Conga Composer dialog box. If set to 0, the Sertifi button is not visible (default) If set to 1, the Sertifi button is visible Sertifi To=[text] Sets the value of the recipient of the document to be delivered via Sertifi An address or a field that contains one or more addresses. SertifiSigner2 =[Em ail address] Specify more recipients Use this parameter to specify the Signer2 address SertifiCCSigner =[E mail Address] Use this parameter to specify the CC Signer address Automatic inclusion of the Composer attachment in the outbound Sertifi The latest version of Sertifi will automatically pre-select the file created by Composer for a Sertifi message Conga Composer Winter 13 Release Page 74

75 SpringCM Integration Parameters SpringCM provides secure file sharing, document management, and collaboration services, making it easy to add, find, share, and manage content directly from standard or custom objects in salesforce.com. You can learn more about SpringCM on their website. SpringCM is available separately from the Salesforce AppExchange. You must subscribe to that service to use this integration. PARAMETER SCMVisible=[0 or 1] Makes the SpringCM button visible on the Conga Composer dialog box If set to 0, the SpringCM button is not visible (default) If set to 1, the SpringCM button is visible DS7=8 Background mode is enabled and the merged document is saved in a SpringCM folder, as defined by the SpringCM configuration rules LGAttachOption=3 Attaches a copy of the merged document to a SpringCM folder, as defined by the SpringCM configuration rules LG4=1 Frequently used in conjunction with the &LG3=2 parameter. Also works with the &LGAttachmentParentId parameter. Conga Composer Winter 13 Release Page 75

76 Advanced Parameters The Advanced Parameters Group lists parameters that are used less frequently in Conga solutions, however, they provide invaluable functionality. These parameters affect: Advanced Data Gathering Advanced Template Selection Advanced Data Formatting Advanced Dialog Box Restrictions Formula-Driven Parameters Advanced Data Gathering Parameters PARAMETER DV0=[value] Also available: DV1, DV2 The DataValue parameters insert a value into the Master data set without requiring a custom field in Salesforce. Example: &DV0=Draft+Document In this example, a column for DV0 would appear on the Master dataset as seen on the Template Builder window. This value could be displayed in a watermark or page header on a Word template. Conga Composer Winter 13 Release Page 76

77 PARAMETER QVar0Id=[id] and {QVar0} Also available: QVar1Id, QVar2Id QVar, which stands for Querystring Variable, lets you execute a Conga Query and use the result of the query as a value for another Conga Composer parameter. A 15-character Salesforce Id of a Query record. May optionally include filter criteria. Usage Guidelines: Set QVar0Id to the Salesforce Id of a Conga Query record. Optionally, you may pass filter criteria to the Query. See #2 below for an example. The Conga Query must return only one column of data and must not retrieve more than 50 rows of data. Multiple rows of data are returned as a comma-separated list. In another Conga Composer parameter, indicate where you want to insert the QVar0 result with "{QVar0}" (no quotes). The resulting values for all QVar variables appear on the Template Builder window. The resulting value may be inserted into most Conga Composer parameters, but not all. Most importantly, it can be included in ReportId, QueryId, TemplateId, TemplateGroup and the parameters. The duplicate values are automatically stripped from the resulting data. Not recommended for retrieving date values. Not for use with the SelectTemplates parameter May be used with MFTSValue parameter Example: Say you wanted to look up the Id for an Account's Primary Contact and use the Id in the ToId parameter. You could accomplish this by following these steps: 1. Create a Conga Query to retrieve the desired data and copy its Salesforce Id to the clipboard. 2. Reference the Conga Query by including &QVar0Id=QueryId: &QVar0Id=a ?pv0={!Account.Id} 3. Pass the QVar result into the ToId parameter: & ToId={QVar0} Conga Composer Winter 13 Release Page 77

78 PARAMETER QVar0Format=[code] Also available: QVar1Format, QVar2Format Formats the result of a QVar query. The [code] value follows the convention below. Code: [#][#][#][#][#] A B C D E A = Delimiter between data elements [0=none, 1=comma, 2=pipe, 3=semi-colon, 4=colon, 5=hyphen] ( 2-Pipe is useful for delimiting values that are passed to a Report) B = Symbol to enclose each data element [0=none, 1=apostrophes, 2=quotes] C = Symbol after delimiter [0=none, 1=space] D = Truncate each data element to 15-characters [0=off, 1=on] (Useful when passing values to a Salesforce Report) E = Reserved for future use Example: Your Conga Query pulls 18-character IDs that you want to pass to a Report as the pv0 value. The Format Code you would use is 20010, which would indicate: 2 = Separate with Pipes 0 = No symbol to enclose each data element 0 = No space between elements 1 = Truncate to 15 characters 0 = Unused The parameter would be included in the button as: &QVar0Format=20010 ReportVar=[value] Placeholder to represent a value passed to multiple reports, thereby resulting in a shorter overall URL length At least two ReportId values Example: &ReportVar=California New+York New+Jersey &ReportId=00O ?pv0={ReportVar}, 00O ?pv0={ReportVar}, 00O ?pv0={ReportVar} In this example, the value of ReportVar ( California New+York New+Jersey ) would be passed to each report s selection criteria. Note the placement of {ReportVar} to indicate where to insert the value. Conga Composer Winter 13 Release Page 78

79 PARAMETER XMD=[0 or 1] Excludes the master object data from being included in the merge process If set to 0, the master data is included in the merge process (default) If set to 1, the master data is excluded from the merge process Applicable only when using exactly one Report as the only data source. The benefit of using this parameter is that in a Word Template, you do not need to use region tags (<<TableStart:ReportData>>), simply place the ReportData fields wherever you like on the template, as though they were Master fields. (See Designing Microsoft Word Merge Templates, Chapter 4). Conga Composer Winter 13 Release Page 79

80 Advanced Template Selection Parameters The following parameters pertain to merge templates. PARAMETER DefaultLocal=[0 or 1] Sets the default source for a template to the user s local computer If set to 0, default template source is set to Choose a template from Salesforce.com If set to 1, default template source is Choose a template from your local computer Setup options configured to allow Local Templates. (See Appendix) DS4=[0 or 1] Lock Template Choices If set to 0, the list of template choices is not locked (default) If set to 1, the selected template choice is locked TemplateId parameter must be set In the absence of this parameter, the template indicated by the TemplateId parameter is pre-selected in the list, but the user may select a different template. This parameter prevents the user from selecting a different template. TNC=[value] Filters the list of templates at appear on the Conga Composer page to those that match this criteria. (The parameter means "Template Name Contains".) Tips: This parameter works with templates stored either in the Conga Template Manager or Communication Templates This parameter works in conjunction with TemplateGroup ZipPDFs=[0 or 1] In a multiple-template merge, indicates that output PDF files should be zipped rather than assembled into a single (large) PDF. Multiple Template Ids specified Output format set to Adobe PDF (DefaultPDF=1) Conga Composer Winter 13 Release Page 80

81 Advanced Data-Formatting Parameters Primarily used for international scenarios, these parameters affect the appearance of number and date values in Microsoft Word templates. Please note: these options override default data formatting options and are generally not necessary for most users. PARAMETER CurrencyCulture=[code] Overrides the default cultural settings for currency formatting. Useful in Word templates that format currency fields with the \# Currency picture switch (see Designing Microsoft Word Merge Templates, chapter 4). A 5-character code (2 lowercase letters, a hyphen, followed by 2 uppercase letters). The code denotes a language/country pair. The first two letters indicate the language, the last two indicate the country. Example codes: de-de en-gb en-us es-es German/Germany - Euros English/Great Britain British Pounds English/United States Dollars Spanish/Spain Euros See the complete list of language/country codes. Example 1: &CurrencyCulture=de-DE This code would specify that the culture is for German/Germany. For Word merge fields that use the \# Currency picture switch, the currency values would automatically be formatted as Euros. Example 2: (using a field to control Culture)..&CurrencyCulture={!Contact.Culture} Culture=[code] Overrides the default cultural settings for currency and date formatting. Useful in Word templates that format currency fields with \# Currency picture switch (see Designing Word Templates). Exactly the same as CurrencyCulture, but affects date as well as currency formatting. See the complete list of language/country codes. TPV=[0 or 1] Translate Picklist Values For organizations where picklist values have been translated via the Translation Workbench, this setting enables Conga Composer to retrieve the translated values. This parameter does not work with SOQL queries; use To Label() on the picklist field instead. If set to 0, picklist values are not translated (default) If set to 1, picklist values are translated to the language specified in the User s Personal Information settings Conga Composer Winter 13 Release Page 81

82 FAQ: Formatting currency values on a record-by-record basis Let s say we re creating a quote from an Opportunity and we d like format currency values based on a field in the Opportunity. Here s how: 1. Create a picklist field on the Opportunity to contain the culture choices. Let s call the field Culture. In this example, let s use the following choices: 2. Insert the CurrencyCulture parameter into the Conga Composer URL: &CurrencyCulture={!Opportunity.Culture} 3. Format the currency fields in your Word template using the \# Currency picture switch: { MERGEFIELD Opportunity_LineItem_SalesPrice \# Currency } These settings would result in output such as: Tip! Disable Wrap Text in cells that use Currency formatting to keep the value and the symbol on the same line. Table Table Properties Cell Options, then uncheck Wrap Text. Conga Composer Winter 13 Release Page 82

83 Advanced Control Parameters PARAMETER DC=[0 or 1] Disable Conga Execution This parameter is usually set a part of a Salesforce formula to evaluate the contents of a field and, in turn, prevent the execution of Conga if the field doesn't meet some criteria. Example: DC={!IF(Opportunity.StageName = "Closed Won", "0", "1") } DCL=[text] Disable Conga Execution Label Displays a message on the Conga Composer dialog box when "Disable Conga Exeuction" is enabled. Displays up to 50 characters. DC=1 (Disable Conga Execution) Example 1: &DCL =Required+fields+have+not+been+set EC=[0 or 1] Enable Conga Execution This parameter is usually set a part of a Salesforce formula to evaluate the contents of a field and, in turn, enable the execution of Conga if the field meets some criteria. Example: EC={!IF(Opportunity.StageName = "Closed Won", "1", "0") } ECL=[text] Enable Conga Execution Label Displays a message on the Conga Composer dialog box when "Enable Conga Execution" is disabled. Displays up to 50 characters. EC=0 (Enable Conga Execution) Example 1: &ECL =Required+fields+have+not+been+set OCNR=[0 or 1] On-Close, No Refresh Disables the default behavior when the Close button is clicked. By default, the Salesforce record is refreshed when Close is clicked. If set to 0, the Salesforce record is refreshed (default) If set to 1, the Salesforce record is not refreshed Conga Composer Winter 13 Release Page 83

84 Formula-Driven Parameters Rather than defining a parameter with a particular value, you can use Salesforce formulas to provide a limited amount of dynamic flexibility to your Conga Composer URLs. Example: Say you d like users of a particular profile to always generate PDFs from Conga Composer, whereas users of other profiles may choose whether to use the native file format or PDFs. You could accomplish this by using a formula to control the behavior of the fp0 parameter. In this example, after the base URL (gray), we ve enabled the Default PDF parameter and made the Force PDF parameter (fp0) dynamic, based on the user s Profile. For System Administrators, fp0 is disabled. For others, fp0 is enabled. &serverurl={!api.partner_server_url_210} &id={!contact.id} &DefaultPDF=1 &FP0={!IF( $Profile.Name = "System Administrator", "0", "1")} Tip! In practice, we would recommend using an Id, such as $Profile.Id, rather than a text string, such as the Profile Name. Tip! You can learn more about the Salesforce formula language by searching for Operators and Functions in the Salesforce.com online help. Conga Composer Winter 13 Release Page 84

85 Conga Composer URL Examples Sometimes it s helpful to see a complete Conga Composer URL to fully comprehend how to assemble various parameters. Here are three examples. Example 1 In addition to the base URL (the gray text), this example enables PDF encryption (ps0=1) and PDF printing (ps1=1). Next, it disables the Log Activity button (ds3=1), sets the template (TemplateId) and locks the template choice (ds4=1). &ServerUrl={!API.Partner_Server_URL_210} &Id={!Contact.Id } &PS0=1 &PS1=1 &DS3=1 &TemplateId= FB &DS4=1 Example 2 The next example demonstrates the use of multiple reports. After the base URL, we ve included four reports (ReportId), specified a template (TemplateId) and the To field ( ToId) &ServerUrl={!API.Partner_Server_URL_210} &Id={!Contact.Id} &ReportID=00O NGuW, 00O O2gr, 00O NGv5, 00O NGvL &TemplateId=01H z4L & toID={!Contact.Id} Example 3 The final example demonstrates the use of Background Mode. After the base URL, we ve included a report (which is filtered by the Account ID), specified a template (TemplateId), enabled the Background Mode that attaches the document (ds7=1) and forced the output to Adobe Acrobat (fp0=1). &ServerUrl={!API.Partner_Server_URL_210} &Id={!Opportunity.Id} &ReportId=00O OAA2?pv0={!Opportunity.AccountId} &TemplateId=01H xop &DS7=1 &FP0=1 Conga Composer Winter 13 Release Page 85

86 5. Conga Template Manager The Conga Template Manager custom object is a significant addition to Conga Composer. With this new custom object, you can create Conga Templates that work a lot like Conga Composer templates built in Microsoft Word. For more information about designing Conga Templates, please see Conga Templates. Conga Composer Winter 13 Release Page 86

87 6. Know Your Limits Conga Composer Limits per Solution Maximum Queries 50 Reports 50 Lines of Data in a Report 1,500 Rows or 5 MB per merge Columns per Tab in View Data workbook 256 Dataset 25,000 total rows Qvar 50 rows of data Number of Templates per operation 10 Template Size 5 MB Conga Mail Merge Limits Output File Size Reports Template Size Conga Query Limits Aggregate SOQL (SUM, COUNT, etc.) Conga Conductor Limits Conga Conductor, per batch process Conga Workflow Limits Conga Workflow Maximum 40 Mb 5k 5 Mb Maximum 200 category values Maximum 50 records for consolidated output. 500 records for distributed output. Maximum 500 transactions per day Conga Courier Limits Maximum Conga Courier Schedules 200 Contacts as recipients for a Courier 25 Schedule Output file size 5 MB Browser URL Limits Internet Explorer Chrome, Firefox, Safari Maximum 2000 bytes (closer to 1,700 bytes in practice) 64,000 bytes Conga Composer Winter 13 Release Page 87

88 7. Other Parameters Supported Culture Codes English Name Abbreviation 1. Afrikaans (South Africa) af-za 2. Albanian (Albania) sq-al 4. Amharic (Ethiopia) am-et 5. Arabic (Algeria) ar-dz 6. Arabic (Bahrain) ar-bh 7. Arabic (Egypt) ar-eg 8. Arabic (Iraq) ar-iq 9. Arabic (Jordan) ar-jo 10. Arabic (Kuwait) ar-kw 11. Arabic (Lebanon) ar-lb 12. Arabic (Libya) ar-ly 13. Arabic (Morocco) ar-ma 14. Arabic (Oman) ar-om 15. Arabic (Qatar) ar-qa 16. Arabic (Saudi Arabia) ar-sa 17. Arabic (Syria) ar-sy 18. Arabic (Tunisia) ar-tn 19. Arabic (U.A.E.) ar-ae 20. Arabic (Yemen) ar-ye 21. Armenian (Armenia) hy-am 22. Assamese (India) as-in 25. Bashkir (Russia) ba-ru 26. Basque (Basque) eu-es 27. Belarusian (Belarus) be-by 28. Bengali (Bangladesh) bn-bd 29. Bengali (India) bn-in 32. Breton (France) br-fr 33. Bulgarian (Bulgaria) bg-bg 34. Catalan (Catalan) ca-es 35. Chinese (Hong Kong zh-hk S.A.R.) 36. Chinese (Macao S.A.R.) zh-mo 37. Chinese (People's Republic zh-cn of China) 38. Chinese (Singapore) zh-sg 39. Chinese (Taiwan) zh-tw 40. Corsican (France) co-fr 41. Croatian (Croatia) hr-hr 42. Croatian (Latin) (Bosnia hr-ba and Herzegovina) 43. Czech (Czech Republic) cs-cz 44. Danish (Denmark) da-dk 45. Dari (Afghanistan) prs-af 46. Divehi (Maldives) dv-mv 47. Dutch (Belgium) nl-be 48. Dutch (Netherlands) nl-nl 49. English (Australia) en-au 50. English (Belize) en-bz 51. English (Canada) en-ca 52. English (Caribbean) en-029 English Name Abbreviation 53. English (India) en-in 54. English (Ireland) en-ie 55. English (Jamaica) en-jm 56. English (Malaysia) en-my 57. English (New Zealand) en-nz 58. English (Republic of the en-ph Philippines) 59. English (Singapore) en-sg 60. English (South Africa) en-za 61. English (Trinidad and en-tt Tobago) 62. English (United Kingdom) en-gb 63. English (United States) en-us 64. English (Zimbabwe) en-zw 65. Estonian (Estonia) et-ee 66. Faroese (Faroe Islands) fo-fo 68. Finnish (Finland) fi-fi 69. French (Belgium) fr-be 70. French (Canada) fr-ca 71. French (France) fr-fr 72. French (Luxembourg) fr-lu 73. French (Principality of fr-mc Monaco) 74. French (Switzerland) fr-ch 75. Frisian (Netherlands) fy-nl 76. Galician (Galician) gl-es 77. Georgian (Georgia) ka-ge 78. German (Austria) de-at 79. German (Germany) de-de 80. German (Liechtenstein) de-li 81. German (Luxembourg) de-lu 82. German (Switzerland) de-ch 83. Greek (Greece) el-gr 84. Greenlandic (Greenland) kl-gl 85. Gujarati (India) gu-in 87. Hebrew (Israel) he-il 88. Hindi (India) hi-in 89. Hungarian (Hungary) hu-hu 90. Icelandic (Iceland) is-is 91. Igbo (Nigeria) ig-ng 92. Indonesian (Indonesia) id-id 95. Irish (Ireland) ga-ie 96. isixhosa (South Africa) xh-za 97. isizulu (South Africa) zu-za 98. Italian (Italy) it-it 99. Italian (Switzerland) it-ch 100. Japanese (Japan) ja-jp 101. Kannada (India) kn-in 102. Kazakh (Kazakhstan) kk-kz 103. Khmer (Cambodia) km-kh Conga Composer Winter 13 Release Page 88

89 English Name Abbreviation 105. Kinyarwanda (Rwanda) rw-rw 106. Kiswahili (Kenya) sw-ke 108. Korean (Korea) ko-kr 109. Kyrgyz (Kyrgyzstan) ky-kg 110. Lao (Lao P.D.R.) lo-la 111. Latvian (Latvia) lv-lv 112. Lithuanian (Lithuania) lt-lt 114. Luxembourgish lb-lu (Luxembourg) 115. Macedonian (Former mk-mk Yugoslav Republic of Macedonia) 116. Malay (Brunei ms-bn Darussalam) 117. Malay (Malaysia) ms-my 118. Malayalam (India) ml-in 119. Maltese (Malta) mt-mt 120. Maori (New Zealand) mi-nz 121. Mapudungun (Chile) arn-cl 122. Marathi (India) mr-in 126. Nepali (Nepal) ne-np 127. Norwegian, Bokmål nb-no (Norway) 128. Norwegian, Nynorsk nn-no (Norway) 129. Occitan (France) oc-fr 130. Oriya (India) or-in 131. Pashto (Afghanistan) ps-af 132. Persian (Iran) fa-ir 133. Polish (Poland) pl-pl 134. Portuguese (Brazil) pt-br 135. Portuguese (Portugal) pt-pt 136. Punjabi (India) pa-in 140. Romanian (Romania) ro-ro 141. Romansh (Switzerland) rm-ch 142. Russian (Russia) ru-ru 146. Sami (Northern) (Finland) se-fi 147. Sami (Northern) (Norway) se-no 148. Sami (Northern) (Sweden) se-se 152. Sanskrit (India) sa-in 158. Setswana (South Africa) tn-za 159. Sinhala (Sri Lanka) si-lk 160. Slovak (Slovakia) sk-sk 161. Slovenian (Slovenia) sl-si 162. Spanish (Argentina) es-ar 163. Spanish (Bolivia) es-bo English Name Abbreviation 164. Spanish (Chile) es-cl 165. Spanish (Colombia) es-co 166. Spanish (Costa Rica) es-cr 167. Spanish (Dominican es-do Republic) 168. Spanish (Ecuador) es-ec 169. Spanish (El Salvador) es-sv 170. Spanish (Guatemala) es-gt 171. Spanish (Honduras) es-hn 172. Spanish (Mexico) es-mx 173. Spanish (Nicaragua) es-ni 174. Spanish (Panama) es-pa 175. Spanish (Paraguay) es-py 176. Spanish (Peru) es-pe 177. Spanish (Puerto Rico) es-pr 178. Spanish (Spain) es-es 179. Spanish (United States) es-us 180. Spanish (Uruguay) es-uy 181. Spanish (Venezuela) es-ve 182. Swedish (Finland) sv-fi 183. Swedish (Sweden) sv-se 187. Tamil (India) ta-in 188. Tatar (Russia) tt-ru 189. Telugu (India) te-in 190. Thai (Thailand) th-th 191. Tibetan (People's Republic bo-cn of China) 192. Turkish (Turkey) tr-tr 193. Turkmen (Turkmenistan) tk-tm 194. Uighur (People's Republic ug-cn of China) 195. Ukrainian (Ukraine) uk-ua 197. Urdu (Islamic Republic of ur-pk Pakistan) 200. Vietnamese vi-vn (Vietnam) 201. Welsh (United cy-gb Kingdom) 202. Wolof (Senegal) wo-sn 204. Yi (People's Republic ii-cn of China) 205. Yoruba (Nigeria) yo-ng Conga Composer Winter 13 Release Page 89

90 8. Index of Conga Composer Parameters APF AttachmentParentId... 42, 52, 70 AWD... 53, 57 BML Conga TemplateGroup Conga TemplateId ContentCustomFieldName ContentCustomFieldValue ContentVisible ContentWorkspaceId Culture CurrencyCulture DC DCL DefaultLocal DefaultPane DefaultPDF DocuSignCustomField DocuSignCustomFieldValue DocuSign Body DocuSign Subject DocuSignEndpoint DocuSignExpireIn DocuSignIgnoreOCR DocuSignR1AccessCode DocuSignR1Id DocuSignR1Role DocuSignR1RoutingOrder DocuSignR1Type DocuSignRelatedAccountId DocuSignRemindAgainIn DocuSignRemindIn DocuSignSendReminders DocuSignTag DocuSignVisible DocuSignWarnIn DS DS DS DS DS , 80 DS DS DS , 47, 68, 71, 75 DS7Preview DS DS DV EC ECL AdditionalTo BCC CC FromId RelatedToId ReplyToId Subject TemplateAttachments TemplateId ToId UseSignature ESAdditionalTo ESAgreementName ESContactId ESContactId ESContractId ESCopyTo ESCustomField ESCustomFieldValue ESExpireInXDays ESLanguage ESLeadId ESLeadId ESMessage ESOpportunityId ESPreview ESRecipient ESRemindRecipient ESRequirePWSign ESRequirePWView ESRequireSelfSign ESSignatureOrder ESSignatureType ESSVBA ESVisible ExcelAutoFitColumns ExcelAutoFitRows FlattenPDFForms FP , 51 HideContent Id LG LG LG LG LG , 69 LG LG LG LGAttachOption... 42, 69, 71, 75 LGParentId LGWhoId MFTS MFTSId MFTSValue MTOFN OCNR OFN PPTPreserveRows PS PS PS PS PSPW QueryId QVar0Format QVar0Id ReportId ReportVar SCHP SCMVisible SelectTemplates SertifiCCSigner Sertifi To SertifiSigner SertifiVisible Conga Composer Winter 13 Release Page 90

91 TemplateGroup TemplateId TNC TPV WPD XMD ZipPDFs Conga Composer Winter 13 Release Page 91