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

Released on May 4th, 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

Envelope Purge

An account admin will be able to send individual envelopes to the document purge queue through a new tool in Admin, Envelope Purge. This lets admins search for completed, declined, or voided envelopes within the account, and to mark them for purging. The admin will also be able also to purge envelope metadata, if necessary. After an envelope has been marked for purging, it will enter the standard envelope purge queue. Envelope Purge leverages existing Document Retention functionality, see the Document Retention support guide for details.

Permission Set Updates Added to Audit Log Content

Audit logs now include changes made to Permission Sets.

Automatically Activate User Memberships

Organization admins will have the ability to automatically activate user memberships— removing the requirement for users to activate their accounts via email. Applicable for domain users on accounts linked to the Organization, this is important for embedded workflow scenarios or when the signer must have an active account membership.

Sending and Templates

AutoPlace Text Scope Can be Set at Document Level

Allowing AutoPlace text to be scoped at the document level enables the following:

  • One template can use an AutoPlace string for a field definition that may be present in another template document or substitution document for that template. The field will not populate on any other template.
  • Two or more templates can use the same AutoPlace string for different field definitions. Field definitions in different templates will not interfere with each other.
  • An envelope can use the same template multiple times. The fields will not duplicate within the envelope.

Contact your account manager for more information or for access to this feature.

Draft Envelopes Creation Date

Draft envelopes now show the creation date when viewing envelope details.

Purged Envelope Indicator

The Manage page and the Envelope Details view now clearly indicate whether an envelope is about to be purged, and the date and time it will be purged. For more information about this feature, see Purge Envelopes on the support site.

Updated Template Matching Feature

When a multi-page document has more than one template that matches the pages in the document, a dialog box appears suggesting matching templates for each corresponding page range.

Phone Numbers Automatically Added When Using Authentication

When users are preparing an envelope and include a contact with an existing phone number, that phone number is automatically added when the users select SMS, Phone, or Fax authentication. If there is more than one existing phone number, the user can select the number from a list that appears.

Remove Get From Cloud Option when Connected Apps are Cleared

When all Connected Apps options are cleared (disabled), the Get From Cloud document source no longer appears.

Sort Templates on Select Template Dialog Box by Name

Users can now sort templates by name in the Select Templates dialog box.

Sort Templates by Name

For parity with the Classic Experience, users can now sort templates by name on the Templates page.

Signing

Change Signatures During Signing Session

This feature lets signers change how their names are spelled or change their signatures after they have adopted a signature during a signing session. It also lets account holders who have saved signatures select, edit, or delete one during signing.

Manage

Resending an Envelope with an Updated Signing Group Updates the Signing Group in the In-flight Envelope

When users update a signing group without updating any in-flight envelopes using the signing group, resending the envelopes updates the signing group in the envelope. Additionally, updating a signing group before an envelope reaches the signing group recipient, updates the signing group on the envelope.

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.

Switching Between Accounts Across Sites

Switching between accounts across sites (for example, NA2 and EU) will cease to work in the Classic Experience after April 30, 2018. It will not be implemented in the New DocuSign Experience. Because of data sovereignty concerns, account switching between linked DocuSign accounts on different sites will no longer be supported. Users will have to log out of one DocuSign account and log in to another DocuSign account to switch between accounts on different sites.

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.

Connect Mutual TLS Certificates Renewal

Update your Connect Mutual TLS certificates for your environment by the dates listed under Important dates.

Who is affected

DocuSign customers who use the optional Mutual TLS feature with either Connect or the Envelopes::create API call with the eventNotification parameter.

Connect can be configured to respond with its X.509 certificate in response to a request from the customer's web server (Mutual TLS). Different certificates are used for DocuSign Demo, North America (NA1, NA2, and NA3), and European (EU) environments.

What you need to do

If your Connect web server uses Mutual TLS with DocuSign, you must update your server by the following deadlines based on your environment.

Important dates

