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

Released on April 10th, 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


Specify Signing Date Format in Admin

When EnableCustomDateSignedFormat is enabled, Admins at the account level can specify the date format for signers in Admin > Signing Settings > Document Formatting. When EnableCustomDateSignedFormat is not enabled, the default date format is used.

Sending and Templates

Transfer Ownership of Envelopes and Templates from the Manage or Templates Page

Users can now transfer envelopes or template from the Manage or Templates page, respectively. The Transfer Ownership option is available from the More menu on either page, from the Use menu on the Templates page, and the Move menu on the Manage page. After selecting the envelopes or templates to transfer, users see a list of persons to whom they can transfer the envelopes or templates.

Select Multiple Envelopes or Templates

Users can now use Shift-click to select a range of envelopes or templates on the Manage and Templates pages. To select disconnected envelopes or templates, users click the checkbox for each one they want.

More Information Added to Bulk Send Errors List

When errors are found in a Bulk Send list, users now see the row number for each error as well as the reason for the error, making it easier to find and correct errors in long lists.

Improved Error Message for Invalid Formulas

When users enter an invalid formula, the first invalid element in the formula and all those following it are highlighted. The highlighted elements following the first error, may or may not be invalid; this is a known limitation of the error message.

Add Fax Number to Contact Card

When a contact has a fax number, that number is now automatically added to the contact card.

Download Form Data from Multiple Envelopes to a Single CSV File

For parity with the Classic experience, senders and admins can select multiple envelopes and download the form data from them to a single CSV file.

Specify Start Page When Applying Templates

Users can now specify a start page when applying templates. This provides more flexibility to users who use many template and document combinations that may not be page-to-page matches.

Download and Print a PDF from a Template

Users can now open a template, click a document thumbnail, and then print or download the resulting PDF file.

Envelopes Retain Recipient Signing Order from Template

For parity with the Classic Experience, when a user uses a template containing multiple recipients in a specific signing order, that order is respected in the New Experience.

Updated Message Displayed for Successful Envelope Correction

To alleviate confusion about whether a new email is sent to every recipient of a corrected envelope, the message users see when successfully correcting an envelope was changed from "Your envelope has been corrected and re-sent." to "Your envelope has been corrected." The corrected envelope is sent only to recipients who have not yet taken action and to any new recipients added as part of the correction.

Merging PDF Form Fields with Template Fields

When users upload a PDF containing form fields and then apply a template, if they choose to merge the PDF form fields with the template fields, when fields match, the data from the form field is placed on the document.

Deprecated Features

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.


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.

More information is available here:

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:


TLSv1.0 and these cipher suites are uses 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 here:

All internet browsers currently supported by DocuSign already default to newer versions of TLS, so this change will go unnoticed by web and mobile users. Contact DocuSign support if you have questions.

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 ( 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 do not see the "Only HTTPS" option on the System Updates 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

Sending and Templates

  • Radio buttons and checkboxes did not retain formatting (like font color) after the envelope was sent (MAR-11629).
  • Signers whose access to history and certificate of completion were disabled in Admin were still able to see some envelope information when opening the envelope's history (but nothing in the CoC). They can still open envelope history, but are no longer able to see any information (MAR-12191).
  • Users were presented with the confusing option to assign a sending brand when building a template even though sending brands are not available in the New DocuSign Experience (MAR-22310).
  • When an administrator on an account attempted to change the Template Modification settings and they were not the original creator or owner of the template, the Template Modi-fication settings weren't available to them (MAR-23637).
  • Users at Manage Envelope role were logged out after correcting an envelope opened with the email link (MAR-23660).
  • When adding fields, some customers intermittently had a problem where the field being placed would follow the cursor after the mouse button had been released (MAR-23728).
  • Using the SOAP API, when a group of radio buttons was added to an envelope, the first signer's selection was not retained when they finished. Adding an index number to each radio button label fixed the problem (MAR-23791).
  • Using DocuSign for Salesforce, users were unable to print documents prior to sending the envelope, receiving an unprintable image when they attempted to print the document (MAR-23837).
  • Using DocuSign for Salesforce, users were unable to print documents prior to sending the envelope, receiving an unprintable image when they attempted to print the document (MAR-23837).
  • On an account with Phone Authentication disabled, when users created a template with only a role name, saved the template, and subsequently edited the template to add a name and email for the role, phone authentication was added to the template causing the SOAP API call createEnvelopeFromTemplate to fail with the error "This Account lacks sufficient permissions. :: Phone Authentication is not permitted." (MAR-24409).
  • Envelopes sent from the web console that required paired authentication (for example, access code + SMS) had the authentication types swapped when the recipient was changed from Needs to View to Needs to Sign, or vice versa (MAR-24409).
  • When sending a new envelope and then either using or applying a template, when the user had selected the checkbox for Custom email and language for each recipient setting, the checkbox was cleared even if the template had the option selected (MAR-24562).
  • When users entered an invalid In Person host email address, the web console did not indicate that the address was invalid when creating the envelope. Validation has been moved to sending to eliminate this confusion (MAR-24621).
  • Users who were not administrators were able to create and share custom fields account-wide. They were also able to edit any custom field shared with them. The ability for non-admin users to share custom fields and to edit custom fields shared with them has been disabled to bring the New Experience into parity with the Classic Experience (MAR-24666).
  • When the restriction "Sender Permissions: Restrict changes" was applied to a field in a template, senders were able to override the restriction by double-clicking the field and typing any number of characters without encountering an error message. They will now receive the error message "Text that does not fit in the field will not be saved." if they exceed the number of characters allowed by the field properties (MAR-25390).
  • When using a template with some or all recipients with the same role name in different signing orders, after the first signer had completed their action, correcting the envelope to change the shared role name did not automatically update any remaining recipients with the new role name (MAR-25442).
  • When viewing the sent date for an envelope after one or more recipients had taken their actions, the original sent date updated to reflect the date the envelope was sent to subsequent recipients instead of retaining its original value (MAR-25443).
  • For parity with the Classic Experience, the New Experience will no longer create ran-dom recipientIDs when using composite templates (MAR-25478).
  • When templates with paired authentication (for example, access code + SMS) were used, the user's saved most-recently-used country code was not reliably populated for phone or SMS numbers (MAR-25520).
  • Using Internet Explorer, users were unable to reliably select the country code for multiple recipients in a template after setting the country code for the first recipient (MAR-25523).
  • An error occurred when attempting to save a custom field after setting up AutoPlace on the Add Fields page for a new envelope. (MAR-25528).
  • Customers were seeing inconsistent expiration dates when correcting an envelope. The web console was showing the expiration date based on the last sent date, but actual expiration date was based on the envelope creation date. The expiration date is now based on the first sent date, not the envelope creation date nor the most recent sent date (MAR-25558).
  • Draft envelopes were showing a sent date in the Envelope Details (MAR-25641).
  • When Knowledge Based Authentication was disabled for an account, senders were still able to see that option when selecting an authentication method (MAR-25676).
  • Templates successfully dragged to a shared template folder disappeared from that folder when the user logged out of DocuSign and logged on again (TT-1030).
  • When using a template created from a PDF that contained Form Fields, the X indicating a selected checkbox was larger than the original checkbox (TT-1046).
  • Envelopes with the characters ">" and "<" in the subject line had the characters incorrectly translated to ">" and "<", respectively (TT-1082).
  • The defined size of Note fields was not respected when added through the API or when an envelope was created through the API (TT-1088).
  • Senders were able to create formulas based on fields from different recipients. For parity with the Classic Experience, senders will now receive an error message that one of the fields is invalid and the envelope cannot be sent (TT-1091).
  • Directed navigation in envelopes containing templates that included a set field order plus anchor tags did not follow the set navigation order (TT-1092).
  • Conditional logic was lost when replacing a template containing the logic with the corresponding document (TT-1097).
  • Required access code authentication was lost when combining templates where only one of the matching roles had access code required (that is, the matching role did not require an access code) (TT-960).
  • When using the REST API to read field information, the status field was not returned. so there was nothing in the response to indicate whether an optional signature or initial field had been signed or initialed (TT-979).


  • When users attempted to adopt a signature by drawing it on Windows tablet in Internet Explorer, the drawing canvas scrolled while they were attempting to draw their signature, causing a line to be drawn while the canvas scrolled (SIGN-11522).
  • When an in-process envelope was corrected, outstanding users were directed to the DocuSign login page after signing (SIGN-12933).
  • Apostrophes ('), quotation marks ("), and ampersands (&) in Declined Reason text were rendered in ASCII codes (SIGN-14752).

Coming Soon

Sending and Templates

Sort Templates by Name

For parity with the Classic Experience, users will be able to sort templates by name on the Templates page.

Remove Get From Cloud Option when Connected Apps are Disabled

When all Connected Apps options are disabled, the Get From Cloud document source will no longer appear.

Draft Envelopes Creation Date

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


Change Signatures During Signing Session

This feature will allow signers to change the spelling of their names or to change their signatures after they have adopted a signature during a signing session. It will also allow account holders who have saved signatures to select, edit, or delete one during signing.

Bug Fixes

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

  • Users have no way to quickly find envelopes that have failed authentication (MAR-21932)
  • 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).
  • Some customers are seeing the old DocYouSign brand (MAR-23793).
  • The What's New label on some French user's home page is not being translated into French (MAR-23933).
  • 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).
  • Filter date ranges are not being preserved within a user session (MAR-25497).
  • Using offline signing, the completion time for an in person signer is incorrect (TT-1070).
  • Using a template with numerous AutoPlace fields takes an inordinate amount of time to present the Quick Send screen (TT-1142).

« Back to Releases