Skip to main content
Conga Support

Test Using a Conga Conductor List View Button

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. Edit the Conga Conductor list view button you created in Conductor Release 7.

  2. Change var CongaURL to  https://conductor.congamerge.com/

    This instructs Conga Conductor to run the list view button on Conga Conductor Release 8.

  3. Create a test list view on the appropriate Master Object in order to gather sample records to use for testing.

    We recommend naming the list view Test CN Release 8 – [Conductor Solution Name].  For example, Test CN Release 8 – Oppty Invoice Email.

    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.

  4. Select a few sample records from the test list view and click the Conductor list view button you just updated to Release 8.

  5. 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.

  1. Edit the Conga Conductor list view button you created in Conductor Release 7.

  2. Change var CongaURL to  https://conductor.congamerge.com/

  3. This instructs Conga Conductor to run the list view button on Conga Conductor Release 8.

  4. Create a test list view on the appropriate Master Object in order to gather sample records to use for testing.

    We recommend naming the list view Test CN Release 8 – [Conductor Solution Name].  For example, Test CN Release 8 – Oppty Invoice Email.

    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.

  5. Select a few sample records from the test list view and click the Conductor list view button you just updated to Release 8.

  6. 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.

Once you confirm that the Conductor list view works as desired, you may use it with list views going forward.