This section covers new and updated features and functionality delivered in the Classic DocuSign Experience.

Transcription

1 Service Pack Notes Service Pack Notes for November 6, 2015 (updated Nov 13, 2015) This document provides information about the updates deployed to the DocuSign Production environment as part of November 6, 2015 Service Pack. There are five sections in the Service Pack Notes: New Signing Experience Reminder Classic DocuSign Experience Updates API Updates Known Issues Service Pack Bug Fixes These notes have been updated since the service pack was deployed to the DEMO environment with the addition of the Default Mobile Web Interface Update, the SOAP API Template Subject Merge Fields, the known issue REST API Radio Group Tab requireinitialonsharedchange, and the removal of bug fix PLAT Additions to the notes are shown by change bars on the left side of the page. November 13, 2015 Update: The date for the Demo environment transition to the New Signing Experience was changed to November 23, New Signing Experience Reminder Beginning Friday, January 8, 2016, DocuSign will begin transitioning all customers Production accounts to the new signing experience. The previous signing experience will not be available after this date. IMPORTANT: This transition applies to the signing experience only. Customers can continue to use the Classic DocuSign Experience for sending & managing digital agreements beyond this date. On November 23, 2015, the Demo environment will automatically transition to the new signing experience. DocuSign highly encourages you to transition to the new signing experience as soon as possible to give your organization ample time to become familiar with the new signing experience ahead of the sunset date. Classic DocuSign Experience Updates This section covers new and updated features and functionality delivered in the Classic DocuSign Experience. PowerForms Merge Fields This change adds the ability for PowerForm administrators to insert recipient name and address merge fields into the subject line for a PowerForm. 1 Copyright DocuSign, Inc. All rights reserved.

2 After a PowerForm signer enters their name and information on the pre-signing dialog for a PowerForm with the merge fields, the signer information is automatically merged into the appropriate fields in the subject line. For cases where the pre-signing dialog is bypassed (the template used has First Name, Last Name and Address tags or the Full Name and Address tags for the first signer in routing order), the information is merged after the signer completes signing the PowerForm. Both PowerForm senders and signers will see the signer information in the subject line for any s associated with the PowerForm. For PowerForm senders, this provides an easy way to see which signers have completed the PowerForm and to organize their PowerForm s without having to open an envelope. Note: If merging the recipient information into the subject line causes the subject line to exceed 100 characters, then any characters over the 100 character limit are not included in the subject line. For cases where the signer name or is expected to be long, you should consider placing the merge field at the start of the subject. How it Works To use this option the PowerForms administrator adds the merge fields to the Subject to All Recipients field when creating or editing a PowerForm. To add the signer s name in the subject line add the following text in the Subject to All Recipients field: [[<RoleName>_UserName]] Example: [[Signer 1_UserName]] To add the signer s address in the subject line add the following text in the Subject to All Recipients field: [[<RoleName>_ ]] Example: [[Signer 1_ ]] In both cases the <RoleName> is the recipient Role in the template used for the PowerForm. 2 Copyright DocuSign, Inc. All rights reserved.

3 Default Mobile Web Interface Update With the November Service Pack DocuSign has updated the mobile web interface to open with a user s default web interface. So if a user has the New DocuSign Experience set as their default web interface, they will now see the New DocuSign Experience when they log on with a mobile browser too. If a user has the Classic DocuSign Experience as their default web interface, they will continue to see that when they log on with a mobile browser. API Updates This section covers new and updated features and functionality delivered in the DocuSign APIs. REST API Template Subject Merge Fields This change adds the ability to insert recipient name and address merge fields into the subject line for templates created and sent through the REST API. The merge fields, based on the recipient s rolename, are added to the subject when the template is created or when the template is used to create an envelope. After a template sender adds the name and information for the recipient and sends the envelope, the recipient information is automatically merged into the appropriate fields in the subject line. Both the sender and the recipients will see the information in the subject line for any s associated with the template. This provides an easy way for senders to organize their envelope s by subject without having to open an envelope to check the recipient. 3 Copyright DocuSign, Inc. All rights reserved.

