Release Notes contain the following information about Conga Sign Spring '21 Release (Conga Sign 1.62.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.

ProductLatest Certificate Version
Conga Sign1.62.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 in this release.

Guided Signing

In this release, Conga Sign introduces the Guided Signing feature. When this feature is enabled, signers can navigate to the locations of each assigned Conga Sign tag in the document while signing. By default, the Guided Signing setting is disabled. The Conga Sign administrator can enable the Guided Signing setting from Conga Sign Setup. 

Get Started

For details on Guided Signing, refer to Setting Guided Signing in Conga Sign Spring '21 Administrator Guide. 

Final Document Delivery 

In Conga Sign Setup, administrators can now choose how completed documents are delivered to recipients. Conga Sign provides functionality to deliver the final document as an attached PDF in an email, a PDF file downloaded from a download link in an email, or both.

Get Started

For details on the final document delivery feature, refer to Setting Final Document Delivery Options in Conga Sign Spring '21 Administrator Guide. 

Enhancements

The following enhancements are new to Conga Sign in this release.

Enhanced Signing User Interface for Mobile Device

In this release, the user interface of the Signing Document is enhanced for mobile devices. As a signer, you can show or hide the footer while signing a document on mobile. 

Purge Attachments after Salesforce Sync 

To maintain data privacy regulations, Conga Sign deletes attachments uploaded by signers after attachments are successfully synced to Salesforce.

Salesforce API Upgrade

Conga Sign has upgraded its Salesforce API version to v50. 

Resolved Issues

The following table lists the issues resolved in this release.

Case NumberConga Internal IDDescription
NADCS-3541

When a user tried to update the Transaction Expiration date and there was a conflict in the time zone and operating system time, the date picker reset to a previous day or two days before the set date.

NADCS-3305

When Conga Sign replaced pre-tag syntax with signer tags in the document, some of the document contents were either removed or shifted to a different location. 

NADCS-2644

When a user opened Preview and Tag screen, the resize handles were visible on the first tag in the document. 

NADCS-1985

When dragging text tags to resize on Preview and Tag screen, the medium font size was displayed between large and x-large.

The following table lists the issues resolved in Conga Sign Spring '21 Preview Release (Conga Sign 1.60 Release).

Case NumberConga Internal IDDescription
NADCS-3475

When signing a document on a mobile screen in landscape mode, the Signature Style Selection window viewport was very narrow for interaction.

Resolution: The Signature Style Selection window dimensions are expanded to fill the screen. Now the user can easily interact with the content of the Signature Style Selection window.

NADCS-2269The signers were unable to change the language of disclosure electronic record and signature disclosure prior to agreeing to terms and signing.

Known Issues 

There are no known issues in this release.


DOC ID: CSSPR21RN20210303