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 June 2018 Update

Released on June 5th, 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

Support for Automatically Claiming Any Sub-domain for SSO

Org Admin - Previously, Org Admins needed to explicitly verify every email domain and sub-domain used with SSO. You can now verify the root domain, and optionally, claim any sub-domain automatically without having to verify it with DNS each time.

eNotary

Support for California eNotary

We are expanding support of eNotary to include California to allow senders to request notarial acts and provide Notaries with the ability to host an in-person signing session to perform notarial acts within the U.S. Support for California is in addition to the current nine states. DocuSign eNotary is available in Enterprise Pro plans; eNotary is always free for the Notary hosting the signing session.

GDPR Compliance

Enable Personal Information Redaction

To support meeting their GDPR compliance needs, customers can request personal data redaction be enabled on their accounts as part of the Envelope Purge process. Contact your account manager or DocuSign Support to request this functionality be enabled.

Payments

PayPal Payment Method for Braintree

For customers using a Braintree payment gateway account for DocuSign Payments, signers now have the option to pay by PayPal, as well as by credit card. Previously, credit card was the only payment method available for the Braintree payments integration.

Sending and Templates

Allow Senders to Set Decimal Separator

For compatibility with European number 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 users' language.

Scale Signature and Initial Fields to the Same Size

For parity with the Classic Experience, Signature and Initial fields can be scaled by a percentage so that all fields are the same size.

Allow Senders to Delete Recipients When Using Quick Send

When templates were created with several potential recipients, users had to click Advanced Edit to delete any unnecessary recipients. This update lets users delete the extra recipients directly in the Quick Send/Use Template dialog box.

Signing

Header Scope Added to Keyboard Navigation for PDF/UA Documents

Using the NVDA screen reader during signing with a document that has PDF/UA header elements, users can now use keyboard shortcuts to navigate at the header level instead of just the page level, which was the previous behavior.

Deprecated Features

Demo Accounts Transitioning to the New DocuSign Experience on June 15

The vast majority of customers are using the New DocuSign Experience exclusively in preparation for the sunset of the Classic Experience on June 30, 2018. As a part of our transition to the New DocuSign Experience, all demo accounts will lose access to the Classic DocuSign Experience on June 15, 2018. This will bring demo accounts into closer alignment with production accounts.

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 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

Admin

  • Custom Destination URLs reverted to the DocuSign Default URL for customers who had multiple Brands with custom Destination URLs, and the customers were unable to update the DocuSign Default to their custom Destination URLs (ADMIN-4871).

API

  • When an envelope is initially created with recipients that have "embed-dedRecipientStartURL" populated, If a template is then applied to the envelope, all match-ing recipients inherit the properties from the template. As a result, "embeddedRecipientStartURL" is removed. This fix resolves that by preserving "embed-dedRecipientStartURL" if it already exists on the envelope, otherwise it accepts what is in the applied template (API-8116).

Sending and Templates

  • When a template had conditional fields where any had the Sender Permissions set to Mandatory (to prevent sender from deleting the fields), an editor of the template was prevented from changing conditional logic rules for any of the fields marked mandatory, or from adding any new conditional fields to a mandatory field (MAR-22099).
  • Templates could not be filtered by the last modified date (MAR-23710).
  • Quick searches for SMS or Phone Auth country code were not returning results based on the first letter in country names (i.e., typing F in the search field returned Afghanistan as the first result instead of France) (MAR-24279).
  • When users created a custom user activity report and added specific users, after they saved and ran the report, it was correct, but when they checked the list of users, random users were displayed in the Selected column (MAR-24560).
  • Users listed on custom reports could not be searched beyond the 200th entry (MAR-24941).
  • When a template required SMS or phone authentication, when the template was used to create an envelope, the focus in the UI was on the first recipient requiring SMS/phone authentication instead of the top of the UI (MAR-25441).
  • When attempting to change the country code for SMS authentication, some languages presented a blank drop down menu and users could not change the country code (MAR-25628).
  • Documents with a large number of pages were causing the document view/download page to freeze, preventing any further actions on the document (MAR-25719).
  • Senders without permission to delete recipients were seeing the "X" next to recipients' name, implying that they could delete the recipient. Clicking the X did nothing, causing confusion for the senders (MAR-25828).
  • When using a template with multiple recipients and with custom email subject and message for each recipient, and with "Don't allow senders to edit the subject, email, or private messages" enabled, the email Subject shown in the Manage page did not match the first recipient's email Subject (MAR-25882).
  • When viewing shared envelopes, the user named at the top of the UI did not match the user whose envelopes were being viewed (MAR-25936).
  • The New Experience did not create DocumentStatus IDs in the same way that the Classic Experience did (MAR-25943).
  • During correction, if recipient 2 was removed and a new recipient was added, the new recipient could not be recipient 2. This error appeared: "The current routing order is 3. Please enter a routing order equal or larger than that." (MAR-25955).
  • When a custom ID Check was set on a template, it was not honored (MAR-26199).
  • ID checks assigned to recipients on a template required the checks to be reassigned when editing the template (MAR-26322).
  • Adding a new template with a role that matched a completed signer added any non-sig-nature fields for the completed recipient to the new document (TT-759).
  • The next URI returned in the response to the following calls did not include the &order=desc&order_by=name query param statements that were used in the original request, which could cause ordering issues (TT-1212).

           api/accounts/\{accountId}/templates?user_filter=owned_by_me&start_ position=0&count=40&order=desc&order_by=name&folder_ids=\{folderIds}&modified_ from_date=2003-01-                               01T00:00:00.000Z&include=powerforms

           api/accounts/\{accountId}/templates?user_filter=owned_by_me&start_ position=0&count=40&order=desc&order_by=name&folder_ids=\{folderIds}&from_ date=2003-01-                                               01T00:00:00.000Z&include=powerforms

  • When a template with locked fields was created, and then an envelope was created from that template, the locked fields were not respected on a vDev get call from the getRecipientTabs endpoint (TT-1268).

    Signing

  • The Decline to Sign reason did not align properly with the radio button with which it was associated (SIGN-14709).
  • For senders who were also signers on an envelope with Sender Must Authenticate Sign-ing set to false, when they attempted to access the envelope through the Manage tab in the web app, they were required to authenticate (SIGN-16101).

