Release Notes

DocuSign July 2019 Update

Released on June 28th, 2019

New and Updated Features

Admin

Admin Home and Admin Notifications

New Admin Notification Type: Core Releases

Admins are now notified of Core Releases through Admin Notifications on the new Admin Home page. This will help admins stay up to date on the newest DocuSign features and bug fixes, and will provide a link to the latest release notes.

Organization Admins Cannot Grant Themselves Account Admin Privileges

Organization admins can no longer grant themselves administrative permissions on accounts for which they were not already an administrator. They must instead be granted admin capabilities by an existing admin on the account.

Remove DocuSign Classic Permission Sets from the Everyone Group

Admins can now remove permission sets from the Everyone group. Assigning permission sets to groups was available in the Classic DocuSign Experience, but not supported in this version of Admin. Once permission sets are removed from the Everyone Group, admins can assign user permission sets individually.

Default Font Settings

Admins can now set a default font for the account, including Font, Size, and Color for the account (not Bold, Italic or Underlined). The setting is located in Sending Settings at the top of the Fields and Properties. For more information view the Admin Release Notes at https://support.docusign.com/en/articles/Admin-Release-Notes.

Reminder: Organization Administration API is available

Reminder: The Organization Admin API was included in the May release. Use the Organization Administration API to easily manage all your DocuSign accounts and users with a REST API. The Organization Administration API enables you to automate user management with your existing systems while ensuring governance and compliance. You must have Organization Administration enabled on your enterprise account to use this API in production, but it is available in the Sandbox (demo) environment. For more information, visit https://developers.docusign.com/orgadmin-api.

Support for Single Sign-On v1 is Ending

DocuSign is deprecating support for legacy Single Sign-On (SSO) v1 platform. Customers still using SSO v1 are encouraged to upgrade to the improved SSO v2 platform with self-service administration. All legacy SSO v1 configurations will be permanently removed by 7/31/2019. Please contact your Account Manager to help with the migration.

API

Error Handling

DocuSign has added new error handling in the REST API when creating fields that prevent invalid Regular Expressions (RegEx) from being saved when sending an envelope. This enhancement will be ramped up over the next 30 days to customers globally.

Sending and Templates

New DocuSign Logo

This product release includes the new DocuSign logo, which is part of the brand evolution. DocuSign will be refreshing their products throughout the year to continually deliver a best-in-class user experience. Currently, it will be released for Signing, Sending, Email, Mobile Apps, Admin, and Account Server.

21 CFR Part 11

DocuSign’s Validator for Life Sciences

Note: Updated verbiage

Accompanying the 21 CFR Part 11 Module is DocuSign’s Validator for Life Sciences, a new add-on available for Part 11 users. DocuSign’s Validator for Life Sciences supports careful testing of the DocuSign platform and provides corresponding documentation to demonstrate that the solution performs the necessary tasks to adhere to Part 11 regulations. As part of the software development lifecycle, DocuSign performs rigorous testing of the functionality prior to releases. For regulated use cases, DocuSign test and document the Part 11 features used by customers to support compliance. When the Validator for Life Sciences is purchased and enabled, DocuSign provides reports to customers that include high fidelity screenshots of each test, details of the specific provisions tested, and the final test results. The report will be sent via a DocuSign envelope, allowing the customers to search and refer back to past reports using the DocuSign console.

For more information, please see DocuSign's Support page https://support.docusign.com/en/guides/ndse-admin-guide-validator or contact your Account Manager.

Responsive Signing

The Responsive Signing will be available for all Customer Demo accounts as of June 20th! DocuSign plans to begin rolling out the switch to enable Responsive Signing to Production accounts on July 8, ending in early August. Please refer to Responsive Signing rollout plan for a detailed schedule.

Benefits of Responsive Signing

Responsive signing will improve usability and performance for mobile signers. Responsive Signing automatically converts documents to HTML and allows you to preview the conversion across device types prior to sending. Signers on small screens will see the responsive HTML and can toggle to view the original document. This functionality helps signers get the most readable document presentation possible without pinching and zooming.

Enabling Responsive Signing

Customers who want to use Responsive SIgning need to enable it in DocuSign Admin. Simply login to DocuSign, click Go to Admin, click Signing Settings and check to Allow recipients to view mobile-friendly documents with responsive signing. The next envelope sent will be enabled for Responsive Signing by default. To control whether an envelope is enabled for Responsive Signing, a sender may toggle Recipients can view documents more easily on mobile devices with responsive signing in an envelope’s Advanced Options;

This feature is disabled by default as it may change what signers see, and DocuSign wants customers to be in control of this feature in their accounts.

Responsive Signing Best Practices