4 Note: If merging the recipient information into the subject line causes the subject line to exceed 100 characters, then any characters over the 100 character limit are not included in the subject line. For cases where the recipient name or is expected to be long, you should consider placing the merge field at the start of the subject. To add a recipient s name in the subject line add the following text in the subject when creating the template or when sending an envelope from a template: [[<rolename>_username]] Example: " subject":"[[signer 1_UserName]], Please sign this NDA", To add a recipient s address in the subject line add the following text in the subject when creating the template or when sending an envelope from a template: [[<rolename>_ ]] Example: " subject":"[[signer 1_ ]], Please sign this NDA", In both cases the <rolename> is the recipient s rolename in the template. For cases where another recipient (such as an Agent, Editor, or Intermediary recipient) is entering the name and information for the recipient included in the subject, then [[<rolename>_username]] or [[<rolename>_ ]] is shown in the subject. SOAP API Template Subject Merge Fields This change adds the ability to insert recipient name and address merge fields into the subject line for templates sent through the SOAP API using CreateEnvelopeFromTemplatesAndForms and CreateEnvelopeFromTemplates. The merge fields, based on the recipient s RoleName in the template, are added to the EnvelopeInformation Subject when the template is used to create an envelope. After a template sender adds the name and information for the recipient and sends the envelope, the recipient information is automatically merged into the appropriate fields in the subject line. Both the sender and the recipients will see the information in the subject line for any s associated with the template. This provides an easy way for senders to organize their envelope s by subject without having to open an envelope to check the recipient. Note: If merging the recipient information into the subject line causes the subject line to exceed 100 characters, then any characters over the 100 character limit are not included in the subject line. For cases where the recipient name or is expected to be long, you should consider placing the merge field at the start of the subject. To add a recipient s name in the subject line add the following text in the EnvelopeInformation Subject when sending an envelope from a template: [[<RoleName>_UserName]] Example: <EnvelopeInformation> <Subject>[[Signer 1_UserName]], Please sign this NDA </Subject> </EnvelopeInformation> 4 Copyright DocuSign, Inc. All rights reserved.

5 To add a recipient s address in the subject line add the following text in the EnvelopeInformation Subject when sending an envelope from a template: [[<RoleName>_ ]] Example: <EnvelopeInformation> <Subject>[[Signer 1_ ]], Please sign this NDA </Subject> </EnvelopeInformation> In both cases the <RoleName> is the recipient s RoleName in the template. For cases where another recipient (such as an Agent, Editor, or Intermediary recipient) is entering the name and information for the recipient included in the subject, then [[<RoleName>_UserName]] or [[<RoleName>_ ]] is shown in the subject. REST API Get Account Users Updates This update adds the ability to use optional query parameters to display a subset of users in the account response results and adds new result set information to the response. URL: /accounts/{accountid}/users Optional query parameters: start_position={integer}, count={integer} HTTP method: GET Parameters: There are no required parameters, but the following optional query strings can be added to the request. Name Reqd? Type Description start_position No Integer Starting value for the list. count No Integer Number of records to return. The number must be greater than 1 and less than or equal to 100. Response The response returns the list of users in the account along with the added information about the result set. Name resultsetsize totalsetsize startposition endposition Description Total number users returned in the result set. Total number users in the account. Starting position of the current result set. The last position in the result set. 5 Copyright DocuSign, Inc. All rights reserved.

6 nexturi previousuri Provides the Uri to the next chunk of records based on the request. If the endposition is the entire results of the search, this is null. Provides the Uri to the previous chunk of records based on the request. If this response is the first response for the search, this is null. Known Issues This section covers any known issues 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. REST API Radio Group Tab requireinitialonsharedchange Setting the REST API Radio Group Tab requireinitialonsharedchange property to true does not currently require the signer to initial when they modify a shared Radio Group. DocuSign is working to correct this issue. Until it is corrected, DocuSign recommends using the SOAP API (See the SOAP API Tab information for more) or Classic DocuSign Experience web application to set the initials requirement (See Classic DocuSign Experience help - Enabling Field Markup for more information). Service Pack Bug Fixes This document provides information about the updates deployed to the DocuSign Production environment as part of November 6, 2015 Service Pack. The name-number is the internal DocuSign tracking number for the bug. Important: Issue numbers that are bold underlined text are externally reported bugs or customer commitments that were fixed in the Service Pack. WAPP-5158: When using the Classic DocuSign Experience to edit the text in a multi-line a Data Field tag, line breaks were not being preserved in the signing experience. WAPP-5513: If a brand profile name contained a special character (such as &) the special characters were replaced by their XML numerical values when brand profile name was viewed in the Classic DocuSign Experience. WAPP-5639: When using the Classic DocuSign Experience to send from a template with multiple documents, when a document is replaced the document did not follow the correct order and could not be changed. This issue is related to API Copyright DocuSign, Inc. All rights reserved.

