DocuSign Spring '16 Release Notes

DocuSign Spring '16 Release Notes Published March 17, 2016 UPDATE This document provides information about the updates deployed to the DocuSign Production environment on March 10, 2016 as part of the DocuSign Spring '16 Release. Note: These Release Notes were updated since the release is deployed to the DEMO environment with the following: Added the Sender as Signer Authentication Requirement. March 17 Update: The Sender as Signer Authentication requirement change was reverted and will be re-evaluated for deployment sometime in the future. Added a note clarifying that the signing resource file updates do not overwrite custom signing resource files. Removed bug fix items WAPP-5976 and SIGN-8911. A link to the most recent version of these Release Notes can be found on the DocuSign web site DocuSign Product Release Information page. New DocuSign Login Page 2 Sender as Signer Authentication Requirement 4 New Date Time Formats 4 Branding Signing Resource File Updates 5 API Updates 7 Known Issues 9 Bug Fixes 10

2 New DocuSign Login Page DocuSign is launching a new login experience. Our goal is to create a platform to ensure all identity features work consistently across all DocuSign applications. Starting today we ll be updating our DEMO environment with the new login experience, and in the weeks that follow we will be slowly rolling the change out to the Production environment. There are a few things we want to share with you about the new login. If you encounter any issues, please contact your account manager or a customer support representative. What does the new login experience look like? Other than a few subtle changes in style, the new login experience behaves in the exact same way. Most users won t notice the difference since the behavior will remain the same. What does this change? Users will continue to log in to DocuSign as before with the same username and password. Nothing about your account or login is changing. For most users, this will be business as usual.

3 For accounts that use SSO with domain trapping If your company is using Single Sign On (SSO) with domain trapping, today you will see the experience on the left when you log in. By selecting the NEXT button you are redirected to your corporate login page. With the new login, you will see the experience on the right. The new button will say COMPANY LOGIN instead of NEXT. Selecting this button will take you to the same destination to complete SSO. For users that log in with social If you are a user that is using social login, the options are now under this link labelled More log in options. Select this link to access all the options for social login. This is just the first step in the direction to a more unified login experience. We re excited to hear your comments and feedback.

4 Sender as Signer Authentication Requirement Update: This change was reverted on March 17, 2016 and will be re-evaluated for deployment sometime int he future. In October 2014 DocuSign introduced an optional account setting that required envelope senders that were also signers of the envelope to pass recipient authentication checks. To improve compliance and security considerations, DocuSign is changing this to be a requirement for all accounts. Note that senders can remove the authentication requirement before sending to avoid the authentication check. Example: A sender is using a template that requires all recipients to pass access code authentication. The sender is added as a signer and the document is sent. The sender is then asked if they would like to sign. Previously, the sender would go directly to the signing workflow. Now the sender must pass the access code authentication check before they can sign the documents. This change also removes the Sender as Signer must authenticate when requested setting in Classic DocuSign Experience Features. New Date Time Formats DocuSign is working to unify and improve the date-time format information and consistency across all DocuSign applications. As part of the Spring 16 Release DocuSign is providing additional date time formats that can be selected for accounts and users through DocuSign applications to support our international customers. The new formats will be available in the Classic DocuSign Experience with the deployment of the DocuSign Spring '16 release on March 4 and in the New DocuSign Experience by mid-march. The first new date time format is available to all languages: yyyy/mm/dd HH:mm Example: 2016/02/15 00:58 The other new formats are only available if the language listed on the left is selected as the user s language: German: d. MMMM yyyy HH:mm Example: 6. Januar 2016 Spanish: d' de 'MMMM' de 'yyyy HH:mm Example: 6 de enero de 2016 Russian: d MMMM yyyy 'r.' Example: 6 Января 2016 г. Portuguese (Brazil): d' de 'MMMM' de 'yyyy HH:mm (6 de Janeiro de 2016) Portuguese (Portugal): d' de 'MMMM' de 'yyyy HH:mm (6 de Janeiro de 2016) Chinese (Simplified): yyyy' 年 'M' 月 'd' 日 ' HH:mm (2016 年 1 月 6 日 )

