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

Released on December 8th, 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 Experience Additions and Updates

The following sections describe additions or updates to the New DocuSign Experience.

Invalid Password Lock-out Configuration Change

Currently, when a user enters an invalid password 10 times, they are locked out of the system for a period of time. For security and compliance reasons, the number of invalid password attempts has been changed to six.

Update to Bulk Download Fields

The field APIUserName is now included when Admins or Delegated Admins download user data to a CSV file. This field is required when Admins update users in bulk.

Admins Can Update User Membership Attributes in Bulk

Admins or Delegated Admins can update the following user membership information in bulk:

  • First Name
  •  Last Name
  • Permission set
  • Groups
  • Company name
  • Job Title
  • Address Line 1
  • Address Line 2
  • City
  • State/Region/Province
  • Postal Code
  • Phone
  • Language

The following fields cannot be updated in bulk:

  • Email Address
  • Log in Policy
  • Federated ID
  • Status

The following fields are required. If either is omitted from the CSV file, the update fails:

  • UserEmail
  • APIUserName

An Organization Admin User Manager Can Add, Edit, and Close Non-admin Users

An Organization Admin User Manager can perform the following administrative tasks:

  • Add new users
    • Assign the user any permission set that does not have admin related rights at the account level
    • Assign the user any group
    • Cannot add or grant organization permissions to a user
    • Hide DocuSign Admin or other admin related roles from the permission set drop down
  • Edit users
    • Edit attributes on any user that is not an Organization Admin. Attributes include: First, Middle, Last Name, email address and domain (as applicable), language, address, phone, company, job title (if available)
    • Cannot edit the log-in policy
  • Edit permissions and groups on any membership that is not an admin related permission set
  • Cannot assign a user a permission set with admin rights
  • Edit the some membership information outside of the permission set: address, phone, company name, job title
  • Set the default account
  • Change the default account on any membership for users that are not Organization Admins
  • Close users
    • Close memberships that are not admin related permission sets
    • Cannot close a user that has a membership with admin related rights and therefore cannot close the user either

Authoritative Copy Can be Set at the Document Level

When Authoritative Copy is not set at the envelope or account level for all, if document-level authoritative copy is enabled, users can set it for individual documents, either in the API or in the web app.

Notarize Page Field

To alert Notary recipients that they must take some action on specific pages in a document, senders can place the Notarize page field on pages where that action is required. The field is only available for Notary recipients, and only one field per Notary recipient per page is allowed. No other fields are allowed for Notary recipients. The field can be optional or required.

In the signing experience the Notary recipient sees a banner at the top of each page that requires action, as well as an indicator on the page thumbnails. They are prompted to drag and drop a field onto the page to complete the action. If they do not take action, they cannot finish the document.+

Specify X/Y Offsets for Fields

For parity with the classic experience, users can specify X/Y offsets or widths (in pixels) when placing fields on documents.

Resize Stamps in Signing

When signing and applying a stamp, users can resize the stamp up to 101.6 MM (4 inches) unless the stamp width is specified in the API (as it is with Shachihata stamps).

Send to Drafts – Sunset December 1, 2017

To ensure the ongoing security and scalability of the service, the send to drafts feature will be decommissioned on December 1, 2017. In case you aren’t familiar, this feature allows users to send an email to drafts@docusign.com, and then return to DocuSign at a future date to add fields and send the enclosed documents.

A lot has changed since we introduced this feature years ago – notably, we’ve released highly reviewed DocuSign mobile apps that help users send and sign documents anywhere. We have also made numerous improvements to the DocuSign user interface to help users send envelopes faster than ever before. We encourage users to use the mobile application (on iOS or Android) or DocuSign’s web experience for sending envelopes.

Please start using the DocuSign mobile app or DocuSign.com for all your sending scenarios.

IE 10 Support in Sending

To provide a more robust and secure experience to our customers, the New DocuSign Experience (NDSE) will remove support for Internet Explorer 10 in the December service pack. Presently, IE 10 is the lowest supported version in NDSE. After this change, Internet Explorer 11 and Microsoft Edge will be the lowest supported versions in NDSE. Signing will continue to support Internet Explorer 8 and higher to ensure that our customers’ signers can complete envelopes.

Microsoft’s support for Internet Explorer 10 ended in January 2016.

For more information about system requirements, including browser support, see System Requirements on the DocuSign Support Center.

File Types No Longer Supported

Due to low use, uploading Kingsoft Office .ET and .ETT documents into a new envelope will no longer be supported starting with the December service pack.

In addition to .ET and .ETT file types, the following types will also no longer be supported:

.ICO, dps, dpt, et, ett, swf, wps, emf, and wmf.

For more information about supported file types, see Supported File Formats on the DocuSign Support Center.

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.

This experience has been rolled out 100% in Demo, Web, Individual, Business Pro, and Enterprise plans.

November Additions and Updates

Admins Can Provide an Address and Phone Number When Adding Users

An Admin or Delegated Admin can add work address and the phone number in the

membership record to a user's membership profile when adding or editing a user.

Display, Clear, or Copy a User's Federated ID

Organization Admin: Federated ID's will be listed on each organization user's page under Security for each Identity Provider for which they have a Federated ID and are a member of a reserved domain. Users without Federated IDs will be indicated by No Federated ID configured for this user. Organization Admins will be able to clear an ID, as well as copy the ID to the clipboard. For more information, see this topic.

Organization Admins Can Update the Organization Profile

Organization Admin: Admins can update the organization name and description in the organization profile

Last Update Date Will Update to Show Most Recent Sent Date

For parity with the classic experience, when an envelope is resent, the Last Update column on the Envelope Details page changes to show new sent date. In addition, the original sent date appears under the envelope label.

Updated View As Experience

