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
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.
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.
Audit logs now include changes made to Permission Sets.
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.
Allowing AutoPlace text to be scoped at the document level enables the following:
Contact your account manager for more information or for access to this feature.
Draft envelopes now show the creation date when viewing envelope details.
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.
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.
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.
When all Connected Apps options are cleared (disabled), the Get From Cloud document source no longer appears.
Users can now sort templates by name in the Select Templates dialog box.
For parity with the Classic Experience, users can now sort templates by name on the Templates page.
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.
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.
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.
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.
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
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 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.
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.
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.
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.
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.
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.
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.
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).
Fields that can be used for searching are:
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.
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).
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.
The name-number is the internal DocuSign issue tracking number for the bug.