5 Chinese (Traditional): yyyy' 年 'M' 月 'd' 日 ' HH:mm (2016 年 1 月 6 日 ) Japanese: yyyy' 年 'M' 月 'd' 日 ' HH:mm (2016 年 1 月 6 日 ) Korean: yyyy' 년 'M' 월 'd' 일 ' HH:mm (2016 년 1 월 6 일 ) Branding Signing Resource File Updates As part of the Spring '16 Release, there are several changes to the default text used in the branding signing resource file. Note: If you are using a custom signing resource file, then any modified values in that file are preserved. For any items changed in this update, if you are using the default value, then the new default value is applied. Help and Information Text Changes These changes update the information message text to remove colors from the messages to make the text easier to understand for accessibility. Node data name: DocuSign_HelpfulMessageInitialHere New default value: Select the initial field to create and add your initials. Old value: Select the yellow initial field to create and add your initials. Node data name: DocuSign_HelpfulMessageInitialHereOptional New default value: Select the initial field to add your initials. Old value: Click the yellow initial field to add your initials.. Node data name: DocuSign_HelpfulMessageSignerAttachment New default value: Select the attachment field to add a document Old value: Click the yellow attachment field to add a document Node data name: DocuSign_HelpfulMessageSignHere New default value: Select the sign field to create and add your signature. Old value: Select the yellow sign field to create and add your signature. Node data name: DocuSign_HelpfulMessageSignHereOptional New default value: Select the sign field to add your signature.

6 Old value: Click the yellow sign field to add your signature. Decline to Sign Warning and Reason Changes These changes update message text for the Decline to Sign warning and reason dialogs to make the text easier to understand for accessibility. Node data name: DeclineWarning_Text New default value: If you continue, this document will be voided. Old value: If you choose to continue, this document will be void and inaccessible to other signers.. Node data name: DeclineWarning_FinishLaterDescription New default value: To request changes to this document, [[[DocuSign_FinishLater]]] and contact the sender. Old value: To request changes to this document, please select [[[DocuSign_FinishLater]]] and contact the sender directly with your request. Node data name: DocuSign_DeclineDesc New default value: Please provide a reason for declining: Old value: Please provide a reason to [[SenderName]] for declining: Assign to Someone Else Changes These changes update message text for the Assign to Someone Else dialog to make the text easier to understand for accessibility. Node data name: DocuSign_ChangeSignerInfo New default value: Selecting the Assign to Someone Else button will send a notification to the person to whom you assigned this envelope. The original sender will also receive a notification. You will be added as a Carbon Copy (CC) recipient. Old value: Clicking the Assign to Someone Else button will send a notification to the person to whom you assigned this envelope. The original sender will also receive a notification. You will be added as a Carbon Copy (CC) recipient. Node data name: DocuSign_ChangeSignerInfoNoCC New default value: Selecting the Assign to Someone Else button will send a notification to the person to whom you assigned this envelope. The original sender will also receive a notification.

7 In addition, you will no longer have access to the envelope. Old value: Clicking the Assign to Someone Else button will send a notification to the person to whom you assigned this envelope. The original sender will also receive a notification. In addition, you will no longer have access to the envelope. Agent Managed Envelopes - Manage Addresses Changes These changes update message text for the Decline to Sign warning and reason dialogs to make the text easier to understand for accessibility. Node data name: Intermediary_DeclineDesc New default value: Reason for voiding:. Old value: Reason for voiding the envelope (this will be sent to [[SenderName]]). API Updates This section covers new and updated features and functionality delivered in the DocuSign APIs. REST API POST Template Edit View This provides a URL to the template edit view of the DocuSign UI for the specified template ID. This is a one-time use login token that allows the user to be placed into the DocuSign template edit view. Note that when using the response URL you can set the default UI page shown to a user by using the send query string parameter on the end of the URL. Setting send=0 starts the user on the prepare page where the sender can add documents and recipients, while setting send=1 starts the user on the tagging page. The setting defaults to the prepare page. Upon completion, the user is returned to the return URL provided by the API application. Important: iframes should not be used for embedded operations on mobile devices due to screen space issues. For ios devices DocuSign recommends using a WebView. URL: /accounts/{accountid}/templates/{templateid}/views/edit Formats: XML, JSON HTTP Method: POST

8 Parameters: Name Reqd? Type Description returnurl No String Identifies the return point after editing a template. Important You must include HTTPS:// in the URL or the redirect might be blocked by some browsers. DocuSign returns to the URL and includes an event parameter that can be used to redirect the recipient to another location. The possible event parameters returned are: save (user saves the template) cancel (user cancels template editing) error (there is an error when performing the edit) sessionend (the sending session ends before the user completes another action) Example Request Body The following example shows the request json body. POST https://{server}/restapi/{apiversion}/accounts/{accountid}/templates/ {templateid}/views/edit X-DocuSign-Authentication: <DocuSignCredentials><Username>{name} </Username><Password>{password}</Password><IntegratorKey>{integrator_key} </IntegratorKey></DocuSignCredentials> Accept: application/json Content-Type: application/json { "returnurl": "string" } Response The response returns the template edit URL. When using the response URL you can set the default UI page shown to a user by using the send query string parameter on the end of the URL. Setting send=0 starts the user on the prepare page where the sender can add documents and recipients, while setting send=1 starts the user on the tagging page. The setting defaults to the prepare page.

