Winter '17 Release Notes

Transcription

1 Winter '17 Release Notes Published: December 2016 This document provides information about the updates deployed to the DocuSign Production environment on December 1, 2016 as part of the DocuSign Winter '17 Release. Note: Some items listed in the Release Notes were implemented in previous monthly service packs. In those cases, the month the item was implemented is shown in the heading for that item. Note: These Notes were updated since the last deployment with the following: Edited topics to reflect events that have already occurred (certificate expiries, cloud storage provider removal, etc.) Added new topics: Signing Agent, Electronic Notary, Supplemental Documents, and Long Term Validation Added API updates: Supplemental Documents and Electronic Notary In Person Signers Recipient Type Added additional accountsettings settings Cloud Storage Provider Update Reminder 3 Any Signer Sunset Reminder 4 DocuSign New Signing Update Reminder 5 DocuSign Connect Certificate Update Reminder (October) 6 DocuSign Admin Update (October) 11 In Person Signing Update (November) 12 Admin Audit Log Update (November) 13 Long Term Validation 14 Enhanced refresh_token Lifetime (November) 15 DocuSign Mobile App Updates (October) 16 Login Screen Redesign 17 DocuSign Stamps 18 Supplemental Documents 23

2 enotary - New Jurisdictions and Features 27 Signing Agent 28 Branding Signing Resource File Updates 29 API Updates 34 Bug Fixes 44

3 3 Cloud Storage Provider Update Reminder On November 9, 2016, DocuSign removed the ability to directly use the cloud storage providers ShareFile, Evernote, and Salesforce as document sources for sending and templates in both the Classic DocuSign Experience and New DocuSign Experience. Users can still use other cloud storage providers, such as Box, Dropbox, and Google Drive, as well as upload files directly. We made the decision because we wanted to invest our efforts in features that would drive the highest impact to our customers. Note that this change does not affect the ability to send documents from Salesforce for DocuSign for Salesforce users.

4 4 Any Signer Sunset Reminder As of March 2, 2017, the Any Signer feature will be retired. Signing Groups will replace Any Signer and is now available for Enterprise Edition, System Automated Premium Edition, Enterprise Professional Edition, and as an add-on to Business Professional Edition. If your account is currently using the Any Signer feature, please reach out to your Account Manager for additional details.

5 5 DocuSign New Signing Update Reminder DocuSign has automatically enabled the DocuSign New Signing Experience Spring 16 for DocuSign accounts on the following schedule: June and July Production environment enabled for all free accounts. August 2016 Demo environment enabled for all paid accounts. November 14, 2016 Production environment enabled for all paid accounts. DocuSign New Signing Experience Spring 16 maintains backward compatibility for existing templates with reading zones and for current custom branding configurations. Customers that are using templates with reading zone, custom branding, and signing resource file branding do not have to take any actions to continue using those items. DocuSign is committed to providing our high quality solution in a manner that is accessible to all individuals, regardless of their abilities or disabilities. DocuSign has adopted the WCAG guidelines as a development standard for the Signing experience and is committed to continue to improve the accessibility support functionality to provide all people equal access to and the freedom to interact with DocuSign s signing application when using assistive or adaptive technologies. To this end, DocuSign will continue to implement new features with accessibility in mind and remediate issues reported according to our standard SLA. For additional details, see the DocuSign Voluntary Product Accessibility Template (VPAT) for the DocuSign Signing Experience - Spring '16 release on the DocuSign Support Center.

6 6 DocuSign Connect Certificate Update Reminder (October) DocuSign has replaced the current DocuSign Connect certificate with three new certificates; one for DocuSign s North American (NA) servers, one for DocuSign s European (EU) servers, and one for DocuSign s DEMO environment. DocuSign has obtained the new certificates and has made them available with the DocuSign Fall 16 Release. Customers that use the current Connect certificate must update the certificate in their systems related to DocuSign Connect. The current certificate expired on November 11, 2016 and has been decommissioned systematically from the DocuSign environments on the following schedule: DocuSign DEMO environment: October 11, 2016 DocuSign Production environment: October 29, 2016 Actions Log on to your DocuSign account, then check your DocuSign Connect Settings Configuration Settings and check the API Notification parameters included your API requests to DocuSign, as outlined in Step 1. If either your Connect configuration or API request uses the DocuSign Connect certificate, then follow Steps 2 through 5. If you have any questions, please contact your DocuSign Account Manager. Step 1: Check to See Whether You are Using a Connect Certificate Use the following steps to determine whether your account uses the Connect Certificate: Important: You must check each Connect configuration associated with your account on all Production and Demo environments. Go to the Connect Configuration Settings for your account in the Classic DocuSign Experience: Log on to the Classic DocuSign Experience web application, click your profile image and select Preferences. Under Account Administration, click Connect.

