Release Notes contain the following information about Conga Sign Summer'21 Release (Conga Sign 1.67.0 Release).

For more information on new features, enhancements, and document improvements refer to What's New in Conga Sign Documentation. 

  • Packages: Lists packages that are required to upgrade to this release of the product

  • System Requirements and Supported Platforms: Lists requirements and recommendations for installing this release

  • New Features: Provides high-level descriptions of new features introduced in this release, with links to more detailed information

  • Enhancements: Provides high-level descriptions of enhancements to existing features
  • Resolved Issues: Lists customer-reported issues that are resolved in this release or known issues resolved from previous releases
  • Known Issues: Lists known issues that are applicable in this release

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.

PackageLatest Certificate Version
Conga Sign1.67.0

System Requirements and Supported Platforms

The following table lists the minimum requirements for installing and using Conga Composer.

System RequirementMinimum Supported Version
Salesforce Edition
  • Performance / Unlimited
  • Enterprise
  • Professional (limitations may exist)
  • Developer
  • Sales Cloud
  • Service Cloud
  • Force.com / App Cloud
  • Health Cloud
  • Financial Services Cloud
  • Quote-to-Cash
Browser
  • Google Chrome®
  • Mozilla Firefox®
    • See Mozilla getting started to ensure Salesforce works optimally with Firefox, update the browser’s configuration settings.
  • See Supported browsers for Salesforce Classic. Salesforce Classic is supported with Microsoft® Internet Explorer® version 9, 10, and 11, and Apple® Safari® version 11.x on macOS. The most recent stable versions of Microsoft Edge, Mozilla® Firefox®, and Google Chrome™ are also supported. There are some limitations.
  • Supported browsers for the Lightning experience. See the supported browsers and limitations for Lightning Experience.
  • Recommendations and Requirements for all browsers. For the best experience and security, follow these guidelines.
    • For all browsers, enable JavaScript, cookies, and TLS 1.2. If TLS 1.2 isn’t available, enable TLS 1.1. Browsers that don’t support TLS 1.1 or TLS 1.2 won’t be able to access Salesforce after we deactivate TLS 1.0. Deactivation has already occurred in sandbox orgs and concludes with production orgs on July 22, 2017.
    • Some features use iframes to work in Lightning Experience, so you must have the appropriate browser security settings for iframes to load correctly. Follow your browser’s instructions to enable working with iframes and third-party cookies. For example: In Internet Explorer, set the Launching programs and files in an IFRAME security setting to Enable orPrompt. In Safari, we recommend changing your privacy settings for cookies to Allow from websites I visit. In Chrome, make sure that Block third-party cookies and site data isn’t selected in the Content settings.
    • The minimum screen resolution required to support all Salesforce features is 1024 x 768. Lower screen resolutions don’t always properly display Salesforce features such as Report Builder and Page Layout Editor.
    • For Mac OS users on Apple Safari or Chrome, make sure the system setting Show scroll bar is set to Always.
    • Some third-party browser plug-ins and extensions can interfere with the functionality of Chatter. If you experience malfunctions or inconsistent behavior with Chatter, disable the browser's plug-ins and extensions and try again.
Template Software
  • Microsoft Office® 2016 (Mac or PC)
  • Adobe Acrobat® XI, Acrobat Reader
Adobe LiveCycle PDFs are not supported.
MobileCompatible with Salesforce1 and all mobile browsers when configured following the documentation.

New Features

The following features are new to Conga Sign this release.

Ability to configure email notification frequency

In this release, Conga Sign provides a new Setup Menu option to control what stages during the Conga Sign transaction you, the recipients, and signers all receive email notifications. 

As an Administrator, you can use the new menu under Conga Sign Setup to decide if an email notification is sent when a Transaction is Completed by all Signers, Cancelled, Expired, Sent, Reassigned, or Completed by each individual Signer. You can also have an email notification sent if the Transaction is Viewed by the signer, either for the first time it is viewed or every time. 

Get Started

For details on Configuring Notification Frequency, refer to Sender Email Notification Frequency Conga Sign Summer '21 Administrator Guide. 

New Conga Sign parameter

In this release, Conga Sign introduces a new parameter to allow a transaction recipient to reassign the Signer of the transaction. 

Get Started

For details on Conga Sign Parameters, refer to Conga Sign Parameters Conga Sign Summer '21 Administrator Guide. 

Ability to remove the Reassign Signer

In this release, Conga Sign provides a new setting that allows Administrators to remove the ability to reassign the transaction to a different Signer. 

As an Administrator, you can use the new menu under Conga Sign Setup to enable or disable Reassign Signer functions from either the received transaction, where recipients of the transaction can reassign to a different Signer or from a global organization level, where the Signer cannot be reassigned from a Transaction record in Salesforce. 

Get Started

For details on Remove Reassign Signer, refer to Configuring Remove Reassign Conga Sign Summer '21 Administrator Guide. 

Enhancements

The following enhancements are new to Conga Sign this release.

Enhancement for Audit Trail Signer and CC entries

In this release of Conga Sign, the transaction Audit Trail now specifies whether the transaction has been viewed by a Signer or a CC recipient. Signers appear in the Audit Trail as "Invitation email sent to...", while CC recipients appear as "Invitation to view sent to...". 

Get Started

For details on Audit Trails, refer to Audit Trails Conga Sign Summer '21 User Guide. 

Enhancement for Facilitator notifications for In-Person Transactions

In this release of Conga Sign, the Facilitator of an In-Person transaction no longer receives a "Transaction Sent" notification email. 

Get Started

For details on In-Person Signers, refer to In Person Signer Conga Sign Summer '21 User Guide. 

Enhancement for Business Units pre-populating Email and Subject lines

In this release of Conga Sign, the Email and Subject lines saved on a configured Business Unit populate on the Create Transaction screen. You can further modify these values on the Create Transaction screen.  

Get Started

For details on Business Units, refer to Business Units Conga Sign Summer '21 Administrator Guide. 

Resolved Issues

The following table lists the issues resolved in this release.

Case Number

Conga Internal ID

Description

00452237DCS-3797

When a 5 Day Expiration timer was set for a transaction, the timer began at the time the Transaction was sent, not when the Invitation to Sign was sent to the recipient. 

Known Issues 

There are no known issues in this release.


DOC ID: CSSUM21RN20210707