DocuSign August 2019 Update
Released on July 22nd, 2019
New and Updated Features
Organization Admins Can Bulk Update Domain User Email Addresses
Organization admins can now bulk update domain user email addresses using bulk actions. This will save org admins time and effort by replacing manual, repetitive actions.
- Admins will use the existing bulk users update workflow to bulk update user email addresses.
- The sample CSV has been updated to include an 'UpdatedUserEmail' column which can be used to modify existing domain user email addresses.
- Bulk Update User Email can only be used on users who currently have an email address that uses the organization’s claimed domain.
- The updated email address must use the organization’s claimed domain.
- Availability: Organization Management or Enterprise Pro - Requires Bulk Import Users Entitlement
Admins can now view and copy their User ID from the API and Integrations page.
For more information on new features and enhancements, see 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.
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. The DocuSign products will be refreshing 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.
Added Language and Region tab under My Profile
DocuSign has moved the setting from My preferences into My Profile and created Language and Region tab in My Profile.
This allows users to set sending language and signing language separately. For example, if your preferred language is Vietnamese and the user speaks French as a second language, users can choose Vietnamese for signing (but since Vietnamese is not supported in Sending language) users can choose French instead of English. English was the default fall back language prior to this new enhancement. (GLOB-1747)
Support CSV with Semicolon for Bulk Sending
This enhancement is related to the usage of MS Excel with many European locales which create CSVs using semicolon delimitation instead of a comma. As a result, it impacts the European customer for any of the import/export capabilities which are using the CSV file format.
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 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 tests and documents the Part 11 features used by DocuSign's 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 DocuSign's customers to search and refer back to past reports using the DocuSign console.
For more information, please see the Support page https://support.docusign.com/en/guides/ndse-admin-guide-validator or contact your Account Manager.
Enhancement: Formulas should be able to process numbers with commas
DocuSign now allows text fields with number validation to have the thousands be separated with commas (or periods in the case of the comma decimal separator).(SIGN-22261)
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
For more information, please visit the DocuSign blog at https://www.docusign.com/blog/dsdev-docusign-esignature-api-v21-api-unveiled/.
- Issues with localization on Admin Home have been resolved.
- The direct link to the Billing and Usage Admin page has been fixed.
For more information see the Admin Release Notes at https://support.docusign.com/en/articles/Admin-Release-Notes.
- transformPdfFields was not working when used on documents inside an inlineTemplate. This issue has been rectified and transformPdfFields is now working as expected. (TT-2487).
Users can now blank out initial text tab values from server templates used in CreateEnvelopeFromTemplatesAndForms API calls, using a special keyword string, “DOCUSIGN_EMPTY” (case sensitive). Users can now set the corresponding tab value to “DOCUSIGN_EMPTY” in the inline template, which gives the collapsed tab the value “” in the final result. This functionality is currently only supported for text tabs. (TT-2082)
21 CFR Part 11
The"21 CFR Part 11 Signature Block" date/time format and time zone now matches that of "Date Signed" field.
- The date/time format of both will be governed by the Signing Settings in the Sender's admin console. If "None" is selected for time format, the default format applied is HH:MM:SS AM/PM TIMEZONE.
- If the Signer has a DocuSign account, the time zone of both will be governed by the Signer's time zone selected under "My Preferences". Note: By default, all signer accounts are set to PST time zone.
- Senders can decide to not allow users/signers to set their own time zone under "Regional Settings" in Admin console. If this is the case, the time zone for both will be the Sender's time zone specified in the same section. (GLOB-1006)
IE 8, IE 9, and IE 10 browsers will be deprecated for Customer Prod accounts in July. IE 11 will be the minimum version of IE browser that will be supported going forward.
Sending and Templates - Coming Soon
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 - Coming Soon
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 - Coming Soon
Docusign has begun rolling out the switch to enable responsive signing to production in July.
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 will be able 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, DocuSign wants their customers to be in control of this feature in their accounts.
Responsive Signing Best Practices
This feature converts agreement content to HTML; 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 the guide on optimizing your content for Responsive Signing https://support.docusign.com/knowledgemarket/article/Best-Practices-for-Responsive-Signing-Application-and-Design
Concerns or Feedback
DocuSign plans on rolling out the switch to enable responsive signing in July. Account Managers and Customers can report issues directly through DocuSign support. For more information using the feature, read the public support page at https://support.docusign.com/en/guides/ndse-user-guide-responsive-signing. (SIGN-22570)
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 8, IE 9, and IE 10 browsers will be deprecated for Customer Prod accounts in the beginning of July. IE 11 will be the minimum version of IE browser that will be 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.