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

Webinar: Advanced Calendar Solution for Sugar Register

Webinar: How to Sync External Data with Sugar Register

DocuSign February 2018 Update

Released on February 2nd, 2018

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

Fax Attachments Disabled in Branding

By default, fax attachments are disabled in branding profiles, but can be enabled if needed by customers.

Company Column Added to Address Book

For parity with the Classic experience, the Address Book now includes Company in addition to Name and Email columns.

Updated Connect Failure List Features

We have enhanced the Admin tool to add Delete All, Republish All, and Refresh actions to the Connect Failures log page.

Republish requests are asynchronous, they occur in the background. After requesting that failed messages be republished, use the Refresh action to update the screen with the current status.

Add Radio Buttons Change

When adding radio buttons, the number of buttons added has been changed from five to two.

Identify Pages Requiring Notary Recipients to Act

To alert Notary recipients that they must take some action on specific pages in a document, senders can place a Notarize page field on pages where a Notary must take action. 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

Org Admin - Fixed Issue with SSO V1

Previously when a customer enabled Organization Admin, it would not allow a user to log into Account Admin to manage an account. We fixed that issue so that a user can continue to use Account Admin with SSO V1 while they’re in the process of migrating to SSO V2.

File Types No Longer Supported

DocuSign no longer supports the following file types:
 

asl dxf pct vss
cdr emf pcx vst
cgm eml pic vst
dcx emz pub vmf
dgn eps rgb wpg
dps ico sam wps
dpt lwp svg wpt
drw odp svgz xlt
dwg dxf tga  
asl emf vsd  

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

Deprecated Features

The following sections describe features that are no longer supported. Unless otherwise indicated, the functionality will no longer be available after June 30, 2018.

Sending Branding Resource Customizations

DocuSign recently released a rich user experience for customizing colors in the sending experience, as well as the ability to restrict commonly hidden user actions with new permission set options (for example, Disable document upload and Hide Other Actions menu). Moving forward, we will continue to support customizations or restrictions to the user experience in this manner – through a rich user experience with native permission checks. Changes to the sending branding XML files will not be respected in the New DocuSign experience.

Sending Branding Preview in Preferences

Previewing the sending branding will not be implemented in the New DocuSign Experience in the near term.

IP Whitelisting

Customers who want to ensure an even higher level of security in DocuSign should configure Single Sign-On. Prior to SSO, IP Whitelisting was a way that administrators could add a degree of certainty in assuring only authorized logins were happening on their account, but SSO is a richer, more robust solution that supports a global and increasingly mobile workforce. If you have IP Whitelisting configured on your account, Going forward, you must call DocuSign Support to make any updates to your whitelist; the user experience for managing IP whitelisting will not be implemented in the New DocuSign Experience.

Envelope Transfer Across Accounts

DocuSign is working to make envelope transfer more secure. Allowing envelopes to be transferred to any account within our system (even accounts you may not be able to administer) could lead to unauthorized placement of envelopes into an unintended account. Envelope Transfer in the New Experience will allow you to transfer envelopes only at the Organization level across accounts that you manage. Envelope transfer in the Classic experience will be deprecated.

Company Directory in Contacts

DocuSign is working to make contact sharing more secure. Good privacy conventions made us reconsider the degree to which we were presenting account member’s information to the rest of the users on the same account. This is why we are no longer including Company Directory contacts to users with a Shared Address Book permission. This feature will not be implemented in the New DocuSign Experience.

Adding DocuSign for Salesforce Contacts to an Envelope from within DocuSign

Support ending February 2018. In the Classic DocuSign Experience, DocuSign for Salesforce (DfS) customers were able to add Salesforce contacts to envelopes when sending from DocuSign without first adding any DfS contacts to their DocuSign account. This ability is not part of the core DfS functionality and presents a potential security risk and as such is not available in the New DocuSign Experience.

Manage Signers

Manage Signers is deprecated in favor of automatic signer account creation because admins no longer to have to deal with managing signers in the Classic admin console. DocuSign handles creation of users who do not have accounts on the fly. This makes the flow easier for senders who no longer see the error “This signer does not have DocuSign account.”

In the New DocuSign Experience for sending, your account can be enabled to automatically create DocuSign accounts for signers that do not already have an account. When this option is enabled and you send to a signer that does not have a DocuSign account, DocuSign creates an account for the signer and sends an account activation email in addition to the request to sign email. DocuSign recommends that you contact your signers to let them know that they will be receiving an account activation email from DocuSign. You can see whether automatic account creation is enabled for your account by looking at the Login Requirements setting. This option is enabled by DocuSign and you can contact your DocuSign Account Manager to request to enable the option.

TLS 1.0 Support to End June 30, 2018

Following industry best practices, DocuSign will end TLS 1.0 support effective June 30, 2018.

TLS versions 1.1 and higher will still be supported. TLS 1.0 is employed by a few customers to support interaction with legacy systems, but industry best practices require that TLS 1.0 use be discontinued. All internet browsers currently supported by DocuSign already default to newer versions of TLS, so this change will go unnoticed by web and mobile users.

Connect Mutual TLS Certificates Renewal May 28, 2018

Update your Connect Mutual TLS certificates by May 28, 2018.

Who is affected

DocuSign customers who use the optional Mutual TLS feature with either Connect or the Envelopes::create API call with the eventNotification parameter.

Connect can be configured to respond with its X.509 certificate in response to a request from the customer's web server (Mutual TLS). Different certificates are used for the DocuSign demo (developer sandbox), North American, and European data centers.

We will replace the current certificates on May 28, 2018 with a new set of certificates.

What you need to do

