Determine Merged Output Files

With CQG, you can determine how the merged output file will be delivered or where it will be stored after launching the 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.

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.

QMode Value	Description
&QMode=Attachments	Attaches the merged output files to the Master Object records. Do not use in conjunction with other parameters that attach the file (e.g. &SC0=1).
QMode=Download	Downloads the merged output files to the internet browser. This parameter value is available only to Conga Batch. 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.
&QMode=Chatter	Posts the merged output file in the Salesforce Chatter feed. By default, Conga Batch 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).
QMode=Documents	Attaches the merged output files to a folder on the Documents tab.
QMode=DocuSign	Sends the merged output files via DocuSign (one DocuSign Envelope per Master Object record).
QMode=EchoSign	Sends the merged output files via Adobe eSign (one Adobe eSign Agreement per Master Object record).
QMode=EchoSignCreate	Merges the output files and attaches each to an Adobe eSign Agreement but does not automatically send those Agreements.
QMode=GoogleDrive	Saves the merged output files in Google Drive. Requires the Google Refresh Token on Conga Batch Setup tab. Use &OFP to specify in which folder the merged output files are to be saved. Remove &SC0=1 and &SC1=Google from the Conga Batch formula field to prevent the 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 Batch Setup tab. Recommended: &OFP to specify in which folder the merged output files are to be saved.
&QMode=SalesforceFile	Sends the merged output files to Salesforce Files for the Master Object. The &SC0=1 and &SC1=SalesforceFile parameters are required in the URL for this QMode.
&QMode=Sertifi	Sends the merged output files via Sertifi. The browser page refreshes and lands on the Sertifi EContract. There are many combinations of possible Sertifi 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 documents to Conga Sign.
&QMode=Contracts	Sends the output documents for negotiation using Conga Contracts for Salesforce's Send for Negotiation email service.
&QMode=AmazonS3	Sends the output documents to AmazonS3.