March 9, 2018: The renewed Demo, NA (the same cert applies to NA1, NA2, and NA3), and EU certs will be available on the DocuSign Public Certificates page on the Trust Center.

  • Demo Cert Update
    • March 14, 2018: The renewed Demo certificate will be available for your integration on the Demo environment.
    • May 2nd, 2018: This is the deadline by which your integration must start using the renewed cert. We will drop support for the current Demo cert on this date.
  • EU Cert Update
    • April 11th, 2018: The renewed EU certificate will be available for your integration on the EU environment.
    • May 16th, 2018: This is the deadline by which your integration must start using the renewed cert in EU. We will drop support for the current EU cert on this date.
  • NA Cert Update
    • April 18th, 2018: The renewed NA certificate will be available for your integration on the NA environment.
    • May 23rd, 2018: This is the deadline by which your integration must start using the renewed cert in NA. We will drop support for the current NA cert on this date.

Connect HTTP Listener Sunset Reminder

The DocuSign Signature developer system (demo.docusign.net) can be configured to make Connect webhook calls to customers’ servers through HTTP or HTTPS connections 

only if the demo account was created before July 2017. The production systems only support HTTPS connections, but in certain situations, customers are able to use HTTP.

HTTP should never be used for sensitive information, including DocuSign Connect notifications.

We will be updating both systems to no longer allow HTTP Connect notifications.

If your Connect listener is currently using HTTP, you must update your server to support HTTPS. Free HTTPS certificates are available from the Let’s Encrypt project. Self-signed certificates are not supported.

These changes also apply to eventNotification Connect webhook listeners.

Summer '17 Update

The June (Summer '17) release adds the setting “Only HTTPS” to the System Updates panel in DocuSign Admin. Activate this setting to ensure that your account is only using HTTPS for Connect and eventNotification webhook subscriptions.

Note: If you see "Only HTTPS" option in the System Update page, your account is already configured to use HTTPS only.

Important dates

June 15, 2017: New accounts on either demo or production systems created after this date will not be able to use HTTP for their Connect listener servers.

May 1, 2018: No account on either demo or production systems will be able to use HTTP.

On this date, any system still using HTTP for its Connect listener will stop working.

If you are currently using HTTP for your Connect or eventNotification listeners, we recommend that you update your server to use HTTPS as soon as possible.

Bug Fixes

API

  • Allows a user who is a member of an envelope's signing group to access the envelope in their shared folder even if they were not the sender or a signer of the envelope. Before this change, the user who was in the signing group would only see the envelope if they were the sender or had signed it. (API-8070).
  • Fixed an issue where envelopes created through the API were not displaying Salesforce merge field values in fields when the draft envelope was displayed in the New Experience (API-8218).

Sending and Templates

  • When an editor adds an agent and signer in a later routing order, the editor is forced to enter the signer's information, which should be entered by the agent in the later routing order, not the current editor (MAR-23335).
  • When users were viewing envelopes in a shared folder, if they clicked the Sent folder in the shared envelopes folder they were directed to their own Sent folder, not the shared Sent folder (MAR-25930).
  • Users have no way to quickly find envelopes that have failed authentication (MAR-21932)
  • Some customers are seeing the old DocYouSign brand (MAR-23793).
  • When downloading a CSV envelope report, the number of envelopes was correct, but the list contained some duplicate envelopes and excluded envelopes that should have been included when compared to the web console list (MAR-23888)
  • The Shared Envelopes label is not being localized on some customer's accounts (MAR-24785).
  • Users are receiving the error "The In Person Signing Host must be a valid user." when they enter the in person host's email address before entering the host's name (MAR-24785).
  • When sending an envelope with multiple documents and a large number of recipients and using Document Visibility, the list of recipients and icons is misaligned (MAR-25439).
  • When adding drop down fields to templates, the fields were the correct width (wide enough to list the longest option), but during signing, all drop downs were only 50 pixels wide (MAR-25448).
  • When sending an envelope with multiple documents and a large number of recipients and using Document Visibility, the list of recipients and icons is misaligned (MAR-25439).
  • When deleting a page in a multi-page envelope, the page was still visible to signers and fields on the following page moved to the "deleted" page (MAR-25762).
  • The What's New label on some French user's home page is not being translated into French (MAR-23933).
  • When attempting to replace an existing signature, neither the old nor the new signature appeared in the Signatures section of My Preferences (MAR-25958).
  • When a template containing conditional logic applied to radio buttons was downloaded, uploaded to the same or different account, and then applied to a new envelope, the conditional logic was deleted (TT-1026)
  • Using offline signing, the completion time for an in person signer is incorrect (TT-1070).
  • Using a template with numerous AutoPlace fields took an inordinate amount of time to present the Quick Send screen (TT-1142).
  • Templates that were imported from another account and moved to a template folder did not remain in the folder to which they were moved (TT-1156).
  • When attempting to upload a CSV file for bulk send to a template with a locked recipient as well as a bulk send recipient, the CSV upload failed (T-1173).
  • When sorting templates by name, if users used From Date the resulting list was different from the list that resulted when they used Modified Date (TT-1210).
  • In the New Experience, a template with hundreds of formulas took significantly longer to load than when using the same template in the Classic Experience (TT-794).

Signing

  • When multiple signers were assigned a shared text field, and an early signer deleted or changed the value of the shared text field, subsequent signers saw the original value in the field (SIGN-15834).
  • When signing an envelope on mobile web, after signing was complete, users were redir-ected to the old mobile web view, not the New Experience view (SIGN-16335).

Coming Soon

Sending and Templates

Allow Senders to Lock Name and Email Fields

When Allow Sender to unlock pre-filled email/name for Send to Manage recipients is enabled, users will see the Lock Name and Lock Email options in the Advanced setting. These two checkboxes will enable the users to change the settings AgentCanEditName and AgentCanEditEmail. By default, these settings will be set to true. This means that if the Allow Sender to unlock pre-filled email/name for Send to Manage recipients is disabled, then the two settings will not be shown and set to true (the Managers should be able to change pre-filled emails/names).

Users Will be Able to Select What Field to Search for Templates

Fields that can be used for searching are:

  • Template Name
  • Owner Name or Email
  • Recipient Name or Email

Filters on the Manage Page Persist for Session

Signing

Browser Support Changing

As of June 25, 2018 we will no longer support IE8, IE9, IE10 for signers using Signing V02R. We are doing this in an effort to be more secure by deprecating support for TLS 1.0. See the updated list of supported browsers for more information.

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, Phone).

