Skip to main content
Conga Support

Test Using the Conga Conductor Record

Follow these instructions if you are currently running Conga Conductor solutions on Release 7 and wish to upgrade to Conga Conductor Release 8. 

To test a Release 7 solution by using the Conga Conductor record:

Before You Begin: Upgrade to Conga Conductor Release 8.  The upgrade process will retain all existing Conga Conductor solutions from Release 7. These solutions can continue to run on Release 7 or can be upgraded to run on Release 8.

  1. Clone the existing Conga Conductor record to prevent interference with your existing solution.

    Include Test Release 8 in the Title of the new, cloned record.

  2. Gather sample Master records for the test batch.

    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.

    Using the Conga Conductor record to launch the Conductor solution, you can either:

    • Write a Salesforce report or SOQL query that includes a handful of sample records and reference it using the Report ID or Query ID field on the Test Release 8 Conga Conductor record.

    • Reference one Master Object sample record at a time using the Record ID field on the Conga Conductor record.

  3. Ensure the proper Conga Conductor formula field (API name) is referenced in URL Field Name.  It should have copied over when you cloned the original Conductor record.  Click Save.

  4. Add Version to the Conductor page layout.

    We recommend that the Version field is accessible only to the System Administrator profile.

  5. Change Version to C8, ensuring that the batch process runs on Conga Conductor Release 8.

  6. Click Launch to initiate the Conga Conductor process.

    If you are prompted to allow or deny permissions for Conga Composer, we recommend clicking Allow, which uses a Salesforce refresh token and may be revoked at any time (Salesforce > My Settings > Personal > Advanced User Details > OAuth Connected Apps).  If you select Deny, a session ID will be used for security settings instead of a refresh token.

  7. Start the Conga Conductor process and analyze the results.

    Analyze the results.

    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.

  8. Once you confirm that the Conductor solution works as desired, you may delete this test record, update your original Conductor record to C8 for Version and use that Conductor record going forward.