Release Notes contain the following information about Conga Sign Spring21.04.05 Release (Conga Sign 1.63.0 Release).

For more information on new features, enhancements, and document improvements refer to

  • What's New in the Conga Sign Spring '21 User Guide or
  • What's New in the Conga Sign Spring '21 Administrator Guide
  • 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.


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.

ProductLatest Certificate Version
Conga Sign1.63.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
  • / App Cloud
  • Health Cloud
  • Financial Services Cloud
  • Quote-to-Cash
  • 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 feature is new to Conga Sign in this release.

Ability to Sign Multiple Documents in a single Conga Sign Transaction

In this release, Conga Sign provides the ability to send multiple documents for signing within a single Conga Sign Transaction. While sending documents for eSignature you can select multiple documents and specify the sequence of documents to be signed.

As a recipient, you receive an email notification from Conga Sign with a list of document names in the email body. When you click the View Document link in the email, it opens all documents in a single transaction. Once the signing process is completed and all recipients have finished signing, click the Download Document button to download a .zip file containing all of the signed documents. You receive another email that contains a link to the audit trail as well as all PDF attachments signed for a transaction.

As a sender, you can view all the documents in the Conga Sign Documents related list on the Transaction page layout. 

You can also send multiple documents for eSignature in a single transaction using Conga Composer, by using the CSMultiDocs=1 and ZipFiles=0 parameters. 

Get Started

For details on sending multiple documents for eSignature and signing a document, refer to Sending Documents for eSignature and Signing a Document in Conga Sign Spring '21 User Guide. For more details on the CSMultiDocs parameter, refer to CSMultiDocs in Conga Composer Spring '21 Parameter Guide.


There are no enhancements in this release.

Resolved Issues

The following table lists the issues resolved in this release.

Case NumberConga Internal IDDescription

When a CC recipient clicked Send new link button after the original link expired, the CC recipient received the email in the signing email template.


When Guided Signing was enabled and you clicked into a writeback tag, the Next and Back buttons did not move to the position of the manually selected writeback tag.

Known Issues 

There are no known issues in this release.