When viewing shared envelopes (formerly shared folders), users will be presented with a dialog box to let them choose or search for the person who has shared an envelope with them. In the past, when users had many envelopes shared with them, the View As feature presented only a subset of the other users, and the search function did not work as expected.

Save Templates With a Blank Email Subject Line

For parity with the classic experience, users can save templates with a blank email Subject line.

Show More Added to Use a Template Dialog

When there are more than 10 folders on the Use a Template dialog box, "Show More" appears below the 10th folder, which the user can click to expand the list of templates.

Email Notifications Added to Admin

For parity with the classic experience, we've added two new user preference email notification options:

  • An envelope that I signed offline failed to synchronize
  • A signer's offline signature failed to synchronize for an envelope that I have sent

Support for XPS and MSG File Formats

For parity with the classic experience, the new experience supports users uploading XPS and MSG files.

Indicate Which Envelopes Have Been Purged

For parity with the classic experience, users will see more indicators that an envelope has been purged, or that a request to purge it has been made. When an envelope has been purged, the Inbox, envelope detail, document preview, and signing email will all state that the envelope has been or will be purged on a specific date. In addition, the option to forward a purged envelope will be removed from the More menu, and if the metadata has been purged, the option to download metadata will be removed from the download menu.

Automatic Email Reminder Events are Included in the Envelope History

When an automatic email reminder is sent to a recipient, the record of the event (date and time sent, recipient email address, and recipient ID) is included in the envelope history. This option is off by default; contact your account manager for more information.

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.


October Additions and Updates

Multiple SMS Phone Numbers in Bulk Send Lists

Users can now specify multiple SMS authentication phone numbers in bulk send lists. If multiple phone numbers are provided, the recipient selects which one to use to receive the SMS verification text. See this guide for more information.

Allow Senders to Create New or Change the Title of Authentication Methods

Users can create custom authentication methods (for example, phone + ID check), or change the name of an existing one (for example, change "ID Check $" to "ID Check,"), and those new or changed options appear as authentication options in the web app.

Download and Upload Templates in Bulk

For parity with the classic experience, when more than one template is selected, users can download all of them into a zip file. This facilitates simultaneously moving multiple templates created and verified in Demo to Production, or when switching from one account to another.

Updated Documentation about Downloading Form Data

When downloading form data, users encountered the undocumented Recipient Signed field, which holds the date and time the recipient clicked the Finish button. The documentation had been updated to define this field.

SSO Log in Policy Changes are Saved

When an organization admin edits the user login policy setting, that setting is now saved.

In the past, the policy change was not always saved.

Separate Last Name and First Name Fields

In the Adopt Your Signature dialog, signers who have set their language to Chinese simplified, Chinese traditional, Japanese, or Korean, are automatically provided with separate last name and first name fields instead of one full name field.

October Addendum

Bug Fixes

  •  After an Organization Admin changed the email address of a closed user, the change did not take effect (ADMIN-3424).
  • When adding a new user and assigning that user to a specific group, the group setting did not take effect (ADMIN-4085).
  • Users with the Delegated Admin role were unable to manage DocuSign Admins (ADMIN-3985).
  • Delegated Admin users with only user level permissions were incorrectly offered the option to provision an Admin level user, but when attempting to provision the admin user no error message appeared and no action was taken, leaving the user confused (ADMIN-3980).
  • Admins received an error when trying to update or edit brands in the new experience (ADMIN-3944).
  • When using the API to create a new user with a specified job title, the title was not provisioned (ADMIN-3893).
  • When an Organization Admin tried to change a user's email address, they received one of two error messages, either that the membership was closed or that there was an error saving the profile, and the changes were rejected (ADMIN-3727).
  • Organization Admins who managed accounts on two sites could not add a user from the account on one site to the account on the other site (ADMIN-3664).
  • When creating an organization, Organization Admins were not taken directly to the Org Admin dashboard (ADMIN-3307).

New and Updated Features

Following are new and updated features for Admin.

Include Account Number Column When Displaying Account Name in Organization

Organization Admin: In Organization Admin, whenever a page contains an Account Name column, a corresponding Account ID column will be displayed. The Account ID will also be updated to display the common ID instead of the current GUID.

Envelope ID Shown with Envelope Publish

For parity with the classic experience, when using Connect > Publish Envelopes, the Envelope ID is now displayed in the output.

Loading Indicator Shown when Searching

When an Organization Admin searches for a user, the Search button dims and includes a spinner to indicate that it is searching. If they enter and invalid email format, they receive an error. If there are no results, they see a message to that effect.

Admins Can provide an Address and Phone Number When Adding Users

An Admin or Delegated Admin can add work address and the phone number in the membership record to a user's membership profile when adding or editing a user.

Reactivate or Create New User on an Account

Admins can reactivate or add a new user to an account with an email address that belongs to a closed user. They have the option of selecting from a list of existing memberships to reactivate, or of creating a new account. If the membership is reactivated, the reactivated user will have access to any existing envelopes.

Reactivate or Create Closed Users with Organization Account Membership Notice

Organization Admin: If a user has a closed membership, we now indicate to the admin that there is an existing closed membership for that user on the account and ask whether they want to reactivate the membership or to create a new membership for that email address. This lets admins reuse email addresses, which is common practice in large organizations.

Display, Clear, or Copy a User's Federated ID

Organization Admin: Federated ID's will be listed on each organization user's page under Security for each Identity Provider for which they have a Federated ID and are a member of a reserved domain. Users without Federated IDs will be indicated by No Federated ID configured for this user. Organization Admins will be able to clear an ID, as well as copy the ID to the clipboard.

Organization Admins Can Update the Organization Profile

Organization Admin: Admins can update the organization name and description in the organization profile.

Reactivate a Closed User Membership When Active Member Exists

When an admin attempts to reactivate a user that is closed, but an active user with the same email address exists on that account, they receive a message saying that an active membership for that email address already exists. They can then open the active membership profile or cancel the reactivation.

Admins in a Group Can Access All Brands Shared with That Group

An Admin in a group has access to all brands shared with that group.

Enforce the Default Date and Time Format at the Account Level

Administrators can enforce a standard time zone and date and time format for all users, or allow users to choose their own settings in Regional Settings. For more information, see this help topic.

Updated Documentation

Documentation for creating and reactivating users has been updated here.

Connect HTTP Listener Sunset Reminder

Currently, the DocuSign Signature developer system (demo.docusign.net) 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.

Bug Fixes - New Experience and Core

The name-number is the internal DocuSign issue tracking number for the bug. Issue numbers that are in bold text are externally reported bugs or customer commitments.

The following bug fixes were deployed to the DocuSign Demo environment on November 20, 2017 as part of the DocuSign Winter 2018 release.

High Priority Bug Fixes

  • In some languages, the drop down menu next to a contact was not displayed (MAR-23685).

Medium Priority Bug Fixes

  • In the new experience, when editing formulas in a template containing many formulas, validation of the formula was taking an excessive amount of time (MAR-20824).
  • In the new experience, when a template with hundreds of formulas was used, it took an excessive amount of time to load (MAR-22602).
  • For parity with the classic experience, users can access an envelope's history from the Actions menu (MAR-22964).
  • Added a message that when deleting an In-Process envelope, the envelope is auto-matically voided and becomes inaccessible (MAR-32587).
  • In Internet Explorer, users experienced keyboard latency when attempting to edit their preferences (MAR-24120).
  • When using a screen reader, the Adopt Signature dialog box field labels and text were in colors that caused some text to be skipped and invisible text or "blank" to be read (SIGN-13543).

Low Priority Bug Fixes

  • Search results display size is static (formerly, the height changed with the number of items in the list) (MAR-23324).
  • When adding a Sending Brand to an envelope when correcting it, the brand was not saved with the corrected envelope (MAR-23383).
  • The Name and Date stamps for eHanko were the same size. Now the Name stamp is 9 MM and the Date stamp is 15 MM (SIGN-15368).

November Bug Fixes

High Priority Bug Fixes

  • Users were not able to change the language on the user interface by using the My Preferences > Regional Settings > Language setting (MAR-21928).
  • Users encountered mislabeled folders and were unable to access templates (MAR-23312/MAR-23313).
  • Users nearing a performance threshold received an error when trying to select templates (MAR-23317).
  • Users trying to log in to the New DocuSign Experience when it was set to Optional received an error (MAR-23813).

Medium Priority Bug Fixes

  • The chargeID was missing from the payment details returned by the REST API response (PYMT-2394).
  • ACH Validation pending status was not returned in the API response (Vdev and V2) (PYMT-2425).
  • Envelopes created from a template containing payment fields sent using Bulk Send, did not actually send (PYMT-2432).
  • Users were unable to search for contacts anywhere except when sending an envelope when they had more than 500 contacts (MAR-21171/TT-686).
  • Users with a single template/document match were prompted to select a template and were unable to use automatic template matching (MAR-21912).
  • When users without send permission clicked Load All on the Manage (formerly Docu-ments) tab, were presented with the Send Your First Document button, and after clicking it, received an error message (MAR-17833).
  • When users created an envelope with custom subject and body, and then applied a template, the template subject overrode the custom subject (the body was unchanged) (MAR-19460).
  • When the Recipient list was long, there was no scroll bar or other way to see the names toward the bottom of the list (MAR-20298).
  • Existing and newly-created contacts were not appearing in My Preferences > Contact in the new experience (MAR-20298).
  • Users without Bulk Send permission were erroneously allowed to use a template containing a bulk list, receiving an inscrutable error message when they attempted to send the envelope (MAR-20299).
  • When users attempted to print a document, the print dialog box did not appear. Instead, the download dialog box appeared (MAR-21043).
  • In the new experience, reports contained the header "Custom Field", which lead users to believe that custom fields would be in the report. The header was changed to "Envelope Custom Fields" and a tool tip was added to clarify that the data was the labels on the envelope (MAR-21494).
  • In the new experience, under Shared Folders, when users created a two layers of sub-folders (Shared Folders>SubFolder1>SubFolder2), and then moved the lowest-level folder up to the first subfolder level (Shared Folders>SubFolder1, SubFolder2), after log-ging out, the folder hierarchy reverted to the three-level hierarchy (MAR-21508).
  • When users attempted to print form data in the new experience, only one page printed regardless of how many pages of data was presented (MAR-21560).
  • Non-admin users with share permissions were unable to rename or move folders (MAR-21801/MAR-20733).
  • Drafts has been removed from search status options for custom folders because draft documents cannot be moved to custom folders (MAR-21930),
  • Characters in search terms that are commonly used in regular expressions interfered with search causing no results to appear (MAR-21946).
  • In the new experience, drop down fields with long items in the list of options were not scaling properly, truncating the items (MAR-21969).
  • When downloading an Envelope report for envelopes that had more than one Envelope Custom Field, only the first Envelope Custom Field appeared in the downloaded file, but all Envelope Custom Fields appeared in the console report (MAR-22000).
  • Shared templates that were deleted from My Templates were still appearing in the Shared Folder (MAR-22048).
  • Templates folders were created without user interaction (MAR-22054).
  • When cloning and immediately sending an envelope from the Sent folder, users were redirected to the Inbox where the sent envelope did not appear instead of staying in the Sent folder (MAR-22132).
  • When saving a custom report in the new experience where Specific Users was used to select only certain users for the report, the users were not listed and not selectable (MAR-22146).
  • Loading templates in Chrome and Internet Explore hung indefinitely (MAR-22186).
  • In Firefox, when users tried to use the Tab key on the keyboard to navigate through fields on the envelope, the focus changed to menu or browser options instead of navigating through the envelope fields (MAR-22398).
  • Users were receiving the error message "Login Unsuccessful. Sorry, an error occurred." after successfully changing their passwords and entering the new credentials correctly (MAR-22419).
  • Uploading the same bulk list on different machines succeeded on some, but not others (MAR-22598).
  • Form data from drop down fields was displaying the values in Options instead of the values in Values (MAR-22619).
  • When using DS EU Advanced with an access code, users had to click Close before the access code would be saved (MAR-22620).
  • Customers using the REST API to create envelopes with some recipients who needed custom email and language and others who didn't receive an error when attempting to correct an envelope after a recipient who did not have custom email and language signed the envelope (MAR-22716).
  • Users sending an envelope to themselves at the same time as a bulk list, could not use the Sign Now function (MAR-22766).
  • Merge field fixed widths in DocuSign for Salesforce were not honored when sending from DocuSign. Text bled off the edge of the page instead of staying within the specified fixed width (MAR-22769).
  • Users were unable to create a powerform from a template that contained a supplemental document (MAR-22875).
  • When using View As on the Manage page, when the list of users was long enough to require scrolling and the user used the scroll bar, the View As menu disappeared (MAR-22918).
  • Custom date ranges on custom reports were not being displayed (MAR-22052).
  • In Demo, when downloading a single completed document that had been uploaded as a non-PDF file, the downloaded document was a PDF, but the file extension was the whatever file had been uploaded (MAR-22997).
  • Users did not receive error messages when uploading unsupported file formats (dwg, dxf, and dgn) (MAR-22998).
  • In the new experience, users were unable to search by batch ID (MAR-23005).
  •  When only one authentication type was required, senders were receiving "Each recipient must have an authentication type specified" for every recipient instead of being allowed to proceed as expected (MAR-23121).
  • When downloading fields, the resulting CSV had headers for each field, but no data when the envelope contained only fields without values (Signature or Initial, for example) (MAR-23133).
  • Users were able to send an envelope with an invalid SMS number by selecting Edit Recipients, changing the SMS number to an invalid number, and then pressing ESC. The envelope sent without validating the SMS number (MAR-22187).
  • In the new experience, users were not able to access Sender IP Address in reports (MAR-23249).
  • When a custom message to recipients was added to an envelope before any document was added, after adding the document, the email message reverted to the default "Please DocuSign: FILE NAME" message (MAR-23251).
  • After correcting an envelope users received "Successfully sent." message instead of one indicating they successfully corrected an envelope (MAR-23262).
  • When selecting multiple documents for download and selecting "Combined PDF", the documents were downloaded as separate PDFs in a zip file instead of a single PDF in a zip file (MAR-23350).
  •  Users with switch to the new experience as optional, lost the ability to switch back to the new experience if they switched to the classic experience and logged out from there (MAR-23427).
  • In the new experience, when any field was locked to the template by sender permission Mandatory or Restrict Changes, or both users were unable to delete the recipient when sending the document (MAR-23571).
  • When users dragged field to a document, the fields disappeared and adding or modifying any other fields took a long time (MAR-23588).
  •  Filters were not being retained on template folders (MAR-23807).
  • Recipient phone authentication was not saved and a JavaScript error occurred (MAR-23827).

Low Priority Bug Fixes

  • Users did not receive any indication that a template that included a supplemental document was sent by clicking the template and choosing Use (MAR-22116).
  • Powerforms columns with double digits were wrapping (MAR-23159).
  • Users were unable to download multiple templates from the Share Templates or Shared With Me folder (MAR-23286).
  • Users were unable to upload some bulk recipient lists (MAR-23316).

October Bug Fixes

High Priority Bug Fixes

  • When users deleted documents from a template before sending, some of the documents reappeared in signing and on the completed envelope (MAR-22276).
  • In demo accounts, users who were on the new experience only were seeing the Switch to Classic options, and if they clicked it, they were returned to the new experience. (MAR-23144).
  • Recipients with allow to edit set and the sender of the envelope were stuck in a loop where the system said that the other was correcting a document (TT-647).
  • A user who was not a sender on an account, but had admin privileges and was added to the envelope as an editor was not able to correct the envelope.(API-7486).

Medium Priority Bug Fixes

  • After filtering a list of envelopes for in progress envelopes, when a new envelope was sent or an envelope in the list was corrected, the filter reverted to the default view instead of returning an updated in progress list (MAR-22009).
  • The Manage Applied Templates functionality was not properly handling adding and removing templates in an envelope (MAR-22148).
  • CFR-11: When sending a template-based envelope with a required signature/initial and an optional signature/initial after using Advanced Edit, users received a spurious error message (MAR-22877).
  • CFR-11: Sending to a non-DocuSign member worked when sending an envelope without using a template, but using a template to send and changing the non-DocuSign member recipient to a DocuSign member recipient resulted in the error: "Account Settings Indicate the recipients must be an active DocuSign user" (TT-598).
  • When users created radio groups with the same name on multiple documents, when a button was selected on one document, it was selected on all documents (MAR-22777).
  • When DS EU Advanced option was selected and an access code assigned, the access code was not saved (MAR-23088).
  • There was a limit of the first 500 contacts shown when users tried to add a recipient from their contacts when sending an envelope (MAR-20203).
  • When users set a document to be a supplemental document with specific view/accept settings and then tried to change those settings, the new settings were not honored (MAR-22399).
  • Envelopes with formulas were able to be sent when recipients were allowed to edit the envelope (MAR-22627).
  • The default country for Standards Based Signatures was not determined in the same way in all parts of the product (MAR-22562).
  • View Form Data has been move to the More menu on the envelope page from where you can download the data (MAR-23125).
  • When an Admin user who created and shared a template had their permissions reduced to Viewer, other Admin users with whom the template was shared could not add recipients or fields to the template because the Viewer permission was incorrectly applied to them also (TT-620).
  • When using autoplace fields for a recipient on a template, when template matching was applied, if any field's x-offset extended beyond the page boundary, the recipient was removed from the envelope with no indication that an error had occurred (TT-589).
  •  When radio buttons or radio button groups were deleted from an envelope, users randomly received the "Save Error: Some fields may be out of sync" error because the deletion was not being properly handled (TT-574).
  • Custom envelope field view/hide/required rules on templates were not applied consistently when using the template or applying the template to draft document (TT-546).
  • When replacing a document with a large number of fields, the new document was not added and the process timed out (TT-525).
  • The Document Volume Report and Dashboard graph were displaying different numbers of envelopes sent for the same time frame (API-6777).
  • The expiration date for an envelope was inconsistent between what was displayed on the Manage tab and the actual envelope (API-6803).
  • In the classic experience, when a user added herself as a signer to an envelope, she received an envelope not found error (SIGN-14070).
  • When a signing ceremony for embedded signers was initiated on iPads, the document appeared off the page, positioned towards the upper right hand corner (SIGN-14129).
  • Using a template with anchor tags that had a horizontal offset that placed the tag off the matching document caused the associated recipient to be removed from the envelope (TT-589).

