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

Webinar: Document Merge in wMobile Desktop for GoldMine Register

DocuSign Summer 2017 Update

Released on June 2nd, 2017

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

New Admin Update

We released a change in New Admin June 6, 2017 that improves the way a user is created and defined within DocuSign. Previously, it was possible to create multiple users with the same email address, which caused a lot of confusion and conflicts. Creating multiple users with the same email address resulted in multiple accounts with different passwords, making it difficult for a user to log in to the right account. Moving forward, an email address can only belong to one user. We have updated the create user experience in New Admin to support this improvement in user management.

Keyboard Accessibility  Improvements

Coming soon: Senders in the New DocuSign Experience will be able to tab between fields and enter text directly without having to use a mouse. Basic options for each field will appear next to the selected field; advanced options will appear in the right navigation bar.

We expect to launch this in June, but the actual date is not yet finalized

Save as Template

Save as Template provides a quick way to make a template from a document that is already prepared. A user can save any document they have sent or drafted as a template. Everything that was added to the original document is included in the template. This includes all envelope data, including the recipient properties and message information, as well as all advanced option settings, such as reminders and expirations. The template also includes all documents in the envelope, plus all fields placed with any data you entered and all field properties.

Save as Template is new functionality in the New DocuSign experience.

System Updates Panel

A new panel, System Updates, available in DocuSign Admin, enables administrators to see and try important upcoming system changes that will affect their accounts. The panel initially contains updates for Connect and APIs. More updates will be available in the future.

Important: The System Updates panel will be released to DEMO in June, and to production in late June or July.

Payments Updates

DocuSign is expanding its Payments feature with a new payment gateway, (coming soon) the ability for signers to select bank transfers as a payment method, and access to some of the Payments API.

PayPal Payment Gateway

In addition to the existing Stripe payment gateway, you can now set up a gateway to use Braintree through PayPal. If you have a Braintree account, you can connect your Braintree gateway account to your DocuSign account to request payments into your Braintree account. In addition, because Braintree is owned by PayPal, you can connect your PayPal gateway accounts to your Braintree account, and then to your DocuSign account.

After you click the PayPal tile, you are taken to a sign-up process that is controlled by PayPal.

Admins can find documentation on how to add Payment Gateways here: Managing Payment Gateways.

Bank Transfers (Coming Soon)

We are in the process of finalizing the ability for signers to select Bank Transfer as a payment method to make payments directly from their bank account when paying while signing. This feature is in addition to Credit Card as a payment method and is only available for Stripe customers located in the United States.

We expect to launch this in June, but the actual date is not yet finalized.

Payments API

If Payments are enabled on your account, you now have access to the Payments API so that you can use the API to configure payment requests in DocuSign envelopes or templates. You can also use the API to check the status of payments.

Note: Admin features related to payments (for example, connecting your payment gateway account to your DocuSign account) are not available through the API.

Connect Send Individual Messages

The new Connect Send Individual Messages feature ensures that your Connect webhook listener will receive all the Envelope and Recipient notification messages for which your Connect and eventNotification subscriptions are registered. If this feature is not activated, messages are aggregated. Activate this feature on the System Updates panel in DocuSign Admin. This is an account-wide setting.

Important: The System Updates panel will be released to DEMO in June, and to production in late June or July.

Wider Signature Manifestations (21 CFR Part-11)

Customers using DocuSign’s 21 CFR Part-11 module can now opt for wider signature manifestations, which adds additional text (name, signing reason, and time stamp) to the right side of the signature as opposed to the bottom. This makes the signature wider but shorter, and enables it to fit many FDA forms.

Connect HTTP Listener Sunset Reminder