When a recipient role was Needs to Sign, but all they had were Approve or Text Fields, the Certificate of Completion indicated that a signature was adopted by drawing it (SIGN-17230).

21 CFR Part 11

  • When sending a 21 CFR Part 11 activation to a closed, non-21 CFR Part 11 recipient, the recipient was not receiving an automatic activation email (TT-877).

Coming Soon

Sending and Templates

Signed in Location Link in Document Details

When recipients or hosts sign a document, a link will appear on the Document Details page that, when clicked, opens a new browser tab in Google Maps indicating the location where the document was signed. No link appears for any other recipient type (i.e., CC or Needs to View, etc.).

Restrict Changes on Radio Buttons Applies to Group

In Radio Button Groups, Restrict Changes will apply to the group as a whole, not to individual radio buttons. In the New Experience, users are able to apply the restriction to an individual button, but in the Classic Experience the restriction applies to the group. This brings the Restrict Changes behavior into parity.

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.

Recipient Preview

Users will have an enhanced Preview experience prior to sending. Senders will be able to view how documents will be presented to their recipients in different signing form factors (desktop, tablet, or phone).

V02 Responsive Signing Experience

Accounts on signing versions V1 and V2 are being 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.

Support for Signing V1 will be deprecated on July 15, 2018.

Bug Fixes

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

  • When two users have shared access to envelopes, the person with whom the envelope was shared cannot manage the envelope (they can correct, but not manage directly) (MAR-23673).
  • When adding documents to an envelope that has been generated from a template, the Preview Pane option on the tagger screen is blank and unresponsive. Users have to use the browser Back button to exit the preview screen (MAR-25669).
  • When preparing envelopes based on a template using DS EU Advanced signatures in combination with the advanced option "Don't allow senders to edit, add, or remove recipients.", the access code and phone number fields are disabled (MAR-25726).
  • When an envelope is created through an integration and a specific expiration/notification is set, and then saved as a draft, when the envelope is sent, the expiration/notification setting reverts to the DocuSign default (MAR-25914).
  • When looking at the number of envelopes expiring soon, the number of envelopes expiring on the day the list is viewed are not being shown in the detail list, but they are counted in the number of envelopes expiring soon shown on the dashboard (MAR-26229).
  • When a document has a large number of pages, clicking any thumbnail doesn't load the image in the document detail page and the UI becomes unresponsive (MAR-26279).
  • When using a template created in the Classic Experience in the New Experience, the recipientID changes (MAR-26284).
  • Templates with text fields that consist of only space characters are having those char-acters removed when the template is edited or when creating a new template with text fields consisting of spaces, causing some customers' processes to ignore the envelopes with the space removed, breaking their workflows (MAR-26288).

Addendum

Published on June 6, 2018

Removed From the Release

The following item was pulled from the June 2018 release, but not communicated in time to remove it from the Release Notes. It is currently scheduled for the July 2018 release.

Allow Senders to Set Decimal Separator

For compatibility with European number 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 users' language.

Added to the Release

The following bug fix was included in the June 2018 release, but not documented in the release notes.

  • Users used to be able to access PowerForms (not individual envelopes) that were tied to other DocuSign accounts that they owned from any account. Now, when users have multiple DocuSign accounts and they want to access a PowerForm, they must be logged in to the account associated with that PowerForm to access it (FRM-376).

« Back to Releases

Trustpilot