Coming Soon

This following features and bug fixes will be available in the near future; any dates are estimates at this time and will be updated when the feature is released. Some of the features were listed in previous months' notes.

Updated Tab/Type Behavior

For all controls, when they are selected:

  • TAB moves to the next field and applies edits made to the field when moving to the next field.
  • CTRL+TAB switches the focus to the properties panel.

Download PDF and Certificate of Completion as Combined Document when Using Custody Transfer

When using custody transfer of envelopes from individual senders to a shared mailbox, the PDF and Certificate of Completion can be downloaded as one combined document, either from the individual's Inbox or from the Shared Sent folder.

Account Member Email Preferences to be Added to Admin

We are adding new section called Email Preferences to Admin so that an admin can manage default email notification settings for account members and API users.

API Will Return Whether a Signer Can View Envelope History

For parity with the classic experience, when a signer has an account, the API will return the status of the "Disable signers from viewing history" setting. When this setting is enabled, the new experience will not allow the user to view any envelope history.

Alert for Drops in Browser Traffic

Created an alert to capture sudden drops in traffic from a given major browser version (IE 11, Chrome 61, etc.) as well as a browser going into loops with API requests.

OCR-A Font on the Add Fields Page

For parity with the classic experience, we will be adding the OCR-A font to the add fields page in the new experience.

Warning When No Merge Fields Permission or No Salesforce Access

Warn a user when they upload a template with merge fields associated with Salesforce fields to an account without merge field permission or Salesforce access.

Apply All Matching Templates

When Apply Matching Templates is enabled, and when multiple documents with matching templates are selected, all matching templates will be applied.

Header and Footer Links in Sending Experience Update

For parity with the classic experience, when users customize the links in headers and footers, those links will render properly in the new experience.

Formulas Created in the Classic Experience

Formulas created in the classic experience will continue to work in the new experience when modified.

Template List Date Range Update

The Template list date range in Use Template or Apply Template dialogs will default to All.

Anchor Text Alignment in Word Documents

In the API, DocuSign for Salesforce anchor text applied in a Word document will be aligned to the bottom of the surrounding text string rather than to the center of the surrounding text string.

Shared with Me Folder Behavior Update

For parity with the classic experience, for Administrators, the Shared with Me folder will not show templates that are only shared with the Administrators group.

Error Message for Templates with the Same Name

Users will receive the error "A template with that name already exists in this account. Please provide a unique template name."when they try to save a new template or update an existing template with the same name as another template in the account.

Admin Setting to Prevent Senders from Adding Recipients

In the classic experience, admins could use the Sending Resource file to disable the Add Recipients button for use cases where senders were not allowed to add recipients to an envelope for security, privacy, or compliance reasons. There is no Sending Resource file in the new experience, so a new Admin user permission setting will let admins prevent senders from adding recipients. This setting only affects adding recipients, it does not prevent senders from deleting recipients.

November Coming Soon

Admins Can Set Default Email Notifications Settings

Currently, in the new admin experience, there are no default email notification settings that can be set for all account users. For parity with the classic experience, new experience admins will be able to set default email notification settings.

Ability to Define Header and Footer Links in Sending Emails

DocuSign admins will see a link in their sending brand to let them customize links in headers and footers. The set-up will be the same as is available in the signing brand, with the exception that there is only one sending brand.

API Will Only Return Shared Contacts When Set in Admin

The contacts API will only return shared contacts for a user when shared contacts is set in the DocuSign Admin.

Determine Whether Senders Can Specify Alternate Names

For parity with the classic experience, users will be able to determine whether senders can specify alternate names for signing.

Add and Edit IDR Zones

For parity with the classic experience, users will be able to add and edit Intelligent Document Recognition zones (IDR zones) to their templates by opening a template for editing, clicking the gear icon at the top of the documents list on the Add Fields view, and then selecting the Add IDR Zones menu option. After an IDR zone has been added, users will see an Edit IDR Zones link at the top of the documents list.

Recipients at the Same Signing Order Retain that Order

Recipients in the same signing order will retain that order when adding fields in the new experience.

Search for Templates Update

Users will be able to select what field to search for templates:

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

Select Multiple Envelopes for Download to CSV

Using the API, users will be able to select multiple envelopes and download all of them to a single CSV file instead of downloading each envelope individually.

Error Message for Templates with the Same Name

Users will receive an error message when they try to create or update a template with the same name as another template in the account.

Basic Authentication Support for Connect

Coming soon, the Connect notification service will be updated to support the Basic Authentication scheme with customer’s Connect servers (listeners).

When the feature is activated by a System Administrator for a Connect custom configuration (subscription), Connect will include the Authorization header in its requests to the customer’s web server.

The System Administrator uses the Connect configuration panel to enable Basic Authentication and to set the user name and password that will be sent.

The user name and password can be updated with the Edit command for the Connect custom configuration.

The Basic Authentication option is only available for custom Connect configurations. Individual Envelope Connect configurations created with the eventNotifications API option do not support Basic Authentication.

If enabled, the Basic Authentication header is included with the Connect notifications. Enabling the Connect Basic Authentication option does not ensure that the customer’s server is implementing access control.

Access control and Basic Authentication requirements are implemented by the customer’s web server, not by DocuSign Connect.

Important Update to Email Case Submission and Default Resource File

To improve responsiveness and routing accuracy, we are streamlining our Customer Support case submission process. After November 8th, 2017, we will retire the use of service@docusign.com and support@docusign.com, and ask customers to submit cases through the DocuSign Support Center.

All references to these emails will be removed from our default resource files and replaced with https://support.docusign.com. If you have customized your Branding Resources Files, we recommend that you update them prior to November 8, 2017 to ensure your envelope recipients have access to the correct support resources*.

Previous default value: DocuSign Customer Support: service@docusign.com or support@docusign.com

Proposed value: DocuSign Customer Support: https://support.docusign.com

*To provide your envelope recipients with a path to contact DocuSign Support, we recommend using verbiage such as: "For assistance, please visit the DocuSign Customer Support Center: https://support.docusign.com."

October Coming Soon

Hide The Use Template Option on the Home Page

We've added the ability to hide the Use Template option on the Home page (MAR-23067).

View As Option Persists During a Session

The View As option was not persistent in a session, meaning that if a user was viewing a shared folder and needed to access more than one item in the shared view, they were required to go through the View As step for each item.

Determine Whether Senders Can Specify Alternate Names

For parity with the classic experience, users will be able to determine whether senders can specify alternate names for signing.

View More on Template Folders

For parity with the classic experience, when a user has more than 10 template folders, users will see "View More" following the tenth, expanded folder.

Updated View As Experience

When viewing shared envelopes (formerly shared folders), users will be presented with a dialog box to let them choose or search for the person who has shared an envelope with them. In the past, when users had many envelopes shared with them, the View As feature presented only a subset of the other users, and the search function did not work as expected.

Add and Edit IDR Zones

For parity with the classic experience, users will be able to add and edit Intelligent Document Recognition zones (IDR zones) to their templates by opening a template for editing, clicking the gear icon at the top of the documents list on the Add Fields view, and then selecting the Add IDR Zones menu option. After an IDR zone has been added, users will see an Edit IDR Zones link at the top of the documents list.

Allow Users to Customize the Sending Experience

Customers will be able to modify colors in the sending experience. This brings the new experience closer to parity with the classic experience branding functionality.

NoteL if your account has branded colors in the classic experience, these colors will appear in the New DocuSign experience with no action on your part. If you want to revert the default experience, you can edit your brand preferences in Admin> Brands> Signing,

Apply All Matching Templates

When Apply Matching Templates is enabled, and when multiple documents with matching templates are selected, all matching templates will be applied.

Save Templates With a Blank Email Subject Line

For parity with the classic experience, users will be able to save templates with a blank email Subject line.

Recipients at the Same Signing Order Retain that Order

Recipients in the same signing order will retain that order when adding fields in the new experience.

XPS and MSG File Formats Allowed for Upload

For parity with the classic experience, XPS and MSG files will be permitted for upload in the new experience.

Documentation Update for Creating and Saving Templates

The documentation for creating and saving templates will be updated to reflect the minimum requirement to save a template as a draft.

Shared with Me Folder Behavior Update

For parity with the classic experience, for Administrators, the Shared with Me folder will not show templates that are only shared with the Administrators group.

Bug Fixes - Coming Soon

The name-number is the internal DocuSign issue tracking number for the bug. Issue numbers that are in bold text are externally reported bugs or customer commitments.

  • When users saved both a phone number and an SMS number, the API did not return both numbers (API-7664).
  • Users attempting to create and save a template received the error "The template is not locked." and they cannot save the template (MAR-18383).
  • When a user with a DocuSign account has been set to "Disable signers from viewing history", they are still able to see the history (MAR-10458).
  • For parity with the classic experience, when a signer fails authentication, the envelope will say "Authentication failed" instead of "Delivery failed" (MAR-19747).
  • Anchor tags are missing when more than one template is applied (MAR-21331).
  • Envelopes were put into an invalid state preventing recipients from signing (MAR-21724).
  • In the new experience, when users tried to upload multiple documents from a cloud service, some documents uploaded, but others did not. They received the error message Error: the resource may have been changed by another user or process while you were performing this operation. Please try again (MAR-21797)
  • When users added SMS authentication and included a complete phone number, they received error messages stating that the phone number was incomplete (MAR-22919).
  • In the new experience, users on Internet Explorer 11 experience extremely long load and search times after logging in (MAR-23359).
  • When “Enforce authentication requirements on sender when signing" is turned off in the new experience Admin, uses signing from the web app are still required to authenticate (MAR-23426).
  • Checkboxes and following text on templates created in the classic experience did not retain their position when the template was used in the new experience, requiring users to manually adjust their positions (MAR-23573).
  • Users with Manage Envelope permission are logged out instead of remaining in the web console after correcting an envelope opened from the email link (MAR-23660).
  • When replacing a template containing AutoPlace fields with a document with the same fields, the replacement document loses its AutoPlace fields (MAR-24045).
  • Users are encountering the error "Error when correcting an envelope - Recipient not in state that allows correction." when trying to change an email address for a recipient who has not yet signed (MAR-24184).
  • Users whose settings for EnableSequentialSigningAPI and EnableSequentialSigningUI were set to false were not able to use Sequential Signing when using templates (as expected) (TT-584).
  • The owner of a shared template cannot see it on the Template page (TT-724).
  • New users activated on an account are created with two Templates folders (TT-764).
  • If some radio buttons in a group are conditional, it's possible to complete signing with an empty required radio button group (TT-768).
  • Users are able to see templates not shared with them (TT-784).
  • When users upload a document containing Auto Place fields, the fields are duplicated when a template is applied (TT-797).
  • In the new experience, when a template containing autoplace fields is used in an API call that also includes autoplace fields, the API autoplace fields do not appear in the document (TT-814).
  • Search by envelope ID does not always return the envelope when using "View As" (TT-821).
  • The routing order for recipients assigned in a template is not retained when using that template (TT-859).
  • When language is not English, the "Last 24 Hours" search option on the Manage page is not translated to the language in use (all other options are translated) (MAR-22360),
  • When editing IDRs on a template, they do not always appear (MAR-23461).

