In these release notes, you can find packages, requirements, features, enhancements, fixed issues, and known issues for the DocuSign Services September22.03.08 Release. For documentation updates, see What's New in DocuSign Services Documentation.

This documentation may contain descriptions of software features that are optional and for which you may not have purchased a license. As a result, your specific software solution and/or implementation may differ from those described in this document. Please contact your CSM or AE for information on your specific features and licensing.


The following packages and dependent packages are required to upgrade to this release to utilize all the new features of this release. These are the minimum required versions; later versions are also supported. Separate prerequisites for each feature can be found in the respective guides.

You can register your org for the Conga Push Upgrade. Conga Push Upgrade is an automated tool that upgrades packages available in your Salesforce org (Production or Sandbox) to the latest versions. In addition, it also ensures all the Conga published managed packages are on the latest versions for your registered orgs. For more information, see Registering for Conga Upgrade Program.

PackageLatest Certified Version NameLatest Certified Version Number
Conga Base Library

Conga Contract Lifecycle Management 



Conga Quote Management


Conga DocuSign API (New)8.1.1428.142.18
Conga CLM DocuSign Integration5.1.505.50.7

Conga Quote DocuSign Integration
If you are upgrading to Conga DocuSign API version 8.142.15 or later from an earlier version, you need to perform the following one-time activity:
  1. Go to DocuSign Configuration Home tab.
  2. Click Encrypt Keys. On clicking the button, the key will be encrypted. The users can now perform DocuSign transactions securely.

The above activity is not required while upgrading from Conga DocuSign API version 8.142.15 to higher versions in future.

If you are performing fresh installation of Conga DocuSign API 8.142.15 or later, then the Encrypt Keys button will not be visible because the Integration Key field value will be automatically encrypted. Hence, you will not be needed to perform the one-time activity.

System Requirements and Supported Platforms

For requirements and recommendations you must consider before you proceed with the installation of the Conga product suite delivered on the Salesforce platform, see System Requirements and Supported Platforms Matrix.

New Features

There are no new features in this release. 


An administrator can configure APTS_StatusCategoriesToIncludeForDocuSign and APTS_StatusCategoriesToExcludeForDocuSign admin entries to specify the agreement status categories that should or should not be changed to In Signatures after an agreement document is sent for DocuSign eSignature. For more information, refer Admin Settings.

Data Model Changes

This release does not have any data model changes for DocuSign Services.

Fixed Issues

The following table lists the issues fixed in this release. If any actions are required, they will be listed in this table.

Case NumberConga Internal IDDescription

On sending a document for DocuSign eSignature, the agreement status category and status are not changing to In Signatures and Other Party Signatures, respectively if the current status category and status is In Effect and Being Terminated respectively.

Resolution Info.: APTS_StatusCategoriesToExcludeForDocuSign and APTS_StatusCategoriesToIncludeForDocuSign admin entries are introduced. For more information, refer Admin Settings.



When DocuSign Templates Enabled checkbox in Custom Settings is selected, the system assigns Signer Role in the Sequence mentioned as per Routing Order and not as per the Role mentioned on the DocuSign Recipient record.

Known Issues

There are no known issues in this release.