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
You can now configure data feeds using Organization Admin. This will allow to you quickly set up your integration key. Once added and configured by your development team, your organization will start retrieving data from all of your accounts. This data can be stored in your data warehouse and used as needed.
Availability: Organization Management or Enterprise Pro; Requires the AllowDataFeed Organization Entitlement
Admins can enable and disable conditional routing from the Sending Settings page. Conditional routing lets you route an envelope to different people based on envelope data. This eliminates the need to manually correct the envelope midway or to use separate templates with slight variations in routing.
Availability: Enterprise Pro or the Advanced Workflow Add-on
Organization admins can now invite external domain accounts to link with the organization via email. An external domain account is an account that is not linked to the organization and has at least one member with an email address on the organization's claimed domain.
Availability: Organization Management or Enterprise Pro; Requires the AllowUserListExport Organization Entitlement
For more information on new features and enhancements, see the Admin Release Notes at https://support.docusign.com/en/articles/Admin-Release-Notes.
IE 8, IE 9, and IE 10 browsers have been deprecated for Customer Prod accounts. IE 11 is the minimum version of IE browser that is supported.
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.
DocuSign has deprecated support for legacy Single Sign-On (SSO) v1 platform. All legacy SSO v1 configurations were permanently removed. Please contact your Account Manager if you need additional help or have questions about the migration.
Comments allows senders and signers to collaborate in real-time by asking and answering questions within an agreement. With Group Comments, customers will now be able to privately communicate to a subset of envelope recipients. (CONV-2390)
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 to customers globally.
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 DocuSign;s platform and provides corresponding documentation to demonstrate our solution performs the necessary tasks to adhere to Part 11 regulations. As part of our software development lifecycle, DocuSign performs rigorous testing of our functionality prior to releases. For regulated use cases, DocuSign tests and document the Part 11 features used by the 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 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.
With this enhancement the following updates have been made:
Require Upload Signature Specimen to Address 'remote Signature Card' for Finserv Customers
Major financial institutions still require a drawn signature specimen on the signature card document when opening an account. For consumer/in-branch scenarios, this is achieved through a bank owned tablet and embedded signing. This enhancement addresses remote signing scenarios, such as for institutional account opening (primary focus here), and
consumer remote account opening, where the signers are using their own devices. (SIGN-22313)
DocuSign has added a Tooltip to the Radio Buttons in Tagger to be included as the primary tool tip instead of the Group Label. In many cases the name may be an internal name that customers do not want disclosed. This tooltip is shown in signing to signers. (SIGN-17333)
This communication is regarding a change to the url returned by the Create Recipient View API endpoint:
What will change? Customers can expect to see the length of the URL to be longer. Customers can expect to be redirected through a different subdomain depending on region of the account sending the envelope. Please verify your domain whitelist per the following documentation: https://www.docusign.com/trust/security/whitelists
What will not change? DocuSign designed this change so that your existing functionality should not change.
Why are these changes made? These changes are part of an effort to standardize and further secure links that redirect into Signing Ceremony. DocuSign is working to centralize the system used for authentication across all its products. These new links provide improved security compared to the current system. These changes will provide the ability to expire, revoke, or modify an existing link without changing it. They also make secret links harder to brute force or to guess. They provide improved auditing on redemption and better ability to enforce authentication policies such as two-step verification. Redemption refers to what happens when the link is used. A token is created via the Create Recipient View Link API request, and then used/redeemed when the link is visited in the browser.
These changes began rolling out the week of Aug 26th.
Demo environment - DocuSign has slowly rolled out this feature in Demo over a few weeks to assess any potential issues with customer integrations. We will send out additional communications about when you can expect a rollout to Production environments.
Prod environment - NDSE initiated signing sessions will start using managed tokens. There are many ways to start signing: Email, API, Web Application, and Mobile Apps (IOS, Android, Windows). When starting from the Web Application, the Signing Links that take you from NDSE to Signing the envelope also use these new, longer format for links. This should not affect any developer integration using the API.
For questions, concerns and feedback, please contact Managed Token Rollout at MTRollOut@docusign.com
DocuSign has rolled out the switch to enable responsive signing to production.
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.
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 customers to be in control of this feature in their accounts.
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
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)
What will change? Customers can expect to see the length of the URL to be longer. Customers can expect to be redirected through a different subdomain depending on region of the account sending the envelope.
Please verify your domain whitelist per the following documentation:
What will not change? DocuSign has designed this change such that your existing functionality should not change.
Why is DocuSign making this change? These changes are part of an effort to standardize and further secure links that redirect into Signing Ceremony. DocuSign is working to centralize the system used for authentication across all its products These new links provide improved security compared to the current system including:
DocuSign has released 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:
Fore more information, please visit the DocuSign blog at https://www.docusign.com/blog/dsdev-docusign-esignature-api-v21-api-unveiled/.
Fixed a bug that caused some admins with Users and Groups delegated permissions to lose access to the Permission Sets page in Admin.
For more information see the Admin Release Notes at https://support.docusign.com/en/articles/Admin-Release-Notes.
The"21 CFR Part 11 Signature Block" date/time format and time zone now matches that of "Date Signed" field.
1. 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.
2. 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.
3. 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)
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.
Favorite Templates: Senders may now tap the star button to mark a template as a favorite. Head to the favorites tab to access all of your important templates in one place.. (PORTFOLIO-2723)
transformPdfFields was not working when used on documents inside an inlineTemplate. This issue will be rectified and transformPdfFields will work as expected. (TT-2230)
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.
With this release we will be introducing a feature to block automated email link checkers, such as ProofPoint, from accessing the content of the envelope. If an email link is accessed within a very short time period from different devices (non mobile) they will be presented with a page asking them to continue to the signing session. The effect of this feature on real signers would be extremely low and they should very rarely be presented with this page. (SIGN-23231)
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.
Near the end of September and on into October, DocuSign's partner LexisNexis (which powers the knowledge-based authentication) is going to be doing some required maintenance. LexisNexis confirmed there should be no discernible issues or changes for your users and members. DocuSign will be monitoring our systems for any anomalies, and should you see any issues, please contact support.
Recipients external to your organization that do not have a DocuSign account will now be able to activate their DocuSign account and sign their envelope all at once through one email. With this new feature, as an unaccounted recipient, you no longer have to search for a separate activation email in your Inbox before signing your envelope. DocuSign will automatically detect you are not an accounted recipient and prompt you to activate your account. Once finished, DocuSign will redirect you to the envelope for signing. This provides a faster and seamless signing experience while adhering to the Part 11 credentialing provisions.
This feature has been rolled out to a few select customers and is expected to roll out broadly over the next few months for relevant accounts, starting in Demo and proceeding to Production environments.
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.
DocuSign is launching a refreshed header across the applications (eSign, CLM, and Rooms) which provides a consistent look and feel with the updated DocuSign branding across the application, as well as a common way to navigate between applications.