There are two different ways to launch Conga Batch – either through a Conga Batch record or a List View Button. You might configure some Conga Batch operations to be launched by a Conga Batch record and others by a List View button, and each method has its advantages and limitations.
Launching from a Conga Batch Record
This method allows you to select the records to include in your batch using a Salesforce report or SOQL query. It also allows you to schedule your Conga Batch to run on a schedule with no user interaction. This method is preferred if you want to schedule your batches to run with no user interaction.
This method allows you to manually select which records to include in your batch (up to 75 records). You can choose to add the List View button to a Search Layout or to an Object Page Layout, letting users choose the records from a List View or a Related List.
Other Considerations
If your output method is an immediate download as a single PDF, single Word file (using AWD parameter), or .zip file (consolidated output), your batch is limited to 200 records regardless of which launch option (above) you choose.
The consolidated output limit can be increased to 500 records on request. To increase the limit, contact your Conga Representative.
If you are emailing the output (known as distributed output), sending for eSignature, or storing it in another location (like Salesforce or Google Drive), you can include as many records as you want in a batch (if launching the solution from a Conga Batch record); however, larger batch operations must adhere to the following constraints:
- Number of Salesforce API calls per day allowed by the Org
- Salesforce file storage limits within the Org
- Email provider (such as Salesforce, SendGrid, or AWS SES) limits on the number of emails to be sent per day
These considerations can help you decide how to launch your Conga Batch solution.