7 7 Click a DocuSign Connect Configuration. On the DocuSign Connect Settings Configuration page, check the settings to see whether the Sign Messages with X509 Certificate, Include X509 Certificate in SOAP Header, or Require Mutual TLS options are selected. If any of these are selected, you must obtain the new certificate as outlined in Steps 2 through 5. Check your API requests to see whether they are set to receive API Envelope Notification with either of the following parameters are set to true : "signmessagewithx509cert" includecertificatewithsoap If either of these parameters is set to true, you must obtain the new certificate as outlined in Steps 2 through 5. Step 2: Obtaining a New Certificate Download and install DocuSign s new certificate on all web servers running your DocuSign Connect listeners or web applications using the DocuSign API as follows:

8 8 Important: You must download the new certificate from all Production and Demo environments used by your account. Log on to the Classic DocuSign Experience web application, click your profile image and select Preferences. In the navigation pane on the left side of the page, under the Account Administration heading, click Features. Scroll down to DocuSign API section and click Download new x.509 certificate. Import the new certificate to your Development and Test environments. You should maintain the current DocuSign certificate on your web servers at this time Step 3: Test the New Certificate in the DocuSign Demo Environment After installing the certificate, you must test your application in the DocuSign Demo environment to ensure it is functioning correctly. Before testing, enable the new DocuSign certificate in the Demo environment. Log on to the Classic DocuSign Experience web application Demo environment. In the upper right corner, click your profile image and select Preferences. Under the Account Administration heading, click Features. Scroll down to the DocuSign API section and select Use the new DocuSign x.509 certificate in Connect messages and save the change.

9 9 If you use DocuSign Connect, then test all your configurations with the new certificate as follows: Create new transactions in DocuSign Demo environment Download messages to your Test environment Verify that you received the expected Connect messages If you are using the DocuSign API with either "signmessagewithx509cert": "true" or includecertificatewithsoap : true, then test the new certificate as follows: Create new transactions using your API integration in DocuSign Demo environment Download messages to your Test environment Verify that you received the expected Connect messages Step 4: Update the Production Environment for Your Web Application After you have completed Step 3 and validated the new configurations in Demo, follow the appropriate steps below to update your Production integration. Enable the new DocuSign certificate in your Production environment. Log on to the Classic DocuSign Experience web application production environment. In the upper right corner, click your profile image and select Preferences. Under the Account Administration heading, click Features. Scroll down to DocuSign API section and select Use the new DocuSign x.509 certificate in Connect messages and save the change.

10 10 If you use DocuSign Connect, then test all your configurations with the new certificate as follows: Create new transactions in the DocuSign production environment Download messages to your Test environment Verify that you received the expected Connect messages If you are using the DocuSign API with either "signmessagewithx509cert": "true" or includecertificatewithsoap : true, then test the new certificate as follows: Create new transactions using your API integration in DocuSign production environment Download messages to your Test environment Verify that you received the expected Connect messages Step 5: Clean up Current Signed By Certificate in Your Environments After you have successfully updated to the new DocuSign Connect certificate, you can remove DocuSign s current certificate from your Development, Test, and Production environments. DocuSign decommissioned the current Connect certificate on October 29, 2016 and your certificates must have been updated before then. If you have any questions, please contact your DocuSign Account Manager.

11 11 DocuSign Admin Update (October) As part of our continuing improvements to support customer transition to the new DocuSign Admin application, DocuSign has added a link in Classic DocuSign Experience Preferences that goes to the new DocuSign Admin application. The link is shown in the left navigation panel, under the Account Administration heading. This link lets administrators switch to the new DocuSign Admin application, allowing them to make new DocuSign Admin their primary interface for administration functions. The link is currently available in the Demo environment for administrators that have access to both the New DocuSign Experience and Classic DocuSign Experience. DocuSign plans to expose the link in the production environment over the next month. In addition to the general rollout, the link will be automatically added for administrators that use a link in the DocuSign Admin Classic Items page to go to a Classic DocuSign Experience administrative feature.

12 12 In Person Signing Update (November) This update adds a new dialog to the in person signing flow when there is more than one in person signer in the same routing order. When the signing host begins an in person signing session, the new dialog is shown asking the host to select the signer for this session. There were no changes to the rest of the in person signing flow. Additionally, there were text updates in the other in person signing dialogs. See the Branding Signing Resource File Updates for a list of all the text changes.

13 13 Admin Audit Log Update (November) The account audit log available through DocuSign Admin is now a fully released feature. The beta period for the audit log has ended, and account administrators can use the feature to see changes to their account settings, billing information, plan type, and users. The log also enables administrators to download this information as a comma separated value (CSV) file. For more information, see the Account Audit Logs guide.

14 14 Long Term Validation The digital certificate that had previously been used to sign documents downloaded from DocuSign expires on December 20, Long Term Validation (LTV) is a feature of the PDF standards that can confirm whether a signature on a PDF is valid for years after the certificate on the PDF was created. DocuSign is not LTV-enabled at this time, which may result in a yellow alert when you open a signed PDF in Acrobat after the previous certificate expires. This alert has no affect on the validity or legality of the document. It simply means that Adobe Acrobat is not capable of determining whether a signature's certificate was valid at the time of signing. You can find more information about LTV here. DocuSign is currently looking into having LTV automatically enabled for all completed, downloaded documents. In the meantime, if you want to enable LTV, you can do it manually by following the steps in this article.

15 15 Enhanced refresh_token Lifetime (November) Client applications can now request longer lifetimes for refresh_tokens. Prior to this feature, refresh tokens had an undefined lifetime and would expire after approximately 30 days. When this scope is requested, the refresh_token is given the maximum allowable lifetime based on the security policies defined by the authenticating users or their organization. Each POST to the /token endpoint, provides a new refresh_token with an updated expiration. Implementers must always store the newly-refreshed refresh_token to take advantage of the extended lifetime. All applications should expect refresh tokens to expire eventually, and so must handle reauthenticating end users.

16 16 DocuSign Mobile App Updates (October) DocuSign has updated the icons used for free-form signing in both the ios and Android mobile apps.

17 17 Login Screen Redesign In December, DocuSign updated our Demo environment with the new login experience. We will be updating the Production environment over the next several months, which means that some users will see the new login design before the end of the year. There are currently many ways to sign into your DocuSign account. Whether you use a user name and password, or Single Sign On (SSO), we wanted to create a frictionless experience for signing in to your account. The new design helps ensure that you re signing in with the correct authentication method while reducing the number of clicks required to sign in. We want to review the new login behavior and remind you that if you encounter any issues, contact your account manager or a customer support representative. What does the new login experience look like? Most users may be familiar with this design as other Internet services have also adopted a similar login experience. The new login experience first prompts you to specify your address, and then, based on your address, the system detects whether you can sign in with a password, or whether your company has required the use of Single Sign-on (SSO). If your account requires a password, then you are prompted to enter your DocuSign credentials. If your account requires the use of SSO, then you are immediately redirected to your Identity Provider. This design simplifies the number of options displayed by presenting only the login method that is available to each user. Not only does this improve the security of our product, but it also improves the usability. The new design is also compliant with Web Content Accessibility Guidelines (WCAG) to ensure our product is accessible to people with disabilities. What does this change? In some cases, the login page remembers your address from your prior session. This simplifies the experience by alleviating the need for you to type your address every time you sign in.

18 18 DocuSign Stamps DocuSign Stamps enables customers in varying markets, cultures, roles, and industry verticals to apply a stamp to be representative of their signature, official approval, or company acknowledgment to documents. For this initial release, DocuSign Stamps supports the following: DocuSign Admin: control to enable stamps for an account New DocuSign Experience: new stamp field to apply to documents and templates Signing: apply a stamp to a document by uploading a stamp image (Signing version v02 only) Certificate of Completion and Document History: audit trail of stamp events DocuSign Stamps is not supported in the Classic DocuSign Experience, or in earlier versions of Signing. DocuSign Stamps must be enabled on your account. Contact your account manager or DocuSign Customer Support to request access to this feature. DocuSign Admin - enable the stamp field DocuSign administrators can enable the Stamp field in DocuSign Admin Sending Settings: With Enable signature stamp field selected, senders on the account see the Stamp field and can add it to documents and templates. New DocuSign Experience - stamps Stamps are only available in the New DocuSign Experience. Senders and template creators can apply the Stamp field to their documents, and all users can manage their own personal stamps. Using the Stamp field If the Stamp field is enabled for your account, when you send a document for signature or prepare a template in the New DocuSign Experience, you see the new field:

19 19 Select a recipient, and then select and place the field onto your document. Signing with stamps Stamps are only supported in Signing version v02. Earlier versions of the signing experience are not supported. Recipients who have a stamp field to complete, can adopt a stamp to sign with or use a stamp already added to their account profile. Signers upload a stamp image, size and position it, and adopt it to apply to a document. If they have previously added a stamp, the stamp is available for them to select and apply to the document. Once a signer applies a stamp, they can resize it or replace it before they finish signing the document.

20 20 Stamp details are captured in both the Document History and the Certificate of Completion, which counts the number of stamps on a document and includes images of all stamps used in signing. Managing personal stamps Just like adopting a signature, you can add your own personal stamps to your DocuSign account profile. When you receive documents to sign that contain a Stamp field, you can use your saved stamps. You manage your personal stamps in your My Preferences, in the new Stamps section.

21 21 From this view, you can add and delete stamps, set a default stamp, and edit stamp names. When you adopt a stamp, you upload an image file of your stamp, and then scale and position the stamp to fit within the guide window:

22 22

23 23 Supplemental Documents You can use supplemental documents to provide additional information to recipients which does not require their signature, such as legal disclosures or terms and conditions. In signing, supplemental documents are represented by an action strip, keeping them separate from the content your recipients need to sign. Recipients view and accept supplements before they can complete a document. With supplemental documents, you can provide information necessary to meet regulatory or other internal compliance requirements of your industry or operation. All delivery, receipt, access, and acknowledgment actions are recorded in the Document History and the Certificate of Completion, providing a complete audit trail. With this release, supplemental documents are now available to DocuSign web and mobile web application users. This release adds account configuration and a sending web app interface for supplemental documents as described in the following paragraphs. Supplemental documents are available only in the New DocuSign Experience, and through the REST API. Supplements are supported in both documents and templates. DocuSign Admin - account configuration for supplemental documents If supplemental documents are enabled for an account, for this initial release, all account members who can send documents will be able to include supplemental documents in the envelopes they send. In addition, supplements are included by default when recipients download the document using either the Separate or Combined PDF option. You can use the API to exclude supplements from the download, and as signers cannot choose whether or not to include supplements when they download or print, you should consider the potential impact of very large supplements. Recipients can still download supplements from the supplement view window, which they open to view a supplement. In the DocuSign Admin Sending Settings, account administrators can adjust the default recipient settings as follows:

24 24 Signer actions settings - These settings control the default recipient actions for all supplements and apply to all recipients who must sign the document. Senders can modify these defaults for each supplement when they prepare their documents. Recipients must complete the specified actions in order to finish signing the document. For example, if the signer actions for a supplement are set to include both Must view and Must accept, then the recipient must select both actions before they can finish signing the document. Must view: All recipients must click the View button on the supplement strip to open the supplement view. Must accept: All recipients must click the Accept button on the supplement strip. New DocuSign Experience - sending supplemental documents For accounts configured to use supplemental documents, senders can add supplements to the documents they send. Senders can add multiple supplements to a document, and reorder them to dictate how they appear in signing with the other files sent for signature. For each supplement, the sender assigns the required signer actions. Recipients must complete the signer actions before they can finish signing the document. Fields cannot be added to supplements; the signer actions are the only controls added to supplements. Supplements are mainly intended for recipients who must sign a document. That is, for recipients who have are assigned Needs to Sign or In Person Signer recipient type. If you have Receives a Copy recipients, who simply receive a copy of a document, they can view any included supplements but are not assigned any signer actions. To add a supplement 1. Create a new document to send as usual, adding the files for recipients to view and sign. 2. For a supplement, upload the file just as you would any other file. Then select the document menu under the uploaded file and choose Set as Supplement.

25 25 3. (Optional) Reorder the files and supplements by dragging them into the order you want to present to your recipients. To specify recipient action for a supplement 1. After adding a supplement, continue to the add fields view and click the supplement action strip to open the supplement properties.

26 26 2. In the supplement properties, select the signer actions your recipients must complete in order to finish signing your document: Must View: Recipients must click the View button on the supplement strip to open the supplement view. Must Accept: Recipients must click the Accept button on the supplement strip. 3. Finish preparing your document, adding fields to the other files as needed, and send it. Audit Trail information Supplemental document interactions are logged in both the History and Certificate of Completion for an envelope. History When viewing an envelope s history through the DocuSign web application, the action taken (viewed or accepted) by the recipient for the supplemental document and a short description of the event is included. The name of the supplemental document is included in the description. Certificate of Completion Supplemental document information is shown in two places in the Certificate of Completion: Source Envelope Information section Shows the total number of pages for all supplemental documents associated with the envelope. Recipient Event sections Includes the supplemental document name and time stamps for the first time a recipient viewed the document, and for when the recipient accepted the supplemental document (if required).

27 27 enotary - New Jurisdictions and Features Building on DocuSign's earlier electronic notary offering for North Carolina, with the December release, we are expanding the DocuSign enotary product with additional jurisdictions, added functionality, and support for the New DocuSign Experience. This is a limited release to the Early Access Program participants only. DocuSign enotary enables in-person electronic notarization of documents. With DocuSign enotary, you can send documents and require recipients sign electronically at an in-person signing session with a Notary Public. The notary adds her electronic notary credentials to the document, witnessing the signature. Notary signing sessions are automatically recorded in the notary's Notary Journal in the DocuSign account. Contact your DocuSign account manager for details on pricing and plan availability. Summary of what's new Supported state jurisdictions: Alaska, Florida, Idaho, Indiana, Kansas, Kentucky, New Jersey, New York, North Carolina, Virginia, Washington New DocuSign Experience support: Notary Public Profile management Notarial Journals Sign with Notary option in sending REST API support

28 28 Signing Agent Some countries (for example, Brazil and Belgium) and specific market sectors (Pharmaceutical) use a physical device to store users' digital identification. These physical devices are often USB tokens or smart cards with the identity information issued and signed by a known and trusted provider. These devices cannot be read directly from a browser, so the Signing Agent, a Java component installed on a browser, acts as a communication bridge between the browser and the local certificates. This feature has been updated for NDSE and is available as of the Winter 2016 release to customers using SBS.

29 29 Branding Signing Resource File Updates This section covers the additions and changes for the branding signing resource file. Note: If you have uploaded 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. In Person Signing - Multiple Signer Selection (November) This adds a new node to set the text in the dialog used to select the in person signer when there is more than one in person signer in the same routing order. Node data name: ActivationSec_MultiSignersAvail Node description: Sets the text associated with the signer selection list. Node default value: There are multiple signers available. Select a person to sign. In Person Signing - Signing Host Welcome Introduction (November) These changes update the text on the Signing Host Welcome - Introduction dialog. Node data name: DocuSign_InPersonSecurityTitle New default value: Host an In-Person Signing Session Previous value: Host an In-Person Signing Node data name: DocuSign_InPersonStartDesc New default value: [[SenderName]] assigned you as the host for an in-person signing session for [[Signer]]. As a host, you will: Previous value: You have been asked by [[SenderName]] to be a signing host for the following documents. As a signing host you will: Node data name: DocuSign_InPersonStartStep1 New default value: Pass control of the signing session to the hosted signer. Previous value: Pass control of the mouse and keyboard or mobile device to [[Signer]]. Node data name: DocuSign_InPersonStartStep2 New default value: Ask the signer to enter any required authentication information.

30 30 Previous value: Ask [[Signer]] to enter required authentication information. Node data name: DocuSign_InPersonStartStep3 New default value: Help the signer sign and get a copy of the finished document. Previous value: Support [[Signer]] through the e-signing process. Node data name: DocuSign_InPersonStartStep4 New default value: Take control of the signing session. Previous value: Help [[Signer]] obtain a copy of the document when finished. Node data name: DocuSign_InPersonStartStep5 New default value: Log in to your DocuSign account to complete the signing session. Previous value: Collect the mouse and keyboard or mobile device from [[Signer]]. Node data name: DocuSign_InPersonStartStep6 New default value: (blank) Previous value: Enter your DocuSign account password to complete the signing process. In Person Signing - Pass to the Signer (November) These changes update the text on the Host an In Person Signing Session dialog for passing control to the signer. Node data name: DocuSign_InPersonSecurityTitlePass New default value: Host an In Person Signing Session Previous value: Host Signing Node data name: DocuSign_InPersonControl New default value: [[SigningHost]], pass control of the session to [[Signer]]. Previous value: [[SigningHost]]; please give [[Signer]] control of the keyboard and mouse.

31 31 In Person Signing - Request a copy (November) These changes update the text in the dialog when the signer can request a copy be sent to their . Node data name: DocuSign_HeaderStepGetCopy New default value: Request a Copy Previous value: Save your Copy Node data name: DocuSign_InPerson Desc New default value: [[Signer]], enter your to request a copy of the completed document. Select PRINT to print a copy. Previous value: [[Signer]], please enter your address so a copy of the signed document can be sent to you after all people have signed. Node data name: DocuSign_InPerson New default value: Previous value: Address In Person Signing - Pass to the Host (November) These changes update the text on the In Person Signing Session dialog for passing control back to the host. Node data name: DocuSign_InPersonPassToComplete New default value: To complete the signing process, pass control back to [[SigningHost]]. Previous value: To complete the electronic signing process please pass control back to [[SigningHost]]. In Person Signing - Signing Host Login (November) These changes update the text on the In Person Signing Session dialog when the host needs to log in to their account. Node data name: DocuSign_InPersonCompleteSigning New default value: Complete Signing Previous value: Signing Complete

32 32 Node data name: DocuSign_InPersonPassCompleteLogin New default value: [[SigningHost]], log in to your DocuSign account by entering your account password and select continue. Previous value: [[SigningHost]] log in to complete the signing process and confirm receipt. Electronic Notary - Introduction (November) This changes the text on the button to start the notary signing. Node data name: DocuSign_BeginSigning Node description: Start Node default value: Begin Signing Sign On Paper and Signer Attachments Fax Cover Sheet (November) This changes the DocuSign Customer Support contact information shown on the fax cover sheet. Node data name: FaxCover_Support New default value: DocuSign Customer Support: Previous value: DocuSign Customer Support: service@docusign.com Note: If the Signer language is French, the URL used is If the Signer language is Portuguese - Brazil the URL used is For all other languages the new default is used. Signing Welcome - Introduction (October This change adds an option for changing how the signing welcome - introduction header is shown at the start of a signing session. Node data name: DocuSign_SuppressStartDialog Node description: Sets if the Welcome Introduction header, at the top of the browser page when starting the signing experience, is shown or hidden (true = hide). Note that hiding this header also hides the sender profile image, sender information, and message. It will not hide any private messages to the recipient. Node default value: False

33 33 Envelope Unavailable Page (October) This updates the DocuSign Support link shown on the envelope unavailable page. Node data name: DocuSign_General_SupportUrl Node description: The default DocuSign link associated with error messages and other administrative tasks. Node default value: For assistance, please visit our <a href='[[docusign_supporturl]]' target='_ blank' style='[[docusign_supporturl_style]]'>support Center</a>.

34 34 API Updates This section covers new and updated features and functionality delivered in the DocuSign APIs. REST API Supplemental Documents Updates The supplemental documents feature adds three new properties to the Documents resource for envelopes and templates, extends the usage of the Approve tab, and adds a new View tab. These changes set how the documents are displayed, the actions recipients must take, and whether the documents can be downloaded when the envelope is completed. The new Documents resource properties are used in the requests when creating new envelopes or templates, and when adding or updating documents in an envelope or template. The Documents resource properties set whether a document is a supplemental document and the interaction for all recipients. The properties are included in the responses when listing envelope, templates, and document information. The new View tab and Approve tab are used to set the interactions for individual recipients. The View tab includes a required property that requires the recipient to view the supplemental document. If the View tab required property is not set, the recipient can, but is not required, to view the supplemental document. To use the View and Approve tabs for supplemental documents, the Documents resource display property must be set to modal or download. The actions that the recipient must take depend on the combination of the Document resource signermustacknowledge property and whether the recipient is assigned View or Approve tabs on the document. To set the interactions for individual recipients, set the signermustacknowledge property to no_interaction and then add View and Approve tabs on the appropriate document for the recipient. The following table outlines the recipient actions for different signermustacknowledge property and tab combinations (n/a = not applicable): The Document signermustacknowledge property is View tab (required) and the recipient has View tab (not required) Approve tab no_interaction No No No Take no action no_interaction n/a Yes No Take no action no_interaction Yes n/a No View no_interaction n/a Yes Yes Accept no_interaction Yes n/a Yes View and Accept view n/a n/a No View view n/a n/a Yes View and Accept accept n/a Yes n/a Accept accept Yes n/a n/a View and Accept The recipient is required to

35 35 The Document signermustacknowledge property is View tab (required) and the recipient has View tab (not required) Approve tab view_accept n/a n/a n/a View and Accept The recipient is required to The new properties and tabs are defined in the next section, followed by an example update supplemental document JSON request, and generic JSON and XML layouts for the Documents resource with the new properties highlighted. Only View and Approve tabs can be added to supplemental documents. Additionally, all actions for setting supplemental document properties and correcting or changing information for envelopes with supplemental documents can only be done through the Signature REST API. New Document Property Definitions Name Type Description includeindownload Boolean When set to true, the document is included in the combined document download. The default value is true. display String This sets the display and behavior properties of the document during signing. The possible values are: modal: The document is shown as a supplement action strip and can be viewed, downloaded, or printed in a modal window. This is the recommended value for supplemental documents. download: The document is shown as a supplement action strip and can be viewed, downloaded, or printed in a new browser window. inline: This value is not used with supplemental documents, but is the default value for all other documents. The document is shown in the normal signing window. collapsed: This option is not active. collapsible: This option is not active. signermustacknowledge String This sets how the signer interacts with the supplemental document. The possible values are: no_interaction: no recipient action is required. view: The recipient is required to view the document. accept: The recipient is required to accept the document

36 36 Name Type Description Example Update Supplemental Document JSON request by selecting accept during signing, but is not required to view the document. view_accept: The recipient is required to view and accept the document. PUT {envelopeid}/documents { } "documents": [ { "documentid":"1", "name":"infodoc.pdf", "display":"modal", "includeindownload":"true", "signermustacknowledge":"view" } ]

37 37 Documents Generic JSON Layout (with new properties highlighted) "documents": [ { "documentid": "string", "remoteurl": "string", "name": "string", "transformpdffields": "boolean", "fileextension": "string", "matchboxes": [ { "pagenumber": 1, "xposition": 2, "yposition": 3, "width": 4, "height": 5 } ], "order": "string, "pages": "string", "documentfields": [ { "name": "string", "value": "string" } ], "encryptedwithkeymanager": "boolean", "documentbase64": "string", "display": "string", "includeindownload": "boolean", "signermustacknowledge": "string" } ], Documents Generic XML Layout (with new properties highlighted) <documents> <document> <display>string</display> <documentbase64>string</documentbase64> <documentfields> <namevalue> <name>string</name> <value>string</value> </namevalue> </documentfields> <documentid>string</documentid> <encryptedwithkeymanager>boolean</encryptedwithkeymanager> <fileextension>string</fileextension>

38 38 <includeindownload>boolean</includeindownload> <matchboxes> <matchbox> <height>5</height> <pagenumber>1</pagenumber> <width>4</width> <xposition>2</xposition> <yposition>3</yposition> </matchbox> </matchboxes> <name>string</name> <order>string</order> <pages>string</pages> <remoteurl>string</remoteurl> <signermustacknowledge>string</signermustacknowledge> <transformpdffields>string</transformpdffields> </document> </documents> View Tabs A View tab is used with a supplemental document to add a View button to the document for an individual recipient. View Tab Properties Name Reqd? Type Description documentid Yes String This is the document ID number on which the tab is placed. This must refer to an existing Document s ID attribute. pagenumber Yes String This is required and should be set to 1. recipientid Yes String This specifies the recipient associated with the tab. Must refer to an existing recipient s ID attribute. required No Boolean If true, the recipient is required to select the supplemental document View button during signing. tablabel No String The label used for the tab. This can be a maximum of 500 characters. If an empty string is provided for this, an empty string is used. If no value is provided, the tab type is used as the value. templatelocked No Boolean Optional element. Used only when working with template tabs. If true, the attributes of the tab cannot be changed by the sender. templaterequired No Boolean Optional element. Used only when working with template tabs. If true, the tab cannot be removed by the sender. xposition Yes String This is required, but can be 0. yposition Yes String This is required, but can be 0.

39 39 View Tabs Generic JSON Layout "viewtabs": [{ "documentid": "1", "pagenumber": "1", "recipientid": "1", "required": true, "tablabel": "InfoDocView", "templatelocked": false, "templaterequired": false, "xposition": "0", "yposition": "0" }], View Tabs Generic XML Layout <viewtabs> <view> <documentid>1</documentid> <pagenumber>1</pagenumber> <recipientid>1</recipientid> <required>true</required> <tablabel>infodocview</tablabel> <templatelocked>false</templatelocked> <templaterequired>false</templaterequired> <xposition>0</xposition> <yposition>0</yposition> </view> </viewtabs> REST API Electronic Notary In Person Signers Recipient Type Update This update adds the properties to the In Person Signers recipient type needed to use DocuSign electronic notary (enotary) feature when requesting signatures. These properties can be used when creating or updating envelopes, and when creating or updating recipients. The update adds the inpersonsigningtype property, which sets whether the notary functionality is used in the envelope. Additionally, the update adds a notaryhost node that is used to add information for the notary that will host the signing session. It is composed of the recipientid, name, and properties. The following restrictions apply to using electronic notary when sending documents: No other authentication methods can be used when the notary option is used. The Sign On Paper, Document Markup, Field Markup, and Change Signer options cannot be used

40 40 for the documents. Tabs cannot be assigned to the notary. Refer to the electronic notary information on the DocuSign Support Center for more information about how the enotary feature works. Parameters: Following are the properties added to the In Person Signers recipient type needed to use DocuSign electronic notary (enotary) feature when requesting signatures. Name Reqd? Type Description inpersonsigningtype No String Sets whether the envelope uses the enotary feature. There are two accepted values: inpersonsigner = envelope uses the normal in person signing flow. notary = envelope uses the notary in person signing flow. notaryhost No* *Required when inpersonsigningtype=notary Generic JSON layout additions "inpersonsigners": { Sets the information for the notary host for the notary in person signing flow. The following information is required: recipientid = A unique ID number for the notary signing host. name = Specifies the name of the notary signing host. This can be a maximum of 100 characters. = Specifies the for the notary signing host. This can be a maximum of 100 characters.

41 41 { ] "inpersonsigningtype": notary, "notaryhost": " ": "string, "name": "string", "recipientid": "string" ], Response Generic JSON Response layout additions Note: The response returns the property hostrecipientid, which is an integer ID and is the same as InPersonSigner - recipientid. "inpersonsigners": [{ "inpersonsigningtype": "notary", "notaryhost": { "name": "string", " ": "string", "hostrecipientid": "string", "recipientid": "string", "recipientidguid": "string", "status": "string" }, ] REST API Get Envelope Documents, Certificate, and Phone Authentication Files (November) This retrieves a zipped file with the PDF files, containing the combined content of all documents and the certificate, and the.wav files associated with phone authentication for completed envelopes. If the account has the Highlight Data Changes feature enabled, there is an option to request that any changes in the envelope be highlighted. URL: /accounts/{accountid}/envelopes/{envelopeid}/documents/archive Optional additional query string parameter: show_changes={true} Formats: XML, JSON

42 42 HTTP Method: GET Parameters: The only required parameter is the envelope ID. The following optional query string parameter can be added to the request. Name Reqd? Type Description show_changes No Boolean Optional. When set to true, any changed fields for the returned PDF are highlighted in yellow and optional signatures or initials outlined in red. Example Request Body GET {envelopeid}/documents/archive X-DocuSign-Authentication: <DocuSignCredentials><Username> {name}</username><password>{password}</password><integratorkey>{integrator_ key}</integratorkey></docusigncredentials> Accept: application/json Content-Type: application/zip Response The response format is always ZIP and the zipped file contains all the PDFs in an envelope, a PDF version of the Certificate of Completion as a byte stream and the.wav files associated with phone authentication. If show_changes was included, any changed fields are highlighted in the PDF. Note: There is a 24-hour delay in the.wav files associated with phone authentication being added to the envelope document download. REST API accountsettings Update (October) This update exposes additional accountsettings in the REST API v2. The additional settings are described below. These settings are only shown in the response when listing account settings. The settings cannot be changed using the API. They can only be changed by DocuSign. Name Type Description allowsigninggroups Boolean When true, the account can use signing groups. allowprivatesigninggroups Boolean Reserved for DocuSign. This currently returns false in a response. maximumsigninggroups String The maximum number of signing groups an account can have. The default value for this is 50. maximumuserspersigninggroup String The maximum number of members in a signing group.

43 43 Name Type Description The default value for this is 50. Additional REST API accountsettings Updates These additional accountsettings are now available in the REST API v2 and can be set by Admins. Name Type Description disablemobilepushnotifications Boolean When true, mobile push notifications are disabled on the account. useconsumerdisclosure Boolean When true, the account can use supplemental documents. consumerdisclosurefrequency enum Possible values are: Once - Per account, the supplemental document is displayed once only per userid Always - Per envelope, the supplemental document is displayed once only per userid EachAccess - Per envelope, the supplemental document is displayed once only per recipientid

44 44 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 Winter '17 Release Bug Fixes The following bug fixes were deployed to the DocuSign Production environment on December 1, 2016 as part of the DocuSign Winter '17 release. The name-number is the internal DocuSign tracking number for the bug. Items marked with an asterisk (*) were deployed to the DocuSign Production environment as part of an earlier weekly patch. API-5238: Adding recipients with different custom languages to a document created from a template caused an error. API-5303: Shared templates were not limited to the user's templates and those shared with the user. API-5386: Deleting reserved or predefined folders (inbox, draft, sent, etc.) did not return an error. SIGN-8375: Signing and sending an , did not honor resource file settings for languages with 4-letter ISO codes like fr-ca or es-mx. SIGN-9048: In the Save a Copy dialog box in Farsi, the arrow icon didn't appear next to the Terms link. SIGN-9362: A signer would remove an attachment and replace it with another, but the completed envelope still showed the original attachment. SIGN-10058: Documents are now hidden from the screen reader in all browsers until the shroud is dismissed. SIGN-10072: When using an iphone 5 in portrait mode, the decline reason drop down menu was cut off. SIGN-10411: A signer would change the language on an envelope, not sign the envelope, and then send the envelope to another signer. The new signer would get the Envelope Not Found error in English instead of the selected language. SIGN-10656: Removed the ability for users to override default text on some tags. SIGN-11063: In Signing v02, error messages and tips were not wrapping properly. SIGN-11141: Chinese characters in Signing History were not aligning properly. SIGN-11324: The View edisclosure option in the Other Actions drop down was not present for

45 45 some roles. SIGN-11333: Users on mobile were able to use the Back button, which caused a session timeout. SIGN-11434: On IE 11, users were unable to use Microsoft IME to input Japanese characters. SIGN-11549: In Signing V02, secured fields were not hiding values. If the value was prepopulated and the data field was set to locked, when users viewed the envelope, the text was not masked with asterisks. STOR-2625: After migrating to an EU server, admin users in NDSE did not have the option to Go to admin, the Templates tab did not appear, clicking Switch to Classic did not work, and Manage Signers created before the migration did not appear in the account. November Service Pack Bug Fixes The following bug fixes were deployed to the DocuSign DEMO environment on October 21, 2016 as part of the November Service Pack. The name-number is the internal DocuSign tracking number for the bug. Items marked with an asterisk (*) were deployed to the DocuSign Production environment as part of an earlier weekly patch. SIGN-6169: An envelope was not completing correctly when two signers used the same address, but different names, and were signing at the same time. SIGN-7882: Date Signed fields were not correctly showing day or year characters for Chinese, Japanese, or Korean translations. SIGN-9461: When using a browser with cookies disabled to try to sign a PowerForm, the user was not being redirected to the cookies required page. SIGN-10768: During signing, when an unsupported culture or language identifier is used by a browser the system will default to English signing instead of showing an error. DocuSign is currently tracking the instances of this action. SIGN-10842: The Envelope Corrected template was not using the correct recipient language. PLAT-4790: An incorrect error message was being returned for some calls using the SOAP API due to an issue when forwarding SOAP calls to a sister site. WAPP-5933: The account default signing language and sender s membership language were being ignored if a custom resource file was used. WAPP-6117: When Company names that contained a diacritic (accent) mark were displayed in the DocuSign web application the HTML code was shown in place of the correct character. API-4752: Senders were unable to download all documents in a completed envelope when