Skip to main content
Conga Support

Determine How Conga Batch Will Deliver the Merged Output Files

With Conga Composer, a user can determine how the merged output file will be delivered or where it will be stored after launching the Composer button; however, Conga Batch runs in the background – without user input after the initial launch process – so we must specify in advance how Conga Batch will deliver the output files.

We do this using a QMode parameter in the Conga Batch formula field. The parameter name remains constant (&QMode=) but the value changes depending on the desired delivery method (e.g. “Download” for downloading, “SendEmail” for emailing). Only one QMode parameter may be used per Conga Batch solution, meaning all of the records within that Conga Batch batch will be delivered in the same way.

The QMode table is also helpful for ensuring that your Conga Batch solution includes the required parameters to correctly deliver the merged output files. If you’re unfamiliar with these parameters, please see How Parameters are Formatted. 

The below table lists the available QMode parameter values and describes how each will deliver the merged output files for a Conga Batch routine using that QMode value.

 

Automation-Background Mode Parameter

Active 1

0 Release 7

1  Release 8

QMode

Parameter Value: [value]

&QMode=Attachments

Parameters for Conga Batch and Conga Trigger
 

QMode parameter is required when working with Conga Batch or Conga Trigger solutions. 

If you use the QMode parameter to distribute documents (such as email or eSignature) and you also want to save copies of the document, ensure the SC1 parameter is used in conjunction with QMode. 

QMode Value

Description

&QMode=Attachments

Attaches the merged output files to the Master Object records

&QMode=Download

Downloads the merged output files to the internet browser.

This parameter value is available only to Conga Batch. There is no download option available in Conga Trigger.

Recommended: &ContentWorkspaceId=[Workspace ID] to specify the Content Workspace (Library) where Conga Batch will store the merged output file if the Conga Batch solution is configured to run on a schedule.  Without this parameter, the merged output file from a scheduled Conga Batch solution configured to download will be stored in the running user’s personal Salesforce Content Workspace (Library).

If either the &DefaultPDF=1 or &FP0=1 parameter is not included in the Conga Batch formula field, the merged output files will be consolidated into a .zip file.  However, if one of these PDF output parameters is included in the formula field, the merged output file will be a consolidated PDF.

&QMode=SendEmail

Emails the output file.

* Requires:   

&TemplateId, unless using only a Conga Email Template (&CongaEmailTemplateId) and no document template

&EmailTemplateId=[Salesforce email template ID] or &CongaEmailTemplateId=[Conga Email Template ID]

&EmailToId=[Salesforce Contact ID] or &ContactId=[Salesforce Contact ID]

If you cannot use the &EmailToId or &ContactId parameters to specify an email recipient by their Contact ID, you may instead specify &EmailAdditionalTo=[email address] and &EmailSubject=[subject text].

&QMode=Chatter

Posts the merged output file in the Salesforce Chatter feed.

By default, Conga Trigger posts files to the Master Object record feed. To override this behavior and post a file to another record’s feed, a Chatter Group or a specific User’s feed, use &AttachmentParentId.

&QMode=Content

Attaches the merged output files to the running user’s personal Workspace (Library) in Salesforce Content.

Recommended: &ContentWorkspaceId=[Salesforce Content Workspace ID] to specify an alternate Content Workspace (Library).

Does not permit saving additional attachments outside of the initial document created in your Content Workspace (for example, cannot save a copy to Attachments or Chatter in addition to your Content Workspace).

Use this method if  you are scheduling a content deliver.

&QMode=Documents

Attaches the merged output files to a folder on the Documents tab.

Does not permit saving additional attachments outside of the initial document created in your Document folder (i.e. cannot save a copy to Attachments or Chatter in addition to your Document folder).

* Requires:    &DocFolderId=[Salesforce Documents Folder ID]

&QMode=DocuSign

Sends the merged output files via DocuSign (one DocuSign Envelope per Master Object record).

* Requires:    DocuSign parameters

There are many combinations of possible DocuSign parameters. Please see DocuSign Integration Parameters for more information.

&QMode=EchoSign

Sends the merged output files via Adobe eSign (one Adobe eSign Agreement per Master Object record).

* Requires:    

Adobe eSign parameters

&ESSVBA=1

There are many combinations of possible Adobe eSign parameters.  For more information, see Adobe eSign Integration Parameters.

Recommended: &ESAgreementTemplateId=[Adobe eSign Agreement Template ID]

&QMode=EchoSignCreate

Merges the output files and attaches each to an Adobe eSign Agreement but does not automatically send those Agreements.

* Requires:    Adobe eSign parameters

There are many combinations of possible Adobe eSign parameters.  For more information, see Adobe eSign Integration Parameters.

&QMode=GoogleDrive

Saves the merged output files in Google Drive.

* Requires:    Google Refresh Token on Conga Batch Setup tab.

Recommended:

&OFP to specify in which folder the merged output files will be saved

Remove &SC0=1 and &SC1=Google from the Conga Batch formula field to prevent storage of duplicate copies of the merged output file in Google Drive.

&QMode=GoogleDocs

Converts the merged output files to Google Documents, Spreadsheets, or Slides, which are saved in Google Drive.

* Requires:    Google Refresh Token on Conga Trigger Setup tab.

Recommended: &OFP to specify in which folder the merged output files to be saved.

&QMode=SalesforceFile Sends the merged output files to Salesforce Files for the Master Object.

&QMode=Sertifi

Sends the merged output files via Sertifi.  The browser page refreshes and lands on the Sertifi EContract.

* Requires:    Sertifi parameters

There are many combinations of possible Sertifi parameters.  For more information, see Sertifi Integration Parameters.

&QMode=SpringCM

Saves the merged output files in a SpringCM folder, as defined by the SpringCM configuration rules.

&QMode=Box

Sends the output documents to Box.

&QMode=OneDrive

Sends the output documents to the user's OneDrive repository.

&QMode=CongaSign Sends the output document to Conga Sign.