If your Connect web server uses Mutual TLS with DocuSign, you must update your server by May 28, 2018.

Important dates

March, 2018: The new certificates will be available in March. The exact schedule has not been set yet. A new update will be added to the Admin Tool’s System Update panel. The new update will enable customers to temporarily or permanently update to the new 2018 certificates.

May 28, 2018: We will automatically activate the system update for all customers. Starting on this date, Connect Mutual TLS will only use the 2018 certificates.

We will provide updated information in the March release notes.

Print Driver Version 3.1.3 Now Available

Updates to Print Driver include:

  • MSI installer - Users can now install using either an .exe or an .msi installer.
  • Admin required for installation - You must have admin privileges to install Print Driver and to change the following (you do not need admin privileges to change other Print Driver settings):
    • Settings in the Print Driver Advanced tab
    • The default browser
    • The log file location
  • Printing settings - Added option to reset session when you click Finish in DocuSign. This speeds processing and eliminates one click when processing a sequence of envelopes.
  • Updates for Citrix - Support for XenDesktop v 7.6 and v7.8. Ability not to require users to accept Terms and Condition each time they log in.

For more information about Print Driver, see the Print Driver documentation on our support site.


Connect HTTP Listener Sunset Reminder

The DocuSign Signature developer system (demo.docusign.net) can be configured to make Connect webhook calls to customers’ servers through HTTP or HTTPS connections only if the demo account was created before July 2017. 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.

Note: If you do not see the "Only HTTPS" option on the System Updates page, your account is already configured to use HTTPS only.

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.

May 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 following bug fixes were deployed to the DocuSign Production environment on February 2, 2018 as part of the DocuSign February 2018 release.

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.

High Priority Bug Fixes

  • After an editor edited an envelope, future editors received the error: "Envelopes and doc-uments are not editable if at least one recipient has completed an action." and were unable to edit or correct the envelope (MAR-23971).
  • When trying to delete pages or fields from a template with nearly 1800 fields, user was unable to complete either action, receiving the errors " "Save Error: Some fields might be out of sync. Tab specified was not found. TabId: ..." or "Save error: Some fields might be out of sync. Bad Request." (MAR-24281).
  • Customer was experiencing latency up to more than 1 minute per action to edit templates or envelopes created from templates (MAR-24801).

Medium Priority Bug Fixes

  • 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).
  • When placing Text fields on a document or template, the field shifts downward when viewed by the recipient, partially covering any text below the field (MAR-24570).
  • When using Print Driver to add multiple documents to an envelope, users were unable to apply matching templates to the documents (MAR-24634).
  •  When auto-applying templates to multiple documents simultaneously, the recipient roles were duplicated on the documents (MAR-24837).
  • When trying to delete pages from a document, user was unable to complete the action, receiving the errors "Save Error: Some fields might be out of sync. The page number specified in the tab element is not in the document that the tab refers to." or "Save Error: Some fields might be out of sync. Tab specified was not found. TabId: ..." This issue is related to and fixed by MAR-24281(MAR-24951).
  • When using template matching and replacing the underlying document with another doc-ument appropriate for matching, the fields on the replacement document were stacked atop the corresponding fields when the template was applied (MAR-24956).
  • When editing a template created in the Classic DocuSign experience that contains anchors with an assigned offset, changing the anchor text to a different word did not move the field to the specified text.
  • This has been fixed in Demo and will be available in phases after the February 2018 Production release (TT-976).
  • In the New Experience, when replacing documents in a template that had been created in the Classic Experience, the documents lost the anchor text that had been applied in the original template (TT-823).
  • When using a template where a signature type had been set on a recipient, the saved sig-nature type was not displayed, requiring it to be redefined (MAR-25040).
  • Using Org Admin to add a member to an account, it appeared in the UI that the new member's status was ACTIVE in the new account, when in fact they were actually PENDING (ADMIN-4448).
  • When an account had Signature Pad Allowed enabled and Signature Pad Choose Type set to Topaz SigPlusExtLite, that signature pad was not listed in the list of available pads (ADMIN-4534).

Low Priority Bug Fixes

  • When creating scheduled reports, email addresses in the form some.-name@company.division were not recognized as valid email addresses (MAR-21820).
  • In organizations with multiple accounts, the account list in Admin was not alphabetized within each account (ADMIN-4345).

Coming Soon

This following features and bug fixes will be available in the near future. Any release dates listed are tentative and subject to change.

Enforce Unique Template Name Setting

The Admin console will include the option "Enforce Unique Template Name", which will be off by default. When enabled, if a user attempts to save a template with the same name as an existing template, they will be prompted to create a different name.

Template Default Filter Changing to All

The list of templates displayed will default to All instead of the current default of 6 months, allowing users to more easily find and use their templates.

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.

  • Correcting an envelope to move a recipient to a lower (one before the current setting) AND changing the recipient type changes the recipient type but does not change the routing order, nor does an error occur (MAR-23344).
  • Templates cannot be filtered by the last modified date (MAR-23710).
  • If an editor, who is not the sender, of an envelope tries to change her routing order to later in the list, and then tries to discard the change, she receives an error and the envelope can be corrected by neither the editor nor the sender (MAR-23720).
  • Merge fields are displaying random characters instead of the preloaded text (API-7804).
  • When using automatic template matching in the new experience, if there are multiple possible matching templates the most relevant is not selected in the list, and if there is only one matching template, it is not automatically selected requiring additional clicks by the user (MAR-23280).
  • When "Allow Sender to set email language for recipients" was disabled, senders are still seeing the option for each recipient (MAR-24352).
     

« Back to Releases

Trustpilot