Conga [email protected]
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 emailed 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 email 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:
[email protected]
Telephone: +1 303-465-1616 or (866) 502-3334
Europe, Middle East, Africa (EMEA)
Support Hours: 9 a.m. – 5 p.m. British Time
Tech Support Email:
[email protected]
Telephone: +44 20 3608 0165
Asia / Pacific (APAC)
Support Hours: 9 a.m. – 5 p.m. Eastern Time
Tech Support Email:
[email protected]
Telephone: +61 28 417 2399
Sales
For information on other products from Conga, please contact our New Business team:
Sales Information Email:
[email protected]
Telephone: +1 303-465-1616
© 2014 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
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
Table of Contents
1. What is Conga Composer? ... 5
2. Create a Conga Composer button ... 6
Create the button ... 6
Adjust the Window Open Properties ... 7
Add the button to a Page Layout... 8
3. Gather Salesforce Data ... 9
What fields are available for merging? ... 10
What if I need data from an object related to the Master Object? ... 12
Using Salesforce Reports with Conga Composer ... 13
Using Conga Queries with Conga Composer ... 26
Create and Store a Merge Template ... 27
4. Refine Conga Composer Solutions with Parameters ... 28
Basic Configuration Parameters ... 29
Data-Gathering Parameters ... 29
Template Selection Parameters ... 32
Email Parameters ... 36
Activity Logging Parameters ... 40
Conga Window Appearance ... 44
Background Mode Parameters... 46
Output File Parameters ... 51
General Output File Parameters ... 51
PDF (Output File) Parameters ... 54
Excel Parameters ... 56
PowerPoint Parameters... 56
Word Parameters ... 57
Email Template Parameters ... 58
Integration Parameters ... 59
DocuSign Integration Parameters ... 59
EchoSign Integration Parameters ... 64
Salesforce Chatter Integration Parameters ... 69
Salesforce Content Integration Parameters... 70
SendGrid Integration Parameters ... 73
Sertifi Integration Parameters... 74
SpringCM Integration Parameters ... 75
Advanced Parameters ... 76
Advanced Data Gathering Parameters ... 76
Advanced Template Selection Parameters ... 80
Advanced Data-Formatting Parameters ... 81
Advanced Control Parameters ... 83
Formula-Driven Parameters ... 84
Conga Composer URL Examples ... 85
5. Conga Email Template Manager ... 86
6. Know Your Limits ... 87
7. Other Parameters ... 88
Supported Culture Codes ... 88
8.
Index of Conga Composer Parameters ... 90
General Disclaimer
Conga Composer solutions depend on and leverage technology from a multitude of software
and hardware vendors including but not limited to salesforce.com, Microsoft, Google, and the
providers of various Internet browsers (“Third Party Technology”). Output from Conga
Composer solutions can be impacted by these and numerous other factors beyond the control
of Conga, including:
•
Template design errors in Microsoft Word, Excel, PowerPoint templates, PDF Forms or
Conga HTML email templates
•
The nature and scope of data and/or images being retrieved for merging into templates
•
Individual user’s browser, network, ISP and/or hardware settings (see Conga Composer
Installation and Administration Guide for additional details)
•
The use of any encryption gateways or appliances that require any re-direct of Conga
Composer traffic
•
The availability and performance of the salesforce.com service and other
software-as-a-service solutions such as eSignature, eCommerce and other AppExchange products, and
periodic updates, enhancements or other changes to such services made by their
respective vendors
•
Salesforce.com security settings including User Profiles and Permissions, folder and
object access and field-level security
•
Internet performance, regional and even global outages
For these reasons, Conga cannot guarantee that your particular implementation of
Third Party Technology and Conga technologies – even if configured based on
Conga documentation and/or guidance offered by Conga Support personnel – will
perform consistent with your expectations or requirements, or provide the output
you require. Accordingly, Conga disclaims any and all liability resulting from, or
related to, performance issues associated with Conga products to the extent arising
from your implementation, configuration, or the behavior of Third Party
Technology.
508 Compliance
Conga Composer is an installable package from the Salesforce AppExchange, which
integrates with an individual customer's existing implementation of Salesforce. When
properly configured, Conga Composer will run within an existing Salesforce instance without
the need to view, manipulate or configure the application outside of the Salesforce user
interface.
The use of Conga solutions is entirely represented by standard Salesforce user interface
components when properly configured. Therefore, customers seeking the 508 Compliance
VPAT documentation are referred to Salesforce.
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
email.
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.
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:
https://www.appextremes.com/apps/Conga/Composer.aspx
?SessionId={!API.Session_ID}
&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.
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 500
5. Clear the checkbox on #6
Show Scrollbars
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.
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.
How do you know which fields are available to you? To answer that question, let’s discover
the power of the Template Builder.
(2)
Add or modify
Salesforce
Reports
(3)
Modify
Conga Composer
Button
URL
(1)
Examine the
Template Builder
window
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).
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
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.
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.)
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 filters the report by passing the Master Object Id
into the first cell of the value column in the report when the merge
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
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=00O50000001LNBd?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.
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
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:
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:
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=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=
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:
https://www.appextremes.com/apps/Conga/Composer.aspx
?SessionID={!API.Session_ID}
&ServerURL={!API.Partner_Server_URL_210}
&Id={!Contact.Id}
&ReportID=00O50000001NGuW,
00O50000001O2gr,
00O50000001NGv5?pv1={!Contact.MailingState},
00O50000001NGvL
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.
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
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.
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
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
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 Email Templates
Storing Merge Templates
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.
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 email, 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 Email 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
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
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 email messages
•
How activity logging should take place
Data-Gathering Parameters
The following parameters affect how Conga Composer gathers data from Salesforce.
PARAMETER DESCRIPTION
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 **
Requires:
A Salesforce Id of any record (Contact, Lead, Account, Custom Object, etc.) or a field that contains an Id
PARAMETER DESCRIPTION
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.
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 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]00143532453dg3A Example 2: (two reports)
…&ReportId=[MyAccounts]00O43532453dg3A, [MyCases]00O43532453dgF2
For more options and a complete discussion of using Reports with Conga Composer, please see Using Salesforce Reports with
PARAMETER DESCRIPTION
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. 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 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]a00143532453dg3 Example 2: (two queries)
…&QueryId=[MyAccounts]a00143532453dg32, [MyCases]a0043532453dgF2
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
.
Template Selection Parameters
The following parameters pertain to merge templates.
PARAMETER DESCRIPTION
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).
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}
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.
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.
PARAMETER DESCRIPTION
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
.
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:
https://www.appextremes.com/apps/Conga/Composer.aspx
?SessionID={!API.Session_ID}
&ServerURL={!API.Partner_Server_URL_210}
&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,
Email Parameters
The standard Conga Composer 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.
PARAMETER DESCRIPTION
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.
Note: If using a Lead Id with Conga Email Templates, must use SendGrid integration, Leads and Conga Email Templates do not work with Salesforce email.
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., “…&EmailToId=+”
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:
…&EmailToId={!Contact.Id} Example 2:
…&EmailToId=00143532453dg3C
NOTE: This parameter will not work when the master object is a Lead and you are using Conga email templates, there is a Salesforce limitation concerning Leads. It will however work when using standard Salesforce email templates.
EmailRelatedToId=[id] Sets the value of the Related To field. Requires:
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 email 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:
…&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}
PARAMETER DESCRIPTION
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
PARAMETER DESCRIPTION
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 Conga Composer 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.
https://www.appextremes.com/apps/Conga/Composer.aspx
?SessionID={!API.Session_ID}
&ServerURL={!API.Partner_Server_URL_210}
&Id={!Contact.Id}
&TemplateId=01H500000005t
&EmailToId={!Contact.Id}
&EmailRelatedToId={!Case.Id}
&EmailAdditionalTo={!Case.OwnerEmail}
&[email protected]
&EmailTemplateId=00X60000000vrZ4
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 DESCRIPTION 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
Follow-PARAMETER DESCRIPTION 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 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:
PARAMETER DESCRIPTION
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} 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”
Requires:
• &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.
Requires:
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. Requires:
• A Salesforce Id of an object which allows Activity Tracking Example:
…&Id={!Opportunity.Id} &LGParentId={!Account.Id}
PARAMETER DESCRIPTION MFTS0=[ApiFieldName]
Also available: MFTS1, MFTS2
Master Field to Set Requires:
• 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 Requires:
• 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.
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 DESCRIPTION
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
PARAMETER DESCRIPTION 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 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
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 Email the output file 2 – Email
12 – Automatic Email 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 DESCRIPTION BML=[text] Background Mode Label
PARAMETER DESCRIPTION DS7=[0, 1, 2, 3, 4, 5, 6,
7, 8, 12, 13, 14, 17 or 24]
Background Mode: Initiate Conga Composer without user intervention 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”. **
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 email
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 email. (Requires EmailToId and EmailTemplateId)
*** Warning *** No preview available before delivery. Please test your configuration thoroughly before using this value.
PARAMETER DESCRIPTION
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 end-users.
For Internet Explorer, we recommend the following browser configuration:
(1) Add “https://*.appextremes.com” 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.
Requires:
• 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 Email Template Id Requires:
• FP0=1 or DefaultPDF=1
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.
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
•
Email Template Parameters
General Output File Parameters
The following parameters affect the output file generated by Conga Composer.
PARAMETER DESCRIPTION
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
PARAMETER DESCRIPTION
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 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.
Requires:
PARAMETER DESCRIPTION
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 File) Parameters
If the output file from the merge operation is a PDF, the following parameters affect the file
generated by Conga Composer.
PARAMETER DESCRIPTION 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 Requires:
• 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
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:
