In these release notes, you can find packages, requirements, features, enhancements, fixed issues, and known issues for the Conga CLM (Contracts for Salesforce) September22.01.11 release.  For documentation updates, see What's New in Contracts for Salesforce 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. The packages marked as (New) are new packages in this release.

Product

Latest Certified Version Number

Conga CLM (Contracts for Salesforce) (New)

2.87

For more information on installing CLM (Contracts for Salesforce) managed packages, see Installing Contracts for Salesforce. For more information on upgrading CLM managed packages, see Upgrading Contracts for Salesforce.


System Requirements and Supported Platforms 

For requirements and recommendations to consider before installing the Conga product suite, see System Requirements and Supported Platforms Matrix.

New Features 

There were no new features in this release. 

Enhancements

The following enhancement was in this release:

Java Update

The Java version for Conga Contracts for Salesforce was updated to 6.7.34.

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

00815415CFS-1193Send for Negotiation returns a 400 error when users do not use an object set up by the Automatic Configurator. 
00815415CFS-1119Send for Negotiation email replies are creating duplicate Content Versions.

Resolution Notes: 

This fix changes the way new Content Versions are added using Send for Negotiation. Previously, if an email reply to Salesforce included a file attachment, and the attached file was the same file as the latest Content Version (no change to the file content), then a new Content Version was added. 

Going forward, if an email reply to Salesforce includes a file attachment, and the attached file is the same file as the latest Content Version (no change to the file content), then a new Content Version will not be added. 

This change will currently only work if the Allow Word Document Renaming custom setting is disabled. If the Allow Word Document Renaming customer setting is enabled fewer Content Versions will be created if the attached file is the same.



Known Issues

There were no known issues in this release.

DOC ID: CFSSEP22RN20230116