November Coming Soon Bug Fixes

The name-number is the internal DocuSign issue tracking number for the bug. Issue numbers that are in bold text are externally reported bugs or customer commitments.

  • When using a custom authorization, users cannot save a phone number as well as an SMS number (API-7285).
  • Envelopes set to expire within 24 hours do not have an expiring soon warning and do not appear in the list of envelopes tat are expiring soon (API-7427).
  • When continuing a draft envelope or correcting an envelope, attempting to clear a recipient's contact information fails (DCMT-960)
  • Users attempting to create and save a template received the error "The template is not locked." and they cannot save the template (MAR-18383).
  • Aligned text fields size changes between preview/creation and when envelope is sent (MAR-21488).
  • Envelopes were put into an invalid state preventing recipients from signing (MAR-21724).
  • In the new experience, when users tried to upload multiple documents from a cloud service, some documents uploaded, but others did not. They received the error message Error: the resource may have been changed by another user or process while you were performing this operation. Please try again (MAR-21797).
  • Users are unable to view the envelopes of other users (using View As) (MAR-22234).
  • When uses switch between a classic experience account that has used the new experience set to optional and an account that has used the new experience set to no, when they switch to the original account they cannot switch to the classic experience (MAR-22520).
  • In the new experience, when a template with hundreds of formulas was used, it took an excessive amount of time to load (MAR-22602).
  • When users added SMS authentication and included a complete phone number, they received error messages stating that the phone number was incomplete (MAR-22919).
  • When a template is created when "Don't allow senders to edit the subject, email, or private messages." has been selected in Advanced Options and the subject is left blank or erased, users were able to save the template without any warning that the subject was empty and that the template was now unusable (MAR-23342).
  • In the new experience, users on Internet Explorer 11 experience extremely long load and search times after logging in (MAR-23359).
  • Checkboxes and following text on templates created in the classic experience did not retain their position when the template was used in the new experience, requiring users to manually adjust their positions (MAR-23573).
  • Envelopes with the same in-person host for two or more signers received one of two errors: "An In Person signer host is not a valid DocuSign User." or "Invalid host. The host must be a DocuSign account holder." (MAR-23583).
  • In the new experience, users are unable to filter reports on closed users (MAR-23603).
  • Users with Manage Envelope permission are logged out instead of remaining in the web console after correcting an envelope opened from the email link (MAR-23660).
  • Users can search envelopes and templates by sender name + email, or recipient name + email. Searching by sender only works if custody of the envelope had not been transferred (TT-260).
  • The owner of a shared template cannot see it on the Template page (TT-724).
  • New users activated on an account are created with two Templates folders (TT-764).
  • Users are able to see templates not shared with them (TT-784).
  • After applying a template, if the document is replaced, the fields lose formatting and the text is distorted (TT-785).
  • When users upload a document containing Auto Place fields, the fields are duplicated when a template is applied (TT-797).
  • When a Needs to Sign recipient is changed to Sign with Notary, the user receives the error "Account lacks sufficient permissions, user cannot send envelopes with a notary requirement" and cannot proceed to the place fields page (TT-817).
  • Templates using autoplace text with custom field validation lost the custom validation when the templates were used (TT-675).

October Coming Soon Bug Fixes

  • When selecting multiple documents for download and selecting "Combined PDF", the documents were downloaded as separate PDFs in a zip file instead of a single PDF in a zip file (MAR-23350).
  • When a custom message to recipients was added to an envelope before any document was added, after adding the document, the email message reverted to the default "Please DocuSign: FILE NAME" message (MAR-23251).
  • When users elected to show Sender IP Address in the Envelope Report, the field was always blank (MAR-23249).
  • When templates with bulk lists were shared with users who did not have permission to send to bulk list, the users were told the envelopes were sent, but they were not actually sent (MAR-20299).
  • When only one authentication type was required, senders were receiving "Each recipient must have an authentication type specified" for every recipient instead of being allowed to proceed as expected (MAR-23121).
  • In the new experience, when editing formulas in a template with many formulas, validation of the formula was taking an excessive amount of time (MAR-20824).
  • In the new experience, under Shared Folders, when users created a two layers of sub-folders (Shared Folders>SubFolder1>SubFolder2), and then moved the lowest-level folder up to the first subfolder level (Shared Folders>SubFolder1, SubFolder2), after logging out, the folder hierarchy reverted to the three-level hierarchy (MAR-21508).
  • In the new experience, simultaneous API calls were causing signed envelopes to fail with a Not all Tags Signed error (MAR-21724),
  • In the new experience, when users tried to upload multiple documents from a cloud service, some documents uploaded, but others did not. They received the error message