Phone Authentication Update

We are moving to a new phone authentication system, although both are in use today. All new accounts are set up to use the new system, which does not support voice recording, but provides better quality and a cleaner, more intuitive interface for the recipient.

In the summer of 2018, existing accounts on the old version will be transitioned to the new version; however, the schedule is yet to be determined. The new version is available to existing accounts should they want to switch immediately.

For more information about the two versions, see How Phone Authentication Works.

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.

Bug Fixes

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

  • Template creators/editors are unable to edit, delete, or add new conditional logic in a parent field when any child field is required for only the sender (MAR-22099).
  • Users who have shared envelope management permission cannot manage an envelope without correcting it first (MAR-23673).Templates cannot be filtered by the last modified date (MAR-23710).
  • When a user who does not have "Allow sender to set email language for recipients” permission attempts to send an envelope with bulk send recipients who have customized email subjects and messages, the envelope appears to send, but actually fails silently with no error message to the user (MAR-24506).
  • When users create a custom user activity report and add specific users, after they save and run the report, it is correct, but when they check the list of users, random users are displayed in the Selected column (MAR-24560).
  • Users listed on custom reports cannot be searched beyond the 200th entry (MAR-24941).
  • When users move a report from the Classic Experience to the New Experience, the filtered users list inside a report is cut short (MAR-25013).
  • When attempting to change the country code for SMS authentication, some languages present a blank drop down menu and users cannot change the country code (MAR-25628).
  •  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 unavailable (MAR-25726).
  • Users who employed the former Any Signer feature are not able to view any envelopes sent to them using Any Signer (MAR-25739).
  • A user with the "Can add fields" permission disabled can send a bulk send template, but no fields are assigned to the bulk send recipients (MAR-25860).
  • When using a template with multiple recipients and with custom email subject and mes-sage 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 does not match the first recipient's email Subject (MAR-25882).
  • The New Experience does not create DocumentStatus IDs in the same way that the Clas-sic Experience did (MAR-25943).
  • During correction, if recipient 2 is removed and a new recipient is added, the new recipient cannot be recipient 2. This error appears: "The current routing order is 3. Please enter a routing order equal or larger than that." (MAR-25955).

« Back to Releases

Trustpilot