Currently, the DocuSign Signature developer system ( can be configured to make Connect webhook calls to customers’ servers through HTTP or HTTPS connections. 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.

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.

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

Organization Administration (May - Updated)

Introducing a powerful infrastructure for advanced administrative capabilities that helps you manage, configure, and control your company's use of DocuSign. Organization Administration centralizes account, user, and identity management so you can better govern how DocuSign is used in your company. You can:

  • See how DocuSign is being used in your organization through centralized visibility and management
  • Keep your organization’s information secure with visibility and management of your domain users
  • Streamline and simplify user management through a centralized user-centric management experience

Beginning April 28th, as an existing SSO customer, you have early access to Organization Admin in Demo. Starting June 6th, Organization Admin will be enabled on your accounts in Production.

For more information about Organization Admin, see this article.

Search by Envelope ID (May)

In addition to being able to search for a document by document name, recipient name, and recipient email, you can now search by Envelope ID in the New DocuSign Experience. This feature shipped in February.

For more information about searching for documents in the New Experience, see this topic.

Terminology Update (May)

We are introducing the term envelope to the New DocuSign experience to refer to the containers, which hold documents, that are used to get signatures. This update will make it easier for first time users, as well as for those who may be more familiar with the Classic DocuSign experience and are transitioning to the new experience. To help make this update consistent, we will also rename the Documents tab to the Manage tab on the home view.

These changes are currently scheduled to appear in demo in the May 2017 release, and in production in the June 2017 release.

Domain Updates for Direct API Deployments (April)

DocuSign intends to provide the most robust and reliable service possible to enable your business transactions. We also want to proactively share information that may be of interest to our customers regarding the evolution of our service. A few of our customers have elected to explicitly allow domains advertised by our service. If you want to allow DocuSign domains, we recommend that you use the following domains.

What Domains Should I Allow?



Port: 443

What Should I Do?

  • If you don’t have any explicit settings in your firewall to use DocuSign services then you do not need to do anything
  • If you have configured your firewall to explicitly allow internet addresses based on published IP ranges, then you do not need to do anything
  • If you have configured your firewall to allow a list of domains to use DocuSign services, then you need to work with your network operations team to check and update the list
  • If you are not sure what your firewall settings are, contact your DocuSign Account Representative for help

What Are the New Domains?

We are adding the following new domains to DocuSign services:

  • Port: 443

When Will I See These New Domains?

These new domains will be available in March 2017.

I Need More Information

Refer to the Domains section on the DocuSign Trust Center for more information.

Shared Template Folders (April)

Users with Template share permission can create shared template folders to make it easy to share templates with other account users and groups. This feature provides parity with the Classic DocuSign Experience.

To set up a shared template folder

Simply add a shared folder and use the Share option to select the users and groups you want to share the folder with.

Then drag templates into the folder to share them. Users will see the new folder in their Shared Folders collection, and be able to use any of the templates you add to the folder.


Keep in mind the following when you share a template:

  • Sharing grants the selected users or groups the right to edit the template, provided the users have the necessary permissions (template create or share). To protect a shared template, you can set a password or lock parts of the template.
  • Anyone with access to the shared folder and who has template share permissions can also add and remove templates from the shared folder.

Bug Fixes

Note: Issue numbers that are in bold text are externally reported bugs or customer commitments that were fixed in the listed release or service pack.

Summer '17 Release Notes Bug Fixes

The following bug fixes were deployed to the DocuSign Production environment on June 2, 2017 as part of the DocuSign Summer '17 release. The name-number is the internal DocuSign tracking number for the bug.

  • Connect Completion events can be missed: it is possible, though rare, for the Connect system to miss Connect or EventNotification envelope Completed events, and for those events not to be sent to your webhook listener. To ensure that all events are reported correctly to your application, use the System Updates panel to activate the Send Individual Messages update for your account. (CONNECT-712)
  • When signers changed the language for signing, the Certificate of Completion did not respect that setting and rendered only in English. With this fix, the Certificate of Completion renders in all supported signing languages except Arabic, Hebrew, and Farsi. (GLOB-47)
  • When drop-down tags were used in a template and the document created from that template was used on an iOS device, the drop-down menus were not responsive to the device size and covered the document text. (SIGN-10968)
  • When drop-down tags were created with fixed widths narrower than the default, that fixed width was ignored and the drop-down reverted to the default width. (SIGN-11396)
  • When drop-down tags were created with fixed widths longer than the default, that fixed width was ignored and the drop-down reverted to the default width. (SIGN-11515)
  • When attempting to add a user as an in-person signing host who was on a different server than the sender, the Classic experience and the New experience produced two different errors. In Classic, the envelope was sent, but the host's name was replaced by the signer's name; in New, the envelope was not sent and an error message appeared indicating that the host was not an active DocuSign user even though they were. (SIGN-11721)
  • After signing on a mobile device, if users tapped the Back button on the after-signing landing page, they were not redirected to the completed document, or to the document view if signing was incomplete. (SIGN-13247)
  • When using Knowledge Based Authentication, and after users entered the required verification fields, the form enabled the NEXT button, but if the users hit Enter on the keyboard instead of clicking the NEXT button, the form was submitted with the CANCEL action. (SIGN-13364)
  • When a template was set up with fields stacked on top of each other that were triggered by selecting a checkbox on the sent document, the inactive fields masked the active fields. This only occurred when returning to a Finish Later document (SIGN-13530).
  • Powerforms did not handle eNotary flow properly (TT-183).
  • The scaleValue in an uploaded template did not match the value in the original template (TT-421).

May '17 Service Pack Notes Bug Fixes

  • The email link in the envelope complete notification for CC recipients in a Signing Group did not work (DCMT-72).
  • Step 5 of an in person signing event continued to appear after editing the Signing Resource file to make blank (SIGN-12950).
  • A mismatch in timeouts between the UI and the API caused errors when editing or using templates in the New DocuSign Experience (TT-7).
  • Searching for a shared document in the Classic Experience returned the document, but the same search in the New Experience did not return the document (TT-54).
  • When an admin attempted to update a template for which they were not the owner, they were not allowed to make the update (TT-194).
  • When attempting to correct an envelope using View As... in the New Experience, the non-owner received an error and was unable to complete the correction (TT-197).
  • Sending an envelope from a template that used hidden values as well hidden text to be shown and disabled the hide with asterisks feature (as Auto Place caused the TT-263).

 April '17 Service Pack Notes Bug Fixes

  • When one member of a signing group did not complete signing, either by canceling their changes or the session timing out, the document remained locked, preventing any other member of the group to complete signing (DCMT-219).
  • Changing the language to Farsi when signing, and then selecting Other Actions -> Decline to Sign resulted in the placeholder [[DocuSign_FinishLater]] appearing in the confirmation dialog box (GLOB-42).
  • CFR part-11 signatures now display time in the signer’s time-zone (GRUS-77).
  • Editing shared fields did not always highlight the changed fields for other recipients (SIGN-6249)
  • An in-person host's title was appearing in the Title field, requiring the signer to modify the field before they could finish signing.(SIGN-11808).
  • The redirect URL for CC recipients defaulted to white text, which on white or light backgrounds was difficult to see (SIGN-11963).
  • During an embedded signing session using IE10, when the user clicked the back button, an Unexpected Data Event error prevented a continuation dialog box from appearing, which halted the signing session (SIGN-12430).
  • Branding URLs did not appear in the same order on the mobile app as they did on the desktop app, causing concern that customers could not specify the primary URL in both experiences (SIGN-12476).
  • Screen readers were not announcing the Change Language button correctly (SIGN-12623).
  • Screen readers were not announcing the Other Actions button correctly (SIGN-12624).
  • IDR zones in a saved template were duplicated when the template was reopened (TT-55).
  • Auto-placed radio buttons in a template shifted position when sending from the template (TT-144).
  • Turning off all email notification preferences were not honored (TT-163).
  • One or two envelopes in a large bulk send appeared to send but were immediately deleted (TT-170).
  • Users were unable to make any changes to their email notification settings (TT-178).

« Back to Releases