This feature converts agreement content to HTML, so some documents may be better-suited to conversion than others. For example, documents with regularly shaped tables and large blocks of text (e.g. common contracts) convert better than documents that have irregular or wide tables (e.g. tax forms). DocuSign recommends senders use Recipient Preview to check content before sending.

If you encounter any issues with your content or if you want to improve your content for mobile signers, read our guide on optimizing your content for Responsive Signing.

Concerns or Feedback

This switch will be available to customer’s account between 7/8 and early August. Account Managers and Customers can report issues directly through DocuSign support. For more information using the feature, read DocuSign's public support page. (SIGN-22570)

API v2.1

DocuSign has been working on an iteration of the API for the first party apps including the web app uses. This iteration is the new eSignature API v2.1. This is an incremental improvement on its predecessor. Users will find much familiarity. The areas of improvement include:

  • Improved usability
  • Access to new features such as Bulk Actions and Payments
  • Handling large workloads

Fore more information, please visit the DocuSign blog at https://www.docusign.com/blog/dsdev-docusign-esignature-api-v21-api-unveiled/.

Bug Fixes

Admin

  • Visual bug identified where Part 11 module shield and "view-only" was not reflected in the Signing Settings below within the Administration console. This fix addresses the visual markers on these settings. The fix will be rolled out over the next several weeks for relevant accounts. (ADMIN-6357) Signing Settings in Administration Console allow: o Recipients to sign on paper
    • Senders to override sign on paper
    • Senders to override change signing responsibility

API

  • DocuSign has added new error handling in the REST API on "draft" envelopes which prevent invalid formulas on form fields from being sent. This addresses the scenario where a recipient may be presented with an "invalid formula" error in the signing ceremony and not know what to do. This fix will be ramped up over the next 30 days to customers globally. (TT-1752)
  • Users can now add and edit IDR zones even when conditional logic is set on the document. (MAR-29497)

Sending and Templates

  • Users can now blank out initial text tab values from server templates used in CreateEn-velopeFromTemplatesAndForms API calls using a special keyword string, “DOCUSIGN_ EMPTY” (case sensitive). To do this, they set the corresponding tab value to “DOCUSIGN_EMPTY” in the inline template, which will give the collapsed tab the value “” in the final result. Please note that this functionality is only supported for text tabs at this time.(TT-2082)
  • AutoPlace now recognizes text and recognizes words in files up to multiple times (TT-2369)
  • Templates created via "Save as Template" from a completed envelope with an In-Person Signer contained an entry in the "InPersonEmail" field. This field could not be deleted from within the Template directly and caused future envelopes created from this template to CC the email listed as "InPersonEmail" within the Template data. This issue had been rectified. (TT-2237)
  • Admins were unable to view user templates if created as a copy. Admins can now view templates if they are created as a copy.(TT-1876)

Signing

DocuSign now supports Signature Tab Resize for simple DS Electronic signature recipients on accounts enabled with SBS.(SIGN-21476)

Coming Soon

Admin 

IE Deprecations

IE 8, IE 9, and IE 10 browsers were deprecated on Demo May 31, 2019 and will be deprecated by the end of June in Production. IE 11 will be the minimum version of IE browser that will be supported going forward.

New Admin Notification Type: Connect Failures

Admins will be notified of Connect failures in real-time through Admin Notifications on the Admin Home page.

Sending and Templates 

Template List Performance Improvements for IE

DocuSign will be updating the template list to be in line with the envelope list. Updates will be made to the menu for the folder items and structure.

Reporting 

Download Email Improvements

Users will be taken to a download section upon clicking the Download link from an email. From the link, users are immediately taken to the download section inside Reporting. Users can see up to 90 days worth of scheduled reports. Once the View button is clicked, the CSV file downloads.

Signing

DocuSign eWitness

DocuSign eWitness allows organizations to enable signers to identify up to two witnesses to sign an agreement in a legal and confidential manner. eWitness captures the witness information in the Certificate of Completion to support any legal disputes. This means many of the typically paper-based deeds can be digitized in the future, saving organization significant time and money. This feature is available for Enterprise Pro customers. If you are not an Enterprise Pro customer, please ask your Account Manager to enable this feature.

IE Deprecations

IE 8, IE 9, and IE 10 browsers were deprecated on Demo May 31, 2019 and will be deprecated by the end of June in Production. IE 11 will be the minimum version of IE browser supported going forward.

IMPORTANT - New DocuSign Logo

DocuSign has a new logo rolling out across the Product Development teams. Currently, it is released for Signing, Sending, Email, Mobile Apps, Admin, and Account Server.

« Back to Releases

DocuSign starting from $10 per month

Trustpilot