9 Example: For the URL - https://docusign.net/member/startinsession.aspx?send=1 The user will start on the tagging page of the template view. The following example shows the response json body. Example Response Body The following example shows the response json body. { } "returnurl": "string" Known Issues This section covers any known issues present in the release which are likely to impact users. Password Reset Security Questions For users that have selected a default language that uses Unicode characters (Chinese Simplified, Chinese Traditional, Japanese, and Korean), there is a known issue where the password reset security questions are returned as question mark characters (?) and are not translated into the selected language. DocuSign is working to correct this issue. Until it is corrected, DocuSign recommends that accounts not require password reset security questions for account users with a user language of Chinese Simplified, Chinese Traditional, Japanese, or Korean.

10 Bug Fixes Note: Issue numbers that are bold underlined text are externally reported bugs or customer commitments that were fixed in the listed release or service pack.. DocuSign Spring '16 Release Bug Fixes The following bug fixes were deployed to the DocuSign Production environment on March 10, 2016 as part of the DocuSign Spring '16 release. The name-number is the internal DocuSign tracking number for the bug. WAPP-4640: When trying to download completed documents as separate PDF files, documents with Chinese, Japanese, and Nepalese characters in the document title were not being downloaded. WAPP-5620: When uploading a template in the Classic DocuSign Experience, Conditional Field settings were being removed from the template. PLAT-4174: The Recipient Viewed Email Template had PDT hard-coded for the delivery time. PLAT-4355: Purge Notification emails were not being sent to senders if the signer purge notification option was not selected. SIGN-6883: When using a direct PowerForm changes to a Full Name tag were not automatically replicated to all Full Name tags in the PowerForm. SIGN-7168: When the Part 11 module is enabled for an envelope and a signer does not have a signature on file, the signer could change their name when adopting a signature but the change was not reflected when the signer was authenticating the signature. SIGN-7580: Added support for displaying custom tooltips during signing for Signature, Initials, Attachment and List tabs created in DocuSign APIs. SIGN-7965: When using freeform signing, name and email fields were not updating correctly if the signer added fields, exited the signer session, and upon return added and edited more fields. SIGN-8120: Updated the order in which languages are presented in the language selector in the Signing footer. SIGN-8213: After an in-person signing session where a signer declined to sign, the signer host was redirected to a log on page instead of returning to the web application. SIGN-8298: Corrected an issue where the post-signing custom landing pages were not always correctly displayed. SIGN-8451: During signing, English signature and initial fields were inadvertently used if the signer s default browser language is set to a language other than English and the signing

11 language setting was Browser Default Language. SIGN-8519: When Account Server was active for an account, if an envelope was sent for In Person Signing and the host email had upper-case letters, the host authentication would fail. API-3034: When using the REST API to send an envelope the Transform PDF Fields setting was not working at the envelope level. API-3388: When using the REST API to send an envelope, the Auto Navigation setting was being ignored. February Service Pack Bug Fixes The following bug fixes were deployed to the DocuSign Production environment on February 8, 2016 as part of the February Service Pack. The name-number is the internal DocuSign tracking number for the bug. WAPP-5691: When using the REST API to create and save a draft envelope with SMS Authentication, the phone numbers were not shown when the draft envelope was opened in the Classic DocuSign Experience web application. SIGN-4758: When using the concealed field option, the asterisks mask was intermittently being implemented when senders were viewing form data. SIGN-5850: During signing, initials were not saved in shared fields when the signer chooses Finish Later option. SIGN-6644: Removed an out of date billing plan item that was causing a display error when viewing Billing Plan usage information. SIGN-7039: The signatures and initials for signers without DocuSign accounts were being reset after the signer completed their portion of an envelope due to a signer email client issue. SIGN-7086: Updated the Assign to Someone Else dialog to WCAG standards. SIGN-7329: The automatic navigation option caused an envelope to become unresponsive when the envelope had a standard esignature field and an ICP Brazil digital signature. SIGN-7487: After declining to sign a captive (embedded) signer was able to view, but not sign, an envelope by using the browser Back button. SIGN-7828: When using the Classic DocuSign Experience to send with an OpenTrust signature requirement and error was being generated if the signer s name contained a comma. SIGN-7835: During signature adoption when the display screen was re-sized the signature and initial previews overlapped the adoption description text. SIGN-7852: Established a server switch to communicate that the correct display and hide options for captive (embedded) signing links. This is related to SIGN-7853. SIGN-7853: Updated signing to correctly display and hide links for captive (embedded) signers.

