In these release notes, you can find packages, requirements, features, enhancements, fixed issues, and known issues for the DocuSign Services September22.02.09 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.
Packages
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.
| Package | Latest Certified Version Name | Latest Certified Version Number |
|---|
| Conga Base Library | 3.1.238.7 | 3.238.7 |
Conga Contract Lifecycle Management | 13.1.683.17 | 13.683.17 |
| Conga Quote Management | 11.0.0242 | 11.242 |
| Conga DocuSign API (New) | 8.1.142 | 8.142.15 |
| Conga CLM DocuSign Integration | 5.1.50 | 5.50.5 |
Conga Quote DocuSign Integration | 4.1.22 | 4.22 |
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:- Go to DocuSign Configuration Home tab.
- 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.
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.
Enhancements
There are no new enhancements in this release.
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 Number | Conga Internal ID | Description |
|---|
| ISC-260 | CONTRACTS-18008 | The Integration Key field that is configured in DocuSign Configuration Home is not encrypted in the metadata. This makes it accessible to any user who has access to metadata. Resolution Info: The Integration Key field values stored in salesforce object is encrypted using a private secure encryption key and AES 256 encryption algorithm. For more details, refer to the note under Packages section. |
| 00870337 | CONTRACTS-16740 | The user is unable to add text in the Additional Details tab while sending agreement for Docusign esignature. |
Known Issues
There are no known issues in this release.
DOC ID: DSIGNSEP22PRN20240209
