To test the solution:

  1. Confirm that the Conga Trigger formula field is accessible (field-level security is set to Visible) by System Administrators only. This ensures that the activated Salesforce workflow rule that initiates the Conga Trigger process won’t work for anyone except System Administrators while you are still in the testing phase.
  2. Locate the Salesforce workflow rule and click Description for the Outbound Message workflow action.
  3. Edit the outbound message and change the Endpoint URL to https://workflow.congamerge.com/OBMListener.ashx.
  4. Save your change.
  5. Select a sample Master Object record to use for the test. 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.
  6. Trigger the Conga Trigger routine in the manner defined on the Salesforce Workflow Rule.
  7. 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.