12 This is related to SIGN-7852, SIGN-8253, and SIGN-8254. SIGN-7981: Removed an unused onclick option in the branding signing resource file. SIGN-8089: When using the Chrome browser for captive signing in an iframe, the signing page was not correctly rendering due to an issue with cookies. SIGN-8253: Updated mobile web browser signing to correctly display and hide links as appropriate for captive (embedded) signers. This is related to SIGN-7853. SIGN-8254: Updated signing to correctly display and hide the access code/security check code as appropriate for captive (embedded) signers. This is related to SIGN-7853. SIGN-8255: Updated mobile web browser signing to correctly display customer footer links for captive (embedded) signers. SIGN-8293: Captive (embedded) signers that failed access code authentication were still unable to sign after the envelope was corrected. SIGN-8339: The in person signing host message text was not correctly shown in the signing notification email template. SIGN-8374: During signing the Select Style signature options were not disappearing when Draw signature was selected. SIGN-8376: When signing on a mobile device if the upload a signature or initials option was enabled, the upload button was not scaling correctly causing the style selection to appear too small on the screen. SIGN-8382: Updated DocuSign Support contact information text and links in email notifications for signing documents. SIGN-8501: When signing on a mobile device and using the Select Style option to adopt a signature for a long name, the signature image was not scaling correctly and would run off the page. PLAT-4069: When Document Retention is set, envelopes with Authoritative Copy enabled and that had been exported were not being purged in the system. PLAT-4125: A user was unable to void a shared envelope when the user was also an envelope recipient. PLAT-4195: Initial data entered in a field was not being shown to all recipients when the option was enabled on sending. PLAT-4303: When using the previous signing version, the knowledge-based ID Check page was not displaying after the signer entered their information. API-2813: When creating an envelope from a template through the SOAP API: the document visibility settings from the template were not being correctly applied to the envelope. API-3034: When using the REST API to send an envelope the transformpdffields option was not

13 converting fields to DocuSign tabs. The option was functioning correctly for composite and inline templates. API-3099: Email addresses for captive (embedded) recipients were being incorrectly updated if the recipient had a DocuSign account and changed their email address. This caused an error when the recipient token for captive recipient was requested through the REST API. API-3202: When creating an envelope from a template through the SOAP API the error The Watermark feature is not allowed for this envelope because a digital certificate is present. was generated even when a digital certificate was note required for the envelope. January Service Pack Bug Fixes The following bug fixes were deployed to the DocuSign Production environment on January 8, 2016 as part of the January Service Pack. The name-number is the internal DocuSign tracking number for the bug. WAPP-3556: When using the Classic DocuSign Experience, users were unable to upload template XML files with conditional or calculated fields. WAPP-5777: When using the Classic DocuSign Experience, the Sender Void page was not translated into French. SIGN-5903: The text used in document History for showing a change in signing responsibility could be misinterpreted and was updated to clarify who made the change in signing responsibility. SIGN-7342: Updated the navigation instruction text when signing through a mobile web browser. SIGN-7488: When the branding signing resource file was used to hide the Decline to Sign option (DeclineAllow=false), Decline fields placed on documents did not function. SIGN-8234: Updated the message in the signing completed dialogs to say a copy of the documents will be sent when completed by all signers. The message previously said a copy has been sent. PLAT-4030: When using the Classic DocuSign Experience to apply templates with a large number of anchor tags, the system was timing out and showing a server error. PLAT-4038: When using the Classic DocuSign Experience to upload template XML files with accessibility reading zones, the zone information was being removed from the template. API-2694: When using the REST API to update user profile information, the authenticating user was being updated instead of user specified in the call. API-2800: When using DocuSign for Salesforce and applying a template to a document, the custom merge field information for template fields was not being applied to the fields. API-2852: When using the REST API to set a Radio Group Tab requireinitialonsharedchange

14 property to true, signers were not required to initial when they modified the Radio Group. API-2961: The row information was missing from the REST API - custom merge field information which impacted the DocuSign for Salesforce integration with the New DocuSign Experience. API-3068: When using the SOAP API to create an envelope, errors were being generated due to integrator key verification checks.