introducing point merge

© 2006 – 2010 AppExtremes Inc.. All rights reserved. This document may be reprinted without permission. Conga Composer is a trademark of AppExtremes, Inc. Salesforce.com is a registered trademark of salesforce.com, and AppExchange, is a trademarks of salesforce.com, Inc., San Francisco, California. Other names used may be trademarks of their respective owners.

AppExtremes, Inc.

[email protected]

Conga Composer Introducing PointMerge

Winter '11 Release

Welcome

Conga Composer lets you generate documents and spreadsheets by gathering data from

Salesforce.com and merging to a template. The resulting file(s) can be printed or emailed

and you can log the actions you’ve taken in Salesforce.

Most Composer solutions utilize PointMerge to let you create individual documents by

clicking a button from a record in Salesforce.

Contacting AppExtremes

AppExtremes is a leading provider of software solutions to enrich your Salesforce.com

experience, specializing in document creation tools that integrate data from Salesforce.

Founded in 2006, AppExtremes has since built a substantial market presence with more than

1,000 customers, worldwide.

Technical Support

At AppExtremes, we are committed to providing you with timely answers to your technical

support questions. We provide support to system administrators for our products via email or

telephone. Generally, we’re available weekdays, 8:00am to 5:00pm Mountain (GMT -7:00).

Tech Support Email: Telephone:

[email protected] +1 303-465-1616

Sales

For information on other products from AppExtremes, please contact our sales department:

Sales Information Email: Telephone:

[email protected] +1 303-465-1616

Examples

For detailed examples, including sample templates, report designs and sample output, please

download the Conga Examples file. You will find the example files on our website.

http://www.appextremes.com/Conga/Conga_Examples.zip

Table of Contents

Welcome ............................................................................................................ 1

Contacting AppExtremes .................................................................................... 1 Technical Support ...................................................................................................... 1 Sales ....................................................................................................................... 1

Examples ............................................................................................................ 1

PointMerge ......................................................................................................... 3 What is PointMerge? ................................................................................................... 3 Create a PointMerge button ......................................................................................... 4

Create the button ............................................................................................ 4 Adjust the Window Open Properties ................................................................... 5 Add the button to a Page Layout ....................................................................... 6

Gather Salesforce Data ............................................................................................... 7 FAQ: What fields are available for merging? ........................................................ 8 FAQ: What if I need data from an object related to the Master Object? ................. 10 Using Salesforce Reports with PointMerge ......................................................... 11 Using Conga Queries with PointMerge .............................................................. 24 Create and Store a Merge Template ................................................................. 25

Refine PointMerge Solutions with Parameters ............................................................... 26 Data-Gathering Parameters ............................................................................ 27 Data-Formatting Parameters ........................................................................... 30 Template Parameters ..................................................................................... 32 Email Parameters .......................................................................................... 35 Security Parameters ...................................................................................... 38 Activity Logging Parameters............................................................................ 41 Output Parameters ........................................................................................ 43 PDF (Output) Parameters ............................................................................... 45 Excel Parameters .......................................................................................... 46 PowerPoint Parameters .................................................................................. 46 Formula-Driven Parameters ............................................................................ 47 DocuSign Integration Parameters .................................................................... 48 EchoSign Integration Parameters ..................................................................... 50 Sertifi Integration Parameters ......................................................................... 54 Salesforce Content Integration Parameters ....................................................... 55 PointMerge URL Examples .............................................................................. 57

Conga Winter '11 Release

PointMerge

What is PointMerge?

PointMerge lets you to create an individual document from a button or link placed on a

standard or custom object page layout. With PointMerge, 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 or PDF template.

This chapter provides guidance on building PointMerge solutions that leverage Salesforce

Reports as a data source. The following illustration depicts a common business scenario in

which PointMerge retrieves data from multiple reports to produce a sophisticated document.

INTRODUCING POINTMERGE

Create a PointMerge button

Create the button

You’ll need to create a button (or link) from which you will invoke PointMerge.

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 PointMerge Base URL:

https://www.appextremes.com/apps/Conga/PointMerge.aspx

?SessionId={!API.Session_ID}