Error: the resource may have been change by another user or process while you were performing this operation. Please try again (MAR-21797).

  • When creating a custom report with a custom date range, after saving the report, when the report was opened the custom date range was blank (MAR-22952).
  • In the new experience, drop down fields with long items in the list of options were not scaling properly, truncating the items (MAR-21969).
  • When more than one custom field was included in a report, the report displayed correctly in the web app, but when the report was downloaded to a CSV file, only the first custom field was included in the download (MAR-22000).
  • When using the SOAP API call CreateEnvelopeFromTemplates with a template that had phone authentication enabled, but did not include a phone number, the envelope sent without failing phone authentication validation (MAR-22249).
  • In Firefox, when users tried to use the Tab key on the keyboard to navigate through fields on the envelope, the focus changed to menu or browser options instead of navigating through the envelope fields (MAR-22398).
  • When users added SMS authentication and included a complete phone number, they received error messages stating that the phone number was incomplete (MAR-22919).l    In the new experience, when a template with hundreds of formulas was used, it took an excessive amount of time to load (MAR-22602).
  • When using View As on the Manage page, when the list of users was long enough to require scrolling and the user used the scroll bar, the View As menu disappeared (MAR-22918).
  • For admins, when filtering templates using Shared with Me, templates shared only with the admin group were included in the list (MAR-22916).
  • When using a DocuSign for Salesforce merge field with a fixed width, the field width was not honored and the text bled beyond the edge of the page when the field was placed near the right edge of the document (MAR-22769).
  • In the classic experience, when an admin selected Use the New DocuSign Experience to require users to use the new experience, "Yes" was not an option in the menu (MAR-22753).
  • Correcting an envelope that included Specify Recipients or Update Recipients did not retain changes made to recipients data (MAR-22744).
  • When using DS EU Advanced with an access code, users had to click Close before the access code would be saved (MAR-22620).
  • In the new experience, a template with hundreds of formulas was taking significantly longer to load than when using the same template in the classic experience (MAR-22602).
  • Users were not able to use the Tab key to move through fields on a document when using FireFox (MAR-22398).
  • When using Standards Based Signature, and correcting the SMS authentication phone number on an envelope, the change is not saved (MAR-22384).
  • When using the SOAP API CreateEnvelopeFromTemplates call, users were able to create templates with phone authentication required, but without specifying a phone number (MAR-22249).
  • Viewing templates by clicking Templates or searching by date produced an indefinite loading state (MAR-22186).
  • Templates folders were created without user interaction (MAR-22054).
  • When downloading an Envelope report for envelopes that had more than one Envelope Custom Field, only the first Envelope Custom Field appeared in the downloaded file, but all Envelope Custom Fields appeared in the console report (MAR-22000).
  • In Signing, envelopes with drop down menus that contained long strings truncated the strings (MAR-21969).
  • When users tried to upload multiple documents from a cloud provider, not all the documents would upload, and they received the message "Error: the resource may have been change by another user or process while you were performing this operation. Please try again" (MAR-21797)
  • In the new experience, users were receiving the message "NOT ALL TAGS ARE SIGNED" when, in fact, all fields had been completed by the recipient (MAR-21724).
  • Users were unable to search for contacts anywhere except when sending and envelope when they had more than 500 contacts (MAR-21171).
  • Clicking Print on a non-draft envelope resulted in the download dialog instead of the print dialog (MAR-21043).
  • Users were unable to see newly added contacts in Contacts under My Preferences when they had more than 500 contacts. Related to MAR-21171. (MAR-20298).
  • When attempting to save a template, users received the error "The template is not locked." and all changes were lost (MAR-18383).
  • Users were unable to load envelopes for a powerform (TT-714).
  • When the Sender role was applied to a document in different routing orders, and different templates containing that role were applied, the Sender role was duplicated instead of being consolidated. This occurred because Sender is based on the person creating the envelope and is auto-populated with that person's name and email when the first template was applied; when the next template was applied, the Sender role on that template did not include the auto-populated data and so did not match the first template's Sender role and was duplicated. Changing the Sender role to Sender1 solves this problem (TT-712).
  • When using a custom text field with custom validation, the text field is applied when the template is used, but the custom validation is ignored (TT-675).
  • In Sending view, templates created in the classic experience and used in the new experience show misalignment of checkboxes, and data field wrap (TT-590)
  • Users whose settings for EnableSequentialSigningAPI and EnableSequentialSigningUI were set to false were not able to use Sequential Signing when using templates (as expected) (TT-584).
  • Text boxes placed on a template changed position and size after saving and reopening the template (TT-540).
  • Users can search envelopes and templates by sender name + email, or recipient name + email. Searching by sender only works if custody of the envelope had not been transferred (TT-260).
  • IDR does not work on dimensionally large documents like engineering drawings (TT-260).
  • When uses modified and then saved a template, the Last Modified column on the Templates page listed the correct date, but the time was in the future (TT-581).
  • When users uploaded multiple templates all of which had the same role names and signing order, and where the role name was blank on some templates, but contained a signing group in others, the roles were duplicated in the envelope (TT-628).
  • Using the REST API to send an envelope based on a template with pre-filled values does not show those values in the envelope seen by the recipient (TT-738).

October Addendum

Bug Fixes

  • An error message will be displayed when Admins attempt to add an email address that is part of a reserved domain that does not permit account memberships outside of the Organization (ADMIN-4044).

New Features

Bulk Add Updates

  • When using Bulk Add, members with closed memberships will be skipped and not reactivated.
  • When using Bulk Add, admins will be able to add optional addresses and phone numbers.

  • Delegated Admins will be able to use Bulk Add to add users.

  • Bulk Add will use First Name and Last Name instead of Full Name when adding users.

Access Bulk Actions

Delegated Admins will be able to access bulk actions in Admin.

Deprecated Admin Role

The delegated Groups admin role will be added to the Users and Groups role.

Remove Closed User from Signing Groups

For parity with the classic experience, when an admin closes a user, and that user is in one or more of the account's Signing Groups, a check box will appear as part of the confirmation dialog to ask whether the admin wants to remove this user from all Signing Groups.
 

« Back to Releases

Trustpilot