If you are using the Conga Batch record to launch a Conga Batch solution, you can either:

• Write a Salesforce report or SOQL query that includes a handful of records and reference it using the Report ID or Query ID field on the Conga Batch record.
• Reference one Master Object record at a time using the Record ID field on the Conga Batch record.

If you are using a Salesforce list view button to launch Conga Batch, then use the Salesforce list view to select a few records. Sample records are used so that the testing phase won’t send documents or communications to actual recipients (customers, partners, employees, etc.). You may want to create new, sample records with fake data to ensure that documents or communications are not sent to actual recipients when testing. For solutions that send emails or eSignature requests, ensure that you have access to the recipient’s email inboxes (or use your own email address) so you can confirm receipt of the email message/eSignature request.

Launching the test batch is determined by which method you used to gather sample records.

• Salesforce report or SOQL query: Launch from the Conga Batch record
• One Master record at a time: Launch from the Conga Batch record
• Salesforce list view: Launch using a Conga Batch list view button

This is perhaps the most important step in the testing process, as you will determine if everything is working correctly and you can deploy the solution or if there are inconsistencies or issues and you need to configure further or troubleshoot.

You should confirm that the following aspects of the solution are working properly:

• Reports and queries are retrieving data to be used in the template.
• Data is merging to the template, creating the merged output file.
• Activity logging, field updates, saving a copy of the merged output file, and any other parameters are acting as desired.
• Fields on the email or eSignature request are referencing the proper information and the email or eSignature request is sending.