7 WAPP-5675: When using the Classic DocuSign Experience to correct an envelope the error message "Envelope Not Accessible Envelope has been digitally signed." was appearing even though no digital signature was applied to the envelope. WAPP-5684: When using the Classic DocuSign Experience to download completed envelope documents as Separate PDFs only first page of first document was downloaded. SIGN-2618: During free-form signing when the signer placed a date signed field the time zone shown was not the time zone set by the sending account. This issue is related to SIGN SIGN-5114: When using the New Signing Experience on a mobile browser the text format for customized signing resource files was not properly displayed. SIGN-6218: The Print option was not available when using the New Signing Experience on a Safari mobile browser. SIGN-6289: Improved the PDF display and legibility properties for signatures that were created on mobile devices using the draw signature option. SIGN-7172: Signers could not complete signing after adopting a signature for documents where 21 CFR Part 11 was enabled when using the New Signing Experience on a mobile browser. SIGN-7188: Signers required to sign with an ICP Brasil digital signature were getting an error message during signing if there was a Receive a Copy recipient in the routing order before the signer. SIGN-7191: Some text in the DocuSign template was not being localized for documents that required an OpenTrust digital signature. SIGN-7483: When using the Sign a Document Now feature and sending the document to another address, a DocuSign Ink 1.0 promo was being appended to PDF. SIGN-7516: When Sign in for Each Location was enabled in envelopes for accounts with single sign on enabled the signer was being required to log on twice. SIGN-7520: The text for the Adopt Signature agreement was not appearing when drawing a signature using the New Signing Experience on a mobile web browser for signers that had previously signed documents. SIGN-7535: Signers that are required to sign with an ICP Brasil digital signature received an error after entering their credentials and could not complete signing. SIGN-7536: For envelopes with multiple signers where at least one signer was required to apply a digital signature and an electronic signature, the signer was receiving the invitation to sign in the incorrect routing order. SIGN-7537: For signers with DocuSign accounts, after completing a document that requires a digital signature if the signer selected to open the next document to sign, the system opened the document that had just been completed. SIGN-7539: During embedded signing the time zone for date signed fields set by the sending account was changing to the Pacific time zone if the sending account did not allow account members to set their own time zones. This is related to SIGN-7641 and SIGN SIGN-7562: When completing the signing process for with payment processing enabled, signer entered information was not being validated until after the payment was completed. SIGN-7590: For custom branding signing resource files, the Suppress Select Signature setting was not being followed. 7 Copyright DocuSign, Inc. All rights reserved.

8 SIGN-7592: Some Hungarian translations in the New Signing Experience were incorrect. SIGN-7596: For custom branding signing resource files, the Hide Sender Profile Information setting was not being followed for signing from mobile browsers. SIGN-7641: During embedded signing in a non-english language the date signed field would switch from the selected language to English. This issue is related to SIGN-7539 SIGN-7662: A signer that was a member of an account with Single Sign On enabled was prompted to log on to DocuSign after completing signing. SIGN-7672: After completing the signing process some Address Recipients recipients were inadvertently shown an authentication message. SIGN-7829: Some Hungarian translations on the signing Access Code page were incorrect. CONNECT-244: After setting up a Connect configuration for a DocuSign for Salesforce account in the new Admin web application, document information was not correctly sent to the Salesforce account. PLAT-3933: When using the Classic DocuSign Experience to send an envelope where two templates were applied to different documents, fields from one template were appearing on multiple documents after the envelope was completed. PLAT-4034: When using the Classic DocuSign Experience to view information for an envelope that used Any Signer functionality, the Summary section does not show any information. API-2025: When using the REST API to requesting information about recipient tabs, positive anchor Y Offset was returned as a negative value. API-2551: When trying to correct an envelope by replacing documents, page numbers were duplicated and tags were not placed in the correct positions. API-2590: When using the SOAP API to create envelopes from a template with document visibility enabled, the envelope could not be sent due to a document visibility error. 8 Copyright DocuSign, Inc. All rights reserved.