&ServerUrl={!API.Partner_Server_URL_80}

&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 must not contain spaces, particularly at the ends of lines

7. Click Save.

Tip! PointMerge will retrieve all fields from the Master Object,

automatically making them available for merging.


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 Width to 625

5. Set the Height to 450

6. Clear all checkboxes

7. Click Save


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 PointMerge in action!

Watch a Video

This video demonstrates how to create a basic PointMerge button

http://www.youtube.com/watch?v=ZEAMET5fKJ4&hd=1


Gather Salesforce Data

The process of gathering the correct data from Salesforce is iterative. Generally, you start by

examining the fields that PointMerge has automatically retrieved. If those fields are sufficient

for your solution, you’re ready to move on to building your template.

If not, you’ll need to add as many Reports or Queries necessary to retrieve whatever data is

required for your solution.

How do you know which fields are available to you? To answer that question, let’s discover

the power of the View Data link.

(2)

Add or modify

Salesforce

Reports

(3)

Modify

PointMerge

Button

URL

(1)

Examine

View Data

Workbook


FAQ: What fields are available for merging?

An essential tool in the development of Conga Composer solutions is the View Data link. The

View Data link is located at the lower-left corner of the PointMerge page. (We’ll refer to the

link simply as “View Data” from here on.)

Tip! You’ll use View Data frequently in the upcoming sections.

View Data exposes the data retrieved by PointMerge from the Master Object, and from any

Salesforce Reports or Conga Queries referenced in the PointMerge URL. (Conga Reports and

Queries are described later in this chapter.)

PointMerge assembles the data and presents it in an Excel workbook. Each dataset comprises

a sheet within the workbook. For example, this workbook has many related datasets:

The column headers (row 1) in each sheet indicate the field names you must use in your

templates.

Tip! Locate fields quickly within the View Data workbook by using Excel’s Find command,

Edit | Find. Use it to look for known field values, thus revealing the Salesforce field name.

Then click the column header and copy it to the clipboard so you can use it when creating a

field in your template.

Tip! Since Conga Composer displays data across several sheets, when using Excel’s Find

command, you may find it helpful to search the entire workbook.

Choose Edit | Find, Options, then Within Workbook.

Tip! If an Opportunity is your Master Object, PointMerge will automatically make the

Opportunity Line Items available for merging on the OppLineItems sheet.

Tip! If an Real-Time Quote is your Master Object, PointMerge will automatically make the

Quote Line Items available for merging on the QuoteLineItems sheet.


Tip! Excel will display up to 256 columns in a sheet. If your dataset has more than 256

columns, it will be represented on multiple sheets in the View Data workbook.

Tip! The User and Org sheets appear only if “Track Activities”

is enabled for the Master Object


FAQ: 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 PointMerge 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.


Using Salesforce Reports with PointMerge

You can use a Salesforce report to retrieve data related to your Master Object. PointMerge

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.)

Example:

Let’s say your PointMerge 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 PointMerge

button and place it on

your Account page layout

2. Create a report based on

“Contacts & Accounts”

3. On the Select Columns

step, choose the columns

you’re interested in

4. On the Select Criteria

step, set the following:

a. Standard Filters: View drop-down list to All Accounts

b. Standard Filters: Clear any values in Start Date and End Date

c. Advanced Filters: Field drop-down list to Account Id

5. Save the report into any publicly accessible folder. (See “Best Practice: Report Naming

Conventions” for advice about report names and folders.)

This report is now ready to receive the Master Object Id (which is the Account Id) from

PointMerge. Next, we’ll explore how to include the report in the PointMerge button.

PointMerge filters the report by passing the Master Object Id into the first cell of the Value column in the Advanced Filters when the merge begins


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 PointMerge report to pull only

the objects and fields necessary.

Tip! PointMerge will retrieve reports with

a maximum of 1,500 rows and may not

contain more than 5 Mb of data.

Tip! If you include an Id column in your report,

position it as the last column.

Referencing the Report in the PointMerge button

To include the new report in the PointMerge 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 PointMerge 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 PointMerge button, click the PointMerge button and then

click the View Data link to test whether PointMerge has retrieved the correct data.

Tip! You may use up to 50 reports as you like in a PointMerge 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 PointMerge button

http://www.youtube.com/watch?v=R4fuGPo9BjE&hd=1

http://www.youtube.com/watch?v=R4fuGPo9BjE&hd=1


FAQ: How can I filter the report on something other than the Master Object Id?

Although PointMerge 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 PointMerge button to send the desired value

Configure your report to receive some other field value:

1. Edit the report

2. On the Select Criteria step, 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 PointMerge button to send the desired value:

1. Edit the PointMerge 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=00O50000001LNBd?pv0={!Account.BillingState}

Tip! When including a ?pv0= parameter, the “pv” must be lower-case.

Tip! Don’t use fields that might contain commas or ampersands to filter reports.

Best practice: Use Id fields to ensure correct results.


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.


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 PointMerge button URL would need to be:


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

PointMerge button:


FAQ: My report already has filter criteria under Advanced Filters. Can

PointMerge filter the report using subsequent rows in Advanced Filters?

Yes. If you want PointMerge 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 PointMerge to supply filter criteria for the second row (pv1). You

could specify that as:

&ReportId=00O5000000001LNBd?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=00O5000000001LNBd?pv0=


FAQ: How can I gather data from multiple reports?

You may include up to 50 ReportId parameters in a PointMerge 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 PointMerge configured to pull data from four reports:


?SessionID={!API.Session_ID}

&ServerURL={!API.Partner_Server_URL_80}

&Id={!Contact.Id}

&ReportID=00O50000001NGuW,

00O50000001O2gr,

00O50000001NGv5?pv1={!Contact.MailingState},

00O50000001NGvL

Each of these reports would be visible through the View Data worksheet as a separate tab.

Conga Composer automatically assigns the worksheet names based on the sequence of

report IDs included in a PointMerge URL.


FAQ: How can I control the sort-order of the data retrieved from a report?

You can control the sort-order of the information PointMerge 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 PointMerge 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.


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. PointMerge 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 View Data

workbook:

Tip! Conga will automatically retrieve the line items from a Real-Time Quote record, too.


Best Practice: Report Naming Conventions

When naming reports created for use with PointMerge, we suggest you adopt a naming

convention that reflects

The PointMerge solution the reports are intended to support (Account Plan, Custom

Invoice, etc.)

The sequence in which the reports are listed in the PointMerge URL (ReportData,

ReportData1, ReportData2, etc.)

A description of the data being retrieved

The Salesforce “Report Type”

In the example below, four Salesforce reports called from a PointMerge 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 in a PointMerge View Data file.

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.


Using Report Fields in Templates

Fields retrieved from PointMerge 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 our

website, http://home.appextremes.com/Documentation.

Designing Microsoft Word Merge Templates

Designing Microsoft Excel Merge Templates

Designing Microsoft PowerPoint Merge Templates

Designing Adobe Acrobat PDF Merge Templates

http://home.appextremes.com/Documentation

http://home.appextremes.com/Documentation/CongaComposer/WordTemplates.pdf

http://home.appextremes.com/Documentation/CongaComposer/ExcelTemplates.pdf

http://home.appextremes.com/Documentation/CongaComposer/PowerPointTemplates.pdf

http://home.appextremes.com/Documentation/CongaComposer/PDFTemplates.pdf


Using Conga Queries with PointMerge

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 can be located on our website. Open the Support page, 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

PointMerge solution

Using Salesforce reports remains a viable option for basic requirements.

For complete details on how to use Conga Queries, please visit our Documentation page, and

look for the Conga Query Manager link.

http://home.appextremes.com/Support/index.php#Resources

http://home.appextremes.com/Documentation


Create and Store a Merge Template

Now that your PointMerge button is configured to retrieve the desired data from Salesforce,

your next task is to create a merge template using Word, Excel, PowerPoint or Adobe

Acrobat. Each type of template has its own benefits and peculiarities regarding merge fields,

so please refer to the appropriate guide for your template type:

Designing Microsoft Word Merge Templates

Designing Microsoft Excel Merge Templates

Designing Microsoft PowerPoint Merge Templates

Designing Adobe Acrobat PDF Merge Templates

Finally, after designing a template you may store your template in any of three locations:

The Salesforce template repository

The Conga Template Manager

Your local hard drive or network drive

Each of these is discussed in Storing Merge Templates.

http://home.appextremes.com/Documentation/CongaComposer/WordTemplates.pdf

http://home.appextremes.com/Documentation/CongaComposer/ExcelTemplates.pdf

http://home.appextremes.com/Documentation/CongaComposer/PowerPointTemplates.pdf

http://home.appextremes.com/Documentation/CongaComposer/PDFTemplates.pdf

http://home.appextremes.com/Documentation/CongaComposer/StoringMergeTemplates.pdf


Refine PointMerge Solutions with Parameters

PointMerge solutions can be highly customized to enhance the user experience. If desired,

you may include any of the following parameters in your PointMerge URL. Append each

parameter to the URL value in your PointMerge 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 PointMerge 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 PointMerge URL in any order

6. Several complete examples are available in the last section of this chapter

We invite you to explore the various categories for PointMerge parameters:

Data-Gathering Parameters

Data-Formatting Parameters

Template Parameters

Email Parameters

Security Parameters

Activity Logging Parameters

Output Parameters

Dynamic Parameters

DocuSign Integration Parameters

EchoSign Integration Parameters

Salesforce Content Integration Parameters


Data-Gathering Parameters

The following parameters affect how PointMerge gathers data from Salesforce.

PARAMETER DESCRIPTION

Id=[id] Sets the master object. All fields are retrieved from this object. ** Note: A PointMerge URL must contain one (and only one) instance of this parameter ** Requires: A Salesforce Id of any record (Contact, Lead, Account, Custom Object, etc.) or a field that contains an Id

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 tab as seen in View Data workbook. You may include up to 50 ReportId values in a PointMerge URL, thus making 50 reports accessible in a single merge operation. Requires: A 15-character Salesforce Id of a Report. May optionally include filter criteria. Example 1: …&ReportId=00143532453dg3A Example 2: (two reports) …&ReportId=00O43532453dg3A,00O43532453dgF2 For more options and a complete discussion of using Reports with PointMerge, please see Using Salesforce Reports with PointMerge, page 11

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 tab as seen in the View Data workbook. You may include up to 50 QueryId values in a PointMerge URL, thus making 50 queries accessible in a single merge operation. Requires: A 15-character Salesforce Id of a Query record. May optionally include filter criteria. Example 1: …&QueryId=a00143532453dg3 Example 2: (two queries) …&QueryId=a00143532453dg32,00143532453dgF2 For more options and a complete discussion of using Queries with PointMerge, please see Using Conga Queries with PointMerge, page 24



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 Requires: 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).

ReportVar=[value] Placeholder to represent a value passed to multiple reports, thereby resulting in a shorter overall URL length Requires: At least two ReportId values Example: &ReportVar=California|New+York|New+Jersey &ReportId=00O987654321?pv0={ReportVar}, 00O876543210?pv0={ReportVar}, 00O654321033?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.

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 sheet of the View Data workbook. This value could be displayed in a watermark or page header on a Word template.



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 PointMerge parameter. Requires: 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 PointMerge parameter, indicate where you want to

insert the QVar0 result with "{QVar0}" (no quotes). The resulting values for all QVar variables appear in the View

Data Workbook (.xls).

The resulting value may be inserted into most PointMerge parameters, but not all. Most importantly, it can be included in ReportId, QueryId, TemplateId, TemplateGroup and the Email parameters.

The duplicate values are automatically stripped from the resulting data.

Not recommended for retrieving date values. Example: Say you wanted to look up the Id for an Account's Primary Contact and use the Id in the EmailToId 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=a01234567890?pv0={!Account.Id}

3. Pass the QVar result into the EmailToId parameter: &EmailToId={QVar0}


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.


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). Requires: 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 German/Germany - Euros en-GB English/Great Britain – British Pounds en-US English/United States – Dollars es-ES 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.

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. 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

http://msdn.microsoft.com/en-us/goglobal/bb896001.aspx


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

PointMerge 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.


Template Parameters

The following parameters pertain to merge templates.


TemplateId=[id] Pre-selects the template(s) specified in the Template list box You may include up to 10 TemplateId parameters. 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)

Requires:

A 15-character Salesforce Id of a Template record

Example 1: …&TemplateId=00143532453dg3B

Example 2 (multiple templates): …&TemplateId=00143532453dg3B,001435121234499

Example 3 (referencing a field that contains the template id): …&TemplateId={!Contact.TemplateId}

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 Requires: 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.

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. Requires: Multiple Template Ids specified Output format set to “Adobe PDF” (DefaultPDF=1)



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”

Requires: Setup options configured to allow Local Templates. (See Appendix)

TemplateGroup=[value] Filters the list of templates that appear on the PointMerge page to those that match this criteria. May include one or more values, separated by

commas. Requires: 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.

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.

The “Multiple Template Selection” dialog box 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

TNC=[value] Filters the list of templates at appear on the PointMerge 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


FAQ: Pre-Selecting a Merge Template for PointMerge Solution

For most PointMerge 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 PointMerge.

Example:




&Id={!Contact.Id}

&TemplateId=01H500000005tMS

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


Email Parameters

The standard PointMerge dialog includes the option to generate the desired merge output

and attach it directly to an outbound Salesforce email message. This feature can greatly

reduce the time required to otherwise generate a merge file, save it to disk, launch an email

message and attach the file – a great productivity tool.


EmailToId=[id] Sets the value of the To field Requires: A Salesforce Id of a Contact or Lead, or a field that contains the Id of a Contact or Lead. If the PointMerge 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., “…&EmailToId=+”

If the PointMerge Master Object is a Real-Time Quote, the To field is automatically set to the Contact on the Quote, without the use of this parameter. Example 1: …&EmailToId={!Contact.Id} Example 2: …&EmailToId=00143532453dg3C

EmailRelatedToId=[id]

Sets the value of the Related To field Requires: A Salesforce Id of an Account, Opportunity or other object, or a field that contains this kind of Id. The Related To field causes the sent email to appear in the Activity History related list of the object identified. Example 1: …&EmailRelatedToId={!Opportunity.Id} Example 2: …&EmailRelatedToId=00143532453dg3D

EmailAdditionalTo=[text]

Sets the value of the Additional To field Requires: An email address or a field that contains one or more email addresses. Example 1: …&[email protected] Example 2:

…&[email protected], [email protected] Example 3: …&EmailAdditionalTo={!Contact.OtherEmailAddress}



EmailCC=[text]

Sets the value of the CC field Requires: An email address or a field that contains one or more email addresses. Example 1: …&EmailCC [email protected] Example 2: …&EmailCC={!Contact.OtherEmailAddress}

EmailBCC=[text]

Sets the value of the BCC field Requires: An email address or a field that contains one or more email addresses. Example 1: …&EmailBCC [email protected] Example 2: …&EmailBCC={!Contact.OtherEmailAddress}

EmailTemplateId=[id] Loads the subject and body fields from a Salesforce email template. ** Note: Attachments stored directly in the email template are not applied unless EmailTemplateAttachments is set to 1 ** Requires: A 15-character Salesforce Id of an email template stored in Setup |

Communication Templates | Email Templates EmailRelatedToId parameter or EmailToId parameter must be set Example: …&EmailTemplateId=00143532453dg7A

EmailSubject=[text] Sets the value of the Subject field If you set this parameter and use EmailTemplateId, this value will override the value of the Email Template’s Subject. Requires: Any text. Use + to indicate spaces. Example 1: …&EmailSubject=Thank+You Example 2: …&EmailSubject=Account+Brief+for+{!Account.Name}

EmailTemplateAttachments= [0 or 1]

Indicates to preserve attachments stored with the Email Template If set to 0, attachments stored on the Email Template are ignored If set to 1, attachments stored on the Email Template are

preserved Requires: EmailTemplateId parameter must be set



EmailFromId=[id] Indicates an Organization-Wide Address as the From identity of the email Requires A 15-character Salesforce Id of an Organization-Wide Address as

defined in Setup | Email 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

EmailReplyToId=[id] Changes the apparent sender of an email 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 email that is delivered in an unattended

manner, e.g., Background Mode (DS7=12), Conga Conductor and Conga Workflow.

EmailUseSignature=[0 or 1] Indicates whether to include or exclude the sending user's signature from appearing in the email 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 email that is delivered in an unattended

manner, e.g., Background Mode (DS7=12), Conga Conductor and Conga Workflow.

FAQ: Detailed example of using the Email parameters

Here’s an example that would be applicable to a PointMerge button contained on a Case. It

specifies who to address the Email to, establishes the Related object, specifies the Additional

To and CC fields, and then specifies an Email Template.




&Id={!Contact.Id}

&TemplateId=01H500000005t

&EmailToId={!Contact.Id}

&EmailRelatedToId={!Case.Id}

&EmailAdditionalTo={!Case.OwnerEmail}

&[email protected]

&EmailTemplateId=00X60000000vrZ4


Security Parameters

For a variety of reasons, it may sometimes be desirable to pre-set certain settings on the

PointMerge 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.


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 PointMerge dialog box (including buttons)

are enabled (default) If set to 1, all controls in the PointMerge dialog box (except the buttons)

are disabled

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 Email Button If set to 0, the Email Button is enabled (default) If set to 1, the Email 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 Requires: TemplateId parameter to 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=[0, 1, 2, 3, 4, 5, 6, 7, 12 or 14]

Background Mode: Initiate PointMerge without user intervention If set to 0, Background Mode is not enabled (default)

If set to 1, Background Mode is enabled and the merged document is

attached to the master object

If set to 2, Background Mode is enabled and the merged document is attached to a Salesforce email

If set to 3, Background Mode is enabled and the merged document is delivered to browser to save or open

If set to 4, Background Mode is enabled and the merged document is attached to a new EchoSign Agreement. (See EchoSign integration parameters)

If set to 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

If set to 6, Background Mode is enabled and the merged document is attached to Salesforce Content

If set to 7, Background Mode is enabled and the merged document is attached to a DocuSign Envelope

If set to 12, Background Mode is enabled and the merged document is automatically delivered via email. (Requires EmailToId and EmailTemplateId) *** Warning *** No preview available before delivery. Please test your configuration thoroughly before using this value.

If set to 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.

Requires: 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 Email 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". **



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

BML=[text] Background Mode Label Displays a message on the Background Mode dialog box. Displays up to 50 characters. Requires: DS7=3 (Background Mode to File Download). “See Background Mode” for more details. Example 1: …&BML =Thank+You Example 2: …&BML=Account+Brief+for+{!Account.Name}

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

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 PointMerge dialog box when "Disable Conga Exeuction" is enabled. Displays up to 50 characters. Requires: DC=1 (Disable Conga Execution). Example 1: …&DCL =Required+fields+have+not+been+set


Activity Logging Parameters

The following parameters affect the Log Activity Options of the PointMerge dialog box.

Tip! For clarity, the following “LG” parameters are shown in uppercase,

however they are not case-sensitive in practice.


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. Requires: A 15-character Salesforce Id of an object which allows Activity Tracking Example: …&Id={!Opportunity.Id}&LGParentId={!Account.Id}

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.EmailSubject}

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 or 1] 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

LG5=[id] Sets the “Assigned To” field in the Activity Requires: 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=00553532453dg3D

LG6=[id] Sets the Assigned To field in the Follow-Up Activity Requires: 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=00553532453dg3D

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.EmailSubject}


Output Parameters

The following parameters affect the output file generated by PointMerge.


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.

OFN=[text] Sets the Output File Name, overriding the default output file name Requires: 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 filesnames, “\”, “/”, “>”, “<”, 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 PointMerge 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.**

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. Requires: A Salesforce Id of a object to which attachments are allowed.


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. Requires: 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


PDF (Output) Parameters

If the output file from the merge operation is a PDF, the following parameters affect the file

generated by PointMerge.

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 Requires: 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 Requires: 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 Requires: 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 Requires: Output to a PDF and Enable PDF Encryption (ps0=1) enabled Enables form fields to be editable in the output PDF (for those fields not specified as “read-only”)

PDFIQ=[5 to 100] 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] 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


Excel Parameters

The following parameters affect the behavior of Excel templates.


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 or 1] Strips parentheses and periods from merge field names This setting removes parentheses 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

PowerPoint Parameters

The following parameters affect the behavior of PowerPoint templates.


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


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 PointMerge 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.


?sessionId={!API.Session_ID}

&serverUrl={!API.Partner_Server_URL_80}

&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.


DocuSign Integration Parameters

DocuSign delivers Conga Composer documents via email, 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

http://sites.force.com/appexchange/listingDetail?listingId=a0N30000001taX4EAI

DocuSign is available separately on the AppExchange. You must subscribe to that service to

use these integration parameters.


DocuSignVisible=[0 or 1] Makes the DocuSign button visible on the PointMerge 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 or R4

Sets the recipient of the document to be delivered Requires: 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 or R4

Sets the recipient’s role Requires: A valid DocuSign Role Name, as defined in Envelope Settings Example: …&DocuSignR1Role=Signer+1

DocuSignR1Type=[text] Also available: The parameter with R2, R3 or R4

Sets the recipient’s type Example: …&DocuSignR1Type=Signer

DocuSignR1AccessCode=[text] Also available: The parameter with R2, R3 or R4

Sets the recipient’s access code Example: …&DocuSignR1AccessCode=ABC123

http://sites.force.com/appexchange/listingDetail?listingId=a0N30000001taX4EAI



DocuSignR1RoutingOrder=[1,2 or 3] Also available: The parameter with R2, R3 or R4

Sets the recipient’s routing order

DocuSignSendReminders=[0 or 1]

Sends reminder emails to recipients who have not yet completed their task If set to 0, email reminders are not sent (default) If set to 1, email 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

DocuSignWarnIn =[0 to 999]

Indicates how many days prior to expiration you want an email message to alert recipients that a deadline approaches for completion

Automatic Role Assignment via Opportunity Contact Roles

When using Conga to generate a document from an Opportunity with Contact Roles, Conga

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.


EchoSign Integration Parameters

EchoSign delivers Conga Composer documents via email, 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

http://www.echosign.com/public/static/product/web/forms.jsp

EchoSign is available separately on the AppExchange. You must subscribe to that service to

use these integration parameters.

IM

PO

RT

AN

T

Setup:

After installing EchoSign from the AppExchange, you must modify the EchoSign

application by disabling the default value of the Signature Order field:

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.


ESVisible=[0 or 1] Makes the EchoSign button visible on the PointMerge dialog box ** Note: This parameter is required ** If set to 0, the EchoSign button is not visible (default) If set to 1, the EchoSign button is visible

ESContactId=[id]

Sets the value of the Contact field Requires: A Salesforce Id of a Contact, or a field that contains the Id of a Contact. If the PointMerge Master Object is an Opportunity, the Contact field is automatically set to the Primary Contact, without the use of this parameter. If the PointMerge Master Object is a Real-Time Quote, the Contact field is automatically set to the Quote's Contact, without the use of this parameter.

http://www.echosign.com/public/static/product/web/forms.jsp



** Note: Depending on your EchoSign Agreement Object’s Page Layout, this parameter may be required ** Example 1: …& ESContactId ={!Contact.Id} Example 2: …& ESContactId =00143532453dg3C

ESLeadId=[id]

Sets the value of the Lead field Requires: A Salesforce Id of a Lead, or a field that contains the Id of a Lead.

Example 1: …& ESLeadId ={!Lead.Id} Example 2: …& ESLeadId =00Q43532453dg3C

ESOpportunityId=[id]

Sets the value of the Opportunity field Requires: A Salesforce Id of a Opportunity, or a field that contains the Id of a Opportunity. Example 1: …& ESOpportunityId ={!Opportunity.Id} Example 2: …& ESOpportunityId =00643532453dg3C

ESContractId=[id]

Sets the value of the Contract field Requires: A Salesforce Id of a Contract, or a field that contains the Id of a Contract. Example 1: …& ESContactId ={!Contact.Id} Example 2: …& ESContactId =00143532453dg3C

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” (default) If set to 2, Signature Type is set to “e-Signature”

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}



ESAdditionalTo=[text]

Sets the value of the Additional Recipients field Requires: An email address or a field that contains one or more email addresses. Example 1: …&[email protected] Example 2: …&[email protected], [email protected] Example 3: …&ESAdditionalTo={!Contact.OtherEmailAddress}

ESCopyTo=[text]

Sets the value of the Email a Copy To field Requires: An email address or a field that contains one or more email addresses. Example 1: …&[email protected] Example 2: …&[email protected], [email protected] Example 3: …&ESCopyTo={!Contact.OtherEmailAddress}

ESMessage=[text]

Sets the value of the Message field Example 1: …&ESMessage=Please+sign+the+attached+document Example 2: …&ESMessage={!Opportunity.AgreementMessage__c}

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 Requires: 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

ESSignatureOrder= [1 or 2]

Sets the Signature Order field. IMPORTANT: Please see the Setup instructions at the beginning of this section.

Requires: 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”



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”

DS7=4

Background Mode for EchoSign See PointMerge Background Mode, page 39.

DS7=14

Background Mode for EchoSign (automatically-delivered) See PointMerge Background Mode, page 39.

ESCustomField= [ApiFieldName] Also available: ESCustomField1 ESCustomField2

Sets the name of a custom field to set on the EchoSign Agreement Record created through the merge process. Use the API name of the field on the EchoSign Agreement Object. Requires: ESCustomFieldValue Example: …&ESCustomField=Account__c …&ESCustomFieldValue=001ABCEDFGHIJL

ESCustomFieldValue= [value] Also available: ESCustomFieldValue1 ESCustomFieldValue2

Sets the value of the corresponding custom field Requires: ESCustomField

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.

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.

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 API name

"Attachment_Order__c".

Conga will automatically populate this field with a list of the ids of the attachments

generated. EchoSign will deliver the attachments in the order specified.


Sertifi Integration Parameters


SertifiVisible=[0 or 1] Makes the Sertifi button visible on the PointMerge dialog box. Sertifi is available separately on the AppExchange. You must subscribe to that service to use this integration parameter. If set to 0, the Sertifi button is not visible (default) If set to 1, the Sertifi button is visible

SertifiEmailTo=[text] Sets the value of the recipient of the document to be delivered via Sertifi Requires: An email address or a field that contains one or more email addresses.


Salesforce Content Integration Parameters

Conga can store output documents in Salesforce Content, rather than as attachments under

the Notes & Attachments related list.

IM

PO

RT

AN

T

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 PointMerge 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

PointMerge 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.


ContentVisible=[0 or 1] Makes the Salesforce Content button visible on the PointMerge dialog box. If set to 0, the Salesforce Content button is not visible (default) If set to 1, the Salesforce Content button is visible

LGContentEnabled= [0 or 1]

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 conjuction with this setting.

ContentWorkspaceId= [id]

Sets the Salesforce Id of the Content Workspace under which attachments will be stored. Requires: A Salesforce Id of a Content Workspace. The Id must begin with the prefix "058". Example:

…&ContentWorkspaceId=058a123456789ab



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 API name of the field on the Salesforce Content Object. Requires: 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 Requires: ContentCustomFieldName

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 PointMerge Background Mode, page 39.


PointMerge URL Examples

Sometimes it’s helpful to see a complete PointMerge 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).




&Id={!Contact.Id }

&PS0=1

&PS1=1

&DS3=1

&TemplateId=0014432553FB

&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 Email To field

(EmailToId)




&Id={!Contact.Id}

&ReportID=00O50000001NGuW,

00O50000001O2gr,

00O50000001NGv5,

00O50000001NGvL

&TemplateId=01H500000005z4L

&EmailtoID={!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).




&Id={!Opportunity.Id}

&ReportId=00O50000001OAA2?pv0={!Opportunity.AccountId}

&TemplateId=01H500000005xop

&DS7=1

&FP0=1