Read our blog for the latest insights on sales and marketing Take Me There

Webinar: Use Sugar Data to Easily Generate Complex Documents Register

Webinar: Advanced Calendar Solution for Sugar Register

DocuSign July 2018 Update

Released on July 6th, 2018

Note: Some features and options are supported only in certain DocuSign plans. Your account plan might not support some options in these Release Notes. For information about which options are available for your account, check your account plan or contact us.

New and Updated Features

Admin

User List Exports

User List Exports are powerful views of the users of your organization. Download and gain visibility of corporate users and their account memberships. The lists include information about each user on an account in your organization, log in policy exceptions, and external account memberships. Use these lists to gain powerful visibility into how users exist within your organization.

User list exports will be available to customers with access to Enterprise Pro or Organization Management in mid July.

Organization Delegate User Admin

Organization’s delegate User admin permission allows you to assign just user management rights to an organization admin. This limits the admin to just managing users for your organization, enabling you to delegate the responsibility of user management to the right person while maintaining the security of your account management. See the Organization Admin support documentation for full details.

Organization Delegate User Admin will be available to customers with access to Enterprise Pro or Organization Management in mid July.

Signing

Improved Cross-site Signature Adoption Behavior

In the past, when an envelope was created on one site and a signature or initials was adopted on a different site, the signatureid or initialid image returned from the signing event was site-specific. Now, the signatureid or initialid image returned is not tied to the site on which the signature or initials was adopted.

V02 Responsive Signing Experience — Rolled out to All Plans

Accounts on signing versions V1 and V2 have been upgraded to the V02 responsive version. This is a minor UI change that results in a more consistent and mobile-friendly signing experience across different devices.

This update has been rolled out to all plans.

Deprecated Features

Columns Removed from Reports

The following columns in reports will no longer be available as of August 2018. The columns were available in reports in the New DocuSign Experience for both live and scheduled reports. Any customers with reporting turned on who use these columns will be affected by this change

Affected columns and fields

  • Envelope Velocity (reportId: 4)
    • Total Documents
    • Total Pages
  • Envelope Report (reportId: 6)
    • #    of Documents
    • #    of Pages
    • EOD Status
  •  Envelope Status (reportId: 7)
    • Total Documents
    • Total Pages

Retiring Classic DocuSign Experience Documentation

As we wrap-up the transition from the Classic DocuSign Experience to the New DocuSign Experience, documentation supporting the Classic Experience is being removed from Google and Bing search results. If you want to find documentation on the Classic Experience, the Classic User Guide and the Classic Admin Guide will be available through June 30, 2018.

Other

TLS 1.0 Support and Other Weak Cipher Support to End June 25, 2018

DocuSign is ending support for TLSv1.0 and weak cipher suites on June 25, 2018. This date has been set by the PCI Security Standards Council and is an industry requirement to remain PCI compliant.

TLSv1.0 Support for Demo Environment Ends on May 29, 2018

This earlier date in Demo will help customers plan and test for the production cutoff date of June 25th. It will provide a period of time for customers to make any necessary updates to integrations before the production environments drop support for TLSv1.0.

The end of support dates for TLSv1.0 are:
Environment        TLSv1.0 Deprecation Date    
Demo                   May 29, 2018    
Production           June 25, 2018    

More information is available in the PCI Security Standards article Are You Ready for 30 June 2018? Saying Goodbye to SSL/early TLS.
 
The ciphers include 3DES as well as a few others that have an insufficient key length to securely encrypt communications. Following is the complete list:
  • TLS_ECDHE_RSA_WITH_3DES_EDE_CBC_SHA
  • TLS_RSA_WITH_3DES_EDE_CBC_SHA
  • TLS_RSA_WITH_AES_256_GCM_SHA384
  • TLS_RSA_WITH_AES_256_CBC_SHA256
  • TLS_RSA_WITH_AES_256_CBC_SHA
  • TLS_RSA_WITH_AES_128_GCM_SHA256
  • TLS_RSA_WITH_AES_128_CBC_SHA256
  • TLS_RSA_WITH_AES_128_CBC_SHA

TLSv1.0 and these cipher suites are used by a small set of customers to support legacy integrations. These integrations will need to be updated to support secure, modern ciphers. Updating is often as easy as recompiling the solution with updated libraries. The PCI Security Standards Council has published detailed guidance for migration from SSL and early TLS. It is available in the article Migrating from SSL and Early TLS.

For information on how to ensure that your access to DocuSign through browsers will not be disrupted, see the support article DocuSign is deprecating TLS 1.0 Encryption Browser Support.

TLSv1.0 and these cipher suites are used by a small set of customers to support legacy integrations. These integrations will need to be updated to support secure, modern ciphers. Updating is often as easy as recompiling the solution with updated libraries. The PCI Security Standards Council has published detailed guidance for migration from SSL and early TLS. It is available in the article Migrating from SSL and Early TLS.

TLSv1.0 Deprecation and Connect Listeners

We have received some questions from customers asking if their Connect listeners are also affected by TLSv1.0 deprecation, and the answer is yes. PCI compliance mandates that all inbound and outbound requests are required to deprecate TLSv1.0 connections along with the legacy ciphers cited previously.

For customers with Connect listeners, integration owners should ensure that their listener is capable of TLSv1.1 or higher to avoid any service interruptions after the cutoff date.

End of TLS 1.0 Support and How it Affects DocuSign Print Driver

All current versions of DocuSign Print Driver do not support TLS 1.1/1.2. This means that customers will not be able to use DocuSign Print Driver when support for TLS v1.0 ends.

Customers are encouraged to upgrade to Print Driver v3.1.4.x before support for TLS v1.0 ends (in Demo 5/29/2018 and in Production 6/25/2018). The new Print Driver version will be available from the DocuSign support download site by the end the week of May 7, 2018.

Bug Fixes

Sending and Templates

  • Dropdown fields were centered instead of being left-aligned when previewed before sending an envelope (MAR-28619).
  • When creating a PowerForm with multiple recipients, some of which were locked to prevent modification by unauthorized signers, the first recipient was able to skip required fields and to change locked fields (FRM-100)

Signing

During an in-person signing session, after clicking Finish, it was possible to cancel the host sign-in and to modify the envelope without re-authenticating (SIGN-16811).

HTML-encoded characters in custom viewing_event return URLs were translated to the actual character, breaking custom integrations (SIGN-17335).

When improperly completed conditional radio buttons were highlighted, and then subsequently completed, the red outline indicating the error was not removed (SIGN-17317).

Coming Soon

Sending and Templates

Add Envelope Status to PowerForm CSV Download

To let customers filter PowerForm responses based on envelope status, a column containing Envelope Status will be added to the CSV download file.

Filters on the Manage Page Persist for Session

When a user sets a search filter on the Manage page, that filter will persist during the current session, even when the user leaves the Manage page and then returns to it.

Allow Senders to Set Decimal Separator

For compatibility with European numbering formats, users can set the decimal separator in numeric values to a comma (,). If the value is not set, the format is based on the user's language.

Signing

Browser Support

Starting June 25, 2018, we will no longer support IE8, IE9, or IE10 for signers using Signing V02R. We are doing this in an effort to be more secure by deprecating support for TLS 1.0. You can see the updated list of supported browsers on the Support Site.

Manage

Keep Form Data in Signed PDFs

When a PDF document contains form data, and the sender chooses to keep form data, that data will persist in the PDF throughout the signing process and into the completed document. This applies to digital signatures, as well as standard electronic signatures.

This change will roll out to all accounts over the next several months, but can be enabled on demand by calling customer support.

Bug Fixes

The name-number is the internal DocuSign issue tracking number for the bug.

  • Anchor tags are missing when more than one template is applied (MAR-21331).
  • Correcting an envelope to move a recipient to an earlier routing order (one before the current setting) AND changing anything else (like recipient type) makes the other change, but correctly, does not change the routing order; however the user is not presented with an appropriate error message (MAR-23344).
  • When an admin creates and shares a template with a user, downloads the template as a ZIP file, and uploads the zipped template, it is shared with all users (TT-1286).

Addendum

Published on August 9, 2018

The following item that appeared in the July 2018 Release Notes leads to some confusion as to what parts of the DocuSign signing experience were affected. This work improved the consistency of already-existing cross-site signature adoption for the native mobile app, but did not affect other signing experiences.

Improved Cross-site Signature Adoption Behavior

In the past, when an envelope was created on one site and a signature or initials was adopted on a different site, the signatureid or initialid image returned from the signing event was site-specific. Now, the signatureid or initialid image returned is not tied to the site on which the signature or initials was adopted.

« Back to Releases

Trustpilot