Release Notes Updated April 25, 2014 Release Notes for DocuSign Spring 14 Release On March 11th, as part of the DocuSign Spring 14 Release, DocuSign will deliver extended and new signing configuration options and signing performance improvements, along with additional API options. Note: The list of features, descriptions, and other release information are updated on a regular basis until the actual release date. Be sure to check the full release notes link DocuSign web site Upcoming Release page for updates. Changes to the release notes since the previous version are shown by a change bar on the left side of the page. Key Features: Feature Name Used through: Web API console Contact DocuSign to enable? Must also be enabled in customer console? Requires changes to API to use? New Signing Configuration Options X X Yes Yes* Yes* Print In-Process Documents X No No No Save-As-You-Go Signing X No No No Signing Performance Optimization X X No No No Terminology Updates X No No No Enabling the New DocuSign X No Yes N/A Experience for your Account DocuSign Mobile App Updates No N/A N/A DocuSign for Salesforce 5.0 No N/A N/A DocuSign for Google Drive 2.6 No N/A N/A DocuSign for Google Apps 2.0 No N/A N/A DocuSign Apps for Microsoft No N/A N/A Office 365 Carrier Grade Architecture No N/A N/A DocuSign Security Appliance X 1 X Yes Yes Yes * Some Signing Configuration Options are set in the console and some are only enabled through the API. See the Signing Configuration Options for more information. 1 The DocuSign Security Appliance is configured in the console. For more information about all the API changes for this release, refer to the API Changes section. For the list of the bug fixes since the DocuSign Winter 14 release, refer to the January, February, and March service pack and bug fix information section. 1 Copyright 2009-2014 DocuSign, Inc. All rights reserved.
Feature Descriptions: New Signing Configuration Options In this release you will see new signing configuration options that provide greater flexibility during the signing experience. All of these options are included in DocuSign Enterprise and DocuSign System Automated (SA) Premium plans, but customers must contact DocuSign to enable them for their accounts. These options include ability to: Allow signers that do not have DocuSign account to upload signature and initials from files. When this option is enabled for your account, signers can upload their signature and initials images instead of using a pre-formatted signature style or the drawing option. Note: The signer must already have existing files with their signature and initials to use this option. DocuSign does not let the signer generate the signature/initial file during the upload. When adopting signatures or initials, the signer selects Upload (this can be set as the default starting point), clicks Upload Your Signature (or Initials), and selects their signature or initials file. The selected file is shown in the Preview field. If the signer selected the incorrect file, they can just click Upload Your Signature (or Initials) and select a new file. If the file is correct, the signer clicks Adopt and Sign to complete the signature adoption. The file upload supports common image files (.jpg,.png,.tiff) with a maximum file size of 3MB. For the best results DocuSign recommends using an image of 400 x 145 pixels for signatures and 150 x 145 pixels for initials. This option is set up through the web app in the Preferences Features Signature Adoption Configuration page. From here you can select the default mode when a signer is adopting their signature or initials after clicking a Signature or Initial tab. Selecting Start on upload shows the 2 Copyright 2009-2014 DocuSign, Inc. All rights reserved.
upload mode. If you do not want signers to be able to upload signatures and initials, you can disable the option from this page. Upload signature settings Require certain signers on an envelope to sign on paper (to support jurisdictions that don t recognize electronic signature). When this option is enabled for a signer, the signer must print, sign, and upload or fax the signed documents to DocuSign. This option is only available for envelopes sent through the DocuSign REST API. It cannot be used through the web console. See the API Changes section for more information on the REST API changes for this option. Enable an Optional tag property for Signer Attachments. This allows the sender to provide the option for signers to attach a file to an envelope. When this option is enabled, signers can, but are not required to, upload or fax supporting documents during the signing process. The process for uploading or faxing documents follows the existing process of requesting documents from signers. This option is only available for envelopes sent through both REST and SOAP APIs. It cannot be used through the web console. See the API Changes section for more information on the API changes for this option. Print In-Process Documents This function allows signers and senders to print or download the contents of an in-process envelope showing all data and fields that have been filled-in by signers, with the exception of signatures and initials. Signatures and initials are only added to the documents when the signer completes the envelope. For accounts that have the Watermark option enabled, the account watermark still appears on inprocess documents. This change is included in all DocuSign plans. 3 Copyright 2009-2014 DocuSign, Inc. All rights reserved.
Save-As-You-Go Signing This new function periodically saves the information a signer is entering in the envelope. If the signer exits the envelope or the signing session times-out, all the information entered by the signer is saved and the signer does not have to re-enter the information when they return to complete the envelope. Note: Signatures and initials are only saved if the signer has a DocuSign account and is logged on to their account. This change is included in all DocuSign plans. Signing Performance Optimization We have made significant enhancements to make the signing experience faster. Additionally, we have removed cookies from our embedded signing experience, improving the performance of this feature in all supported browsers. This change is included in all DocuSign plans. Terminology Updates As part of the Spring 14 Release, DocuSign is updating some of the terminology relating to the disclosure designations. In general, the term Consumer Disclosure is being replaced with Electronic Record and Signature Disclosure throughout DocuSign. Important: The terminology changes do not change information in your current disclosure or require your recipients to agree to a new disclosure. Recipients will see the terminology changes on the Welcome screen for web and mobile signing. 4 Copyright 2009-2014 DocuSign, Inc. All rights reserved.
DocuSign customer administrators will see the terminology changes in the Preferences - Electronic Record and Signature Disclosure section (formerly Consumer Disclosure), in the Preferences Features section and in the Certificate of Completion. Enabling the New DocuSign Experience for Your Account Users DocuSign is excited to announce the launch of the New DocuSign Experience for sending. You can red more about it on New Experience page. With the launch of the New DocuSign Experience, DocuSign is providing customer administrators with the option of allowing their users to access the new experience. This option can be set on the account, group, and user level. To set the access option for your account, go to the Classic DocuSign Experience and select Preferences Features and select the access option. Use the New DocuSign Experience (List) This controls whether access to the New DocuSign Experience. The three options are: No: Users will not have access to the New DocuSign Experience. Optional User can opt in: Users have the option to use the New DocuSign Experience or the Classic DocuSign Experience and can switch between the two options. Yes: Users are required to use the New DocuSign Experience. Note: If Yes is selected, users that have Manage Account access are still able to switch between the two options. The setting will take effect the next time a user logs on to DocuSign. 5 Copyright 2009-2014 DocuSign, Inc. All rights reserved.
If you selected the Optional User can opt in or Yes access options, you can also set the access options for specific Permission Profiles, Groups, and Users. Setting Access for Permission Profiles, Groups, and Users To change access to the New DocuSign Experience for a Permission Profile: 1. From the Classic DocuSign Experience and select Preferences Permission Profiles. 2. Select the Permission Profile you want modify. 3. Select the Use the New DocuSign Experience option for the Permission Profile. 4. Click Save to save the change. 5. Repeat steps 2 4 for any other Permission Profiles. To change access to the New DocuSign Experience for a Group: Note: If your account uses Permission Profiles, DocuSign recommends that you use Permission Profiles to set group and user permissions. 1. From the Classic DocuSign Experience and select Preferences Groups. 2. Select the Group you want modify. 3. Click the Permissions tab. 4. Select the Use the New DocuSign Experience option for the Group. 6 Copyright 2009-2014 DocuSign, Inc. All rights reserved.
5. Click Save Changes to save the changes for the Group. To change access to the New DocuSign Experience for a single User: Note: If your account uses Permission Profiles, DocuSign recommends that you use Permission Profiles to set user permissions. 1. From the Classic DocuSign Experience and select Preferences Users. 2. Click Open for the User you want modify. 3. Click the Permissions tab. 4. Select the Access to the New DocuSign Experience for the Permission Profile. 5. Click Save to save the changes for the User. Switching between the New DocuSign Experience and Classic DocuSign Experience. If you have selected to allow your users to opt in to using the New DocuSign Experience, your users can seamlessly move between the New DocuSign Experience and the Classic Experience. To switch to the New DocuSign Experience, users simply click the SWITCH TO NEW button in the top right of the Classic DocuSign Experience. To go back to the Classic DocuSign Experience, users can click SWITCH TO CLASSIC in the upper right portion of the New DocuSign Experience Home page. DocuSign Mobile App Updates We will be renaming DocuSign Ink to DocuSign. Our new Windows Phone app has already adopted this change, and you ll see updates for Windows 8, ios, and Android throughout the Spring. These changes will automatically occur as part of the standard app upgrade process for ios, Android, and Windows Phone. Once upgraded, you will notice a new app icon along with branding updates within the app. 7 Copyright 2009-2014 DocuSign, Inc. All rights reserved.
DocuSign for ios A number of usability enhancements are planned for the ios app, including a revised home screen, improved document status and the addition of Badges. Freemium and Trial users will be able to upgrade to Individual or Professional plans within the app using the itunes payment subscription service. The app will be localized into 11 languages. In addition to English, the new app will support Dutch, German, French, Italian, Japanese, Korean, Portuguese (Brazilian), Russian, Simplified Chinese, and Spanish (Catalan). The estimated availability for the next version of DocuSign for ios is April. DocuSign for Windows 8 and Windows Phone Both apps will receive template support, document tagging, cloud storage support, continued design updates, as well as localization into 22 languages. Templates must still be created in the Web console or API. The estimated availability for DocuSign for Windows 8 and Windows Phone is March. DocuSign for Android The Android app recently released support for templates (note that templates must still be created in the Web console or API). The app will continue to see major upgrades, including the addition document tagging, push notifications, and a design update. The estimated availability for the next version of DocuSign for Android is April. DocuSign for Salesforce 5.0 DocuSign for Salesforce 5.0: This release will add support for Salesforce1, Salesforce s new Customer Platform. DocuSign for Salesforce 5.0 is available now. DocuSign for Google Drive 2.6 This release adds the ability to easily and quickly sign & return documents. Estimated availability is March. DocuSign for Google Apps 2.0 This release adds support for OAuth2 and will allow Google Apps administrators to easily install DocuSign for Google Drive domain-wide. Estimated availability is March. DocuSign Apps for Microsoft Office 365 Throughout Spring DocuSign will be expanding our offerings for Microsoft products by adding the following integrations: DocuSign for Microsoft Word: DocuSign for Microsoft Word allows users to send or sign documents created or edited in Word 2013. Additionally, DocuSign-enabled templates will be published on the Office.com template store, so that users can open, edit, and send pre-tagged templates using the Microsoft Word 2013 application. The estimated availability for DocuSign for Microsoft Word is March. 8 Copyright 2009-2014 DocuSign, Inc. All rights reserved.
DocuSign for Outlook DocuSign s integration with Microsoft Outlook allows users to sign and return email attachments through the Outlook. Signed attachments can be saved locally or to OneDrive. The estimated availability for DocuSign for Microsoft Outlook is March. DocuSign for SharePoint Online The DocuSign for SharePoint Online application supports sending one or more documents out for signature from SharePoint Online. Users can also track the status of documents and signed document are automatically saved back to SharePoint Online. The estimated availability for DocuSign for SharePoint Online is March. Carrier Grade Architecture Knowing that customers rely on DocuSign for their mission-critical business processes and transactions, we have invested in redesigning our system architecture from the ground-up to be continuously available. While DocuSign has historically been the leader in SaaS for system availability, DocuSign s Carrier Grade Architecture takes availability to the next level. Each DocuSign instance in this new architecture is comprised of three simultaneously active DocuSign systems in three different geographic locations, each supporting customer transactions while staying synchronized with each other. Customer data are saved up to nine times across our three geographic locations, providing a superior level of protection against data loss or corruption. This architecture results in zero planned downtime for maintenance, near-zero data loss in disaster scenarios, and incredibly resilient system performance even during peak traffic or full site loss. Most importantly, it ensures that DocuSign will be available when customers need it most. Visit www.docusign.com/how-it-works/availability for more information. DocuSign Security Appliance The DocuSign Security Appliance is customer controlled, on premise software solution that allows customers to manage the encryption/decryption of their DocuSign documents independent of DocuSign. The DocuSign Security Appliance is a self-managing appliance designed to address the most sensitive scenarios, where the highest level of security is required. The DocuSign Security Appliance offloads the key storage and release policies from the DocuSign cloud into a customer s private network. This feature can be used in conjunction with the DocuSign REST API. Click here for more information on the API changes for this option. The DocuSign Security Appliance is only available to DocuSign Platform plans. How it works During sending, when the customer prepares an envelope through the web or API, the DocuSign service contacts the customer s Security Appliance to request encryption keys as needed. DocuSign uses the keys to encrypt the documents in the envelope before they are stored and sent by DocuSign. When a recipient opens an envelope with encrypted documents, DocuSign sends a key request containing relevant context information, such as identity, transaction ID, and timestamps to the customer s DocuSign Security Appliance. The Security Appliance makes a policy decision based on the context information to release the keys. DocuSign uses the keys to decrypt the documents in the envelope and displays the documents to the recipient allowing the recipient to sign them normally. This process allows the customer to retain control over the documents sent through DocuSign. 9 Copyright 2009-2014 DocuSign, Inc. All rights reserved.
API Changes for the DocuSign Spring 14 Release This section provides addition information on the API changes to implement the features in the DocuSign Spring 14 Release. The following table shows a list of the features in the release that impact the DocuSign SOAP and REST APIs. Feature Name DocuSign API change? Yes No Customer API change required if feature is not used? New Signing Configuration Options X No Envelope Override Options X No Requiring Signer Certificates X No DocuSign Security Appliance X No New Signing Configuration Options In this release you will see new signing configuration options that provide greater flexibility during the signing experience. These options include ability to: Require Recipient Sign On Paper (REST only) This change adds support to require a signer to use a wet signature (the signer must print, sign, and upload or fax the signed documents to DocuSign). This option cannot be used through the web console. This change adds a requiresignonpaper node to the In Person Signers and Signers Recipient types. When this is set to true, the signer must print, sign, and upload or fax the signed documents to DocuSign. This information can be used with recipients in templates. Additionally, this change adds the new accountsetting called enablerequiresignonpaper. When this option is set to true the option to require recipients to sign on paper is available to the account. When getting account settings, the response returns enablerequiresignonpaper, which indicates if the option is turned on (true) or off (false), and enablerequiresignonpaperrights, which indicates if the requesting user has permission to modify the enablerequiresignonpaper setting (editable) or not (read_only). The enablerequiresignonpaper option can be editing using PUT /accounts/{accountid}/settings. Enable Optional Signer Attachments (available for REST in March and for SOAP in April) This change allows Signer Attachment tags to be optional. When an optional signer attachment tags is used, signers can, but are not required to, upload or fax supporting documents during the signing process. The process for uploading or faxing documents follows the existing process of requesting documents from signers. This option cannot be used through the web console. REST For the REST API this change adds an optional node to signerattachmenttab. When this is set to true, the signerattachmenttab is optional and not required to complete the envelope. Note: This change will also automatically transform PDF text fields in the uploaded PDF file to optional signer attachment tags if the text field name property contains DocuSignSignerAttachmentOptional or esignsignerattachmentoptional and transformpdffields is set to true. 10 Copyright 2009-2014 DocuSign, Inc. All rights reserved.
Envelope Override Options (REST and SOAP) This change adds support for optional envelope level overrides. The options allow setting the Reply To information (email address and name), adding BCC email addresses, and suppressing the consumer disclosure. Reply To Override (available for SOAP in March and for REST in April) Using this option overrides the Reply To information in the emails sent to recipients. For the SOAP API this change adds a new EmailSettings object that contains two strings (ReplyEmailAddressOverride and ReplyEmailNameOverride) to the Envelope section for CreateEnvelope and CreateAndSendEnvelope, and to the EnvelopeInformation section for CreateEnvelopeFromTemplate and CreateEnvelopeFromTemplatesAndForms. Important: The Reply To override information is not returned in the responses for these calls and the RequestEnvelope call. The EmailSettings object strings have the following characteristics: ReplyEmailAddressOverride: The Reply To email used for the envelope. DocuSign will verify a correct email format is used, but does not verify that the email is active. This can be a maximum of 100 characters. ReplyEmailNameOverride: The name associated with the Reply To email address. This can be a maximum of 100 characters. Example Reply To Override XML [ SNIP] <Envelope> <EmailSettings> <ReplyEmailAddressOverride>string</ReplyEmailAddressOverride> <ReplyEmailNameOverride>string</ReplyEmailNameOverride> <BCCEmailAddresses> <Email/> <Email/> </BCCEmailAddresses> </EmailSettings> [SNIP] BCC Email Override (available for SOAP in March and for REST in April) Using this option adds up to five BCC email addresses to an envelope. Using this also overrides the BCC for Email Archive information set through the web console for the envelope. Example: if your account has BCC for Email Archive set up for the email address archive@mycompany.com and you send an envelope using the BCC Email Override to send a BCC email to salesarchive@mycompany.com, then a copy of the envelope is only sent to the salesarchive@mycompany.com email address. For the SOAP API this change adds a new EmailSettings object that contains a BCCEmailAddresses object that can contain up to five Email strings to the Envelope section for CreateEnvelope and CreateAndSendEnvelope, and to the EnvelopeInformation section for CreateEnvelopeFromTemplate and CreateEnvelopeFromTemplatesAndForms. Important: The BCCEmailAddresses information is not returned in the responses for these calls and the RequestEnvelope call. 11 Copyright 2009-2014 DocuSign, Inc. All rights reserved.
The BCCEmailAddresses object string has the following characteristics: Email: An email address the envelope. DocuSign verifies that the email format is correct, but does not verify that the email is active. This can be a maximum of 100 characters. Example BCC Override XML [ SNIP] <Envelope> <EmailSettings> <ReplyEmailAddressOverride>string</ReplyEmailAddressOverride> <ReplyEmailNameOverride>string</ReplyEmailNameOverride> <BCCEmailAddresses> <Email/> <Email/> </BCCEmailAddresses> </EmailSettings> [SNIP] Consumer Disclosure Override (available for REST in March and for SOAP in April) Using this option will override the account s consumer disclosure setting on an envelope by envelope basis. For the REST API this change adds a new usedisclosure node to the envelope. When this is set to false, the consumer disclosure is not shown to any envelope recipients. If this is set to true, the consumer disclosure is shown to recipients in accordance with the account s Consumer Disclosure Frequency setting. If there is no setting for use usedisclosure, then the account s normal consumer disclosure setting is used and the usedisclosure setting is not returned in responses when getting envelope information. Requiring Signer Certificates (REST and SOAP) This change adds support for requiring recipient signer certificates when sending an envelope using DocuSign s REST or SOAP API. This change became available with the January 13, 2014 Service Pack. REST This change adds a requiresignercertificate node to the In Person Signers and Signers Recipient types. This is used to set the type of signer certificate required for signing. Only one type of certificate can be set for a signer. If left blank, no certificate is required. The possible values are docusign_express (meaning a DocuSign Express signature is required) and safe (meaning a SAFE-BioPharma certificate is required). SOAP This change adds a RequireSignerCertificate node to the Recipient structure. This is used to set the type of signer certificate required for signing. Only one type of certificate can be set for a signer. If left blank, no certificate is required. The possible values are DocusignExpress (meaning a DocuSign Express signature is required) and Safe (meaning a SAFE-BioPharma certificate is required). DocuSign Security Appliance (REST only) This change adds support for using documents encrypted with the DocuSign Security Appliance. This change adds the following to the Documents parameter. encryptedwithkeymanager A Boolean setting. If true, the document is encrypted by the sender for use with the DocuSign Security Appliance. 12 Copyright 2009-2014 DocuSign, Inc. All rights reserved.
Note: If the document is encrypted, the Document name parameter must contain the unencrypted name of the document. 13 Copyright 2009-2014 DocuSign, Inc. All rights reserved.
Service Pack Notes January 13, 2014 The following bug fixes were completed for the January 13, 2014 service pack. The name-number is the internal DocuSign tracking number for the bug. WAPP-2342: Corrected an issue where signatures were present on a document, but were not visible in the downloaded version of the completed envelope. WAPP-2396: Corrected an issue where password protected PDF's were causing errors with SAFE-BioPharma certificates. WAPP-2441: Updated email files to improve spacing in emails displayed in Yahoo mail. WAPP-2445: Updated email files to improve button location (centering buttons) in emails. WAPP-2691: Corrected an issue where a different time zone was shown in an Envelope Report when the report was exported to a csv file. WAPP-2693: Corrected an issue where a customer could not save the Social ID settings. WAPP-2729: Migrated SSO 1.1 to full.net 4.5 using System.IdenityModel to deal with a null HttpContext.Current.User.Identity.Name value. WAPP-2848: Corrected a system error when using SAFE-BioPharma certificates. WAPP-2863: Corrected misspellings in the Branding Signing Resource file. WAPP-2895: Corrected an issue where the sender was not receiving failed authentication email notifications due to a setting in the Brand profile. WAPP-2973: Corrected an issue where a merge field in the Consumer Disclosure was not populating correctly in the consumer disclosure that appears in the Certificate of Completion. WAPP-3011: Changed the CSS font family for Helvetica to match the font family used in Internet Explorer when signing. WAPP-3016: Corrected an issue where a completed notary PDF showed an invalid certificate when viewed with Adobe Reader or Acrobat. WAPP-3043: Corrected a Reporting issue where a time zone change caused an error with the report start date. WAPP-3060: Corrected an issue where emails sent to Gmail had their content stripped. WAPP-3065: Corrected an issue where a PowerForms user could use direct PowerForms when direct PowerForms was not enabled for the user. WAPP-3066: Corrected an issue where the last authentication method on a user's ID card did not update when a digital certificate was completed. WAPP-3081: Corrected an issue where an Applied action did not appear in the history for an envelope signed with a SAFE-BioPharma certificate. WAPP-3094: Corrected an issue where a customer s Single Sign On (SSO) required an extra click to initiate. WAPP-3118: Corrected a digital signature issue where the new signer could not complete signer after changing the signer. WAPP-3149: Corrected Phone Authentication error dialog box function when recipient hangs up the telephone before verification or does not enter appropriate code. WAPP-3203: Corrected the button and description text for the Single Sign On (SSO) login page. WAPP-3242: Corrected an issue where the incorrect time values were used on a user s ID card for last authentication method. 14 Copyright 2009-2014 DocuSign, Inc. All rights reserved.
SIGN-1: Corrected a signing issue for Window8 mobile where lines did not appear when drawing initials. SIGN-3: Corrected a signing issue where signers could not add multiple attachments when signing on an ipad. SIGN-21: Corrected a signing issue where the text box would move out of view when trying to enter text while freeform signing on an ipad. SIGN-31: Corrected a signing issue where repeatedly clicking on a signature or initials tag caused the tag to move up and left on the document. SIGN-145: Corrected a signing issue for the Chrome browser where when zoomed 110%, signers could not enter characters in a multi-line data field. SIGN-148: Corrected a signing issue where the signer could not collapse a not tag to view content when signing on an ipad with ios6 and ios7. SIGN-468: Corrected an issue where some branding color settings were not saved correctly when creating a new brand profile. SIGN-498: Corrected a signing issue where repeatedly clicking on a signature or initials tag caused the tag to move up when signing on a device with ios6 and ios7. SIGN-524: Corrected a signing issue where the header bar (to click on 'Start' or 'Finish') did not appear when signing on the Chrome browser on an ipad. SIGN-528: Corrected a signing issue with accessibility where pressing Enter to sign an optional signature tag caused a previously signed optional signature tag to become unsigned. SIGN-599: Corrected a signing issue where there was no way to close a certified delivery envelope. SIGN-1443: Corrected a signing issue where browsers with Italian set as the primary language were unable to authenticate using access code from a PowerForm email. SIGN-1457: Corrected a signing issue where adopting a drawn signature when signing from a PowerForm using a mobile device resulted in error. SIGN-1462: Corrected a signing issue where the correct Finish Later landing page was not being displayed for envelopes that did not have a brand set. SIGN-1486: Corrected a signing issue where pressing Enter after typing an Access Code used two access code attempts. SIGN-1529: Corrected a signing issue where the upload attachment button graphic was not updated. SIGN-1531: Changed how Optional Signature and Optional Initials tags are displayed. SIGN-1566: Corrected a signing issue where the Continue button was not working for the ID Check pages when the browser language is set to French. SIGN-1567: Corrected errors on the in-person signing welcome dialog when the browser language is set to French. SIGN-1568: Corrected a signing issue where the Access Code Validate button did not function correctly when the browser language is set to French. SIGN-1587: Corrected an issue where the footer links were missing from the signing view in Internet Explorer. SIGN-1603: Updated spinner image when uploading attachments. SIGN-1610: Corrected a signing issue with accessibility where a blue/yellow box appeared around the top menu bar during signing. 15 Copyright 2009-2014 DocuSign, Inc. All rights reserved.
SIGN-1641: Corrected a signing issue where the label for the zoom control in the menu bar did not appear when signing using the Firefox browser. SIGN-1646: Corrected a signing issue where signers were unable to complete the signing process using Internet Explorer 9.0. SIGN-1727: Updated the copyright year in the web console footer. SIGN-1739: Corrected an issue in the DEMO environment where some accounts could not selfsign an envelope when using a mobile device. SIGN-1747: Corrected an issue where when using a signature pad and Internet Explorer 7 with the sign in each location setting the signing session did not continue after the first signature was drawn. PLAT-274: Corrected a REST API issue where tags were shifting location when sending with composite templates. PLAT-552: Corrected an issue where a wide format Excel spreadsheet did not display correctly during signing. PLAT-667: Corrected an issue where the background box for the envelope ID was not appearing correctly and was obscuring part of the document when the document was rotated. PLAT-761: Corrected a REST API issue where radio button group names were being truncated if name included an underscore. PLAT-764: Corrected an issue with mobile offline signing where the acceptance time for the Consumer Disclosure shown in the Certificate of Completion was defaulting to the time the envelope was synchronized with DocuSign. PLAT-785: Corrected a SOAP API issue where envelope custom fields were not being returned correctly in the CreateEnvelopeFromTemplates response for a DSPro template. PLAT-791: Corrected an issue where a user was unable to edit shared template in the console or with the API and could not download template document through the API. PLAT-876: Corrected a REST API issue where using POST to create radio tabs created a duplicate tab for all recipients. PLAT-905: Corrected a REST API issue where GET Templates did not return the signer name for in-person signer recipients. PLAT-906: Corrected a REST API issue where GET Template with ID did not return the host name and email for in-person signer recipients. PLAT-910: Corrected a REST API issue where in a template the host name was being returned as the signer name for in-person signer recipients. PLAT-924: Corrected REST API issue where PUT a recipient's signature/initials images for inperson signers caused a blank signature display in the recipient view. PLAT-925: Corrected REST API issue where GET signature for in-person signers caused a 404 error. PLAT-935: Updated REST API POST Recipient View with additional authentication assertion parameters (assertionid, authenticationinstant, and securitydomain) to match similar SOAP call. PLAT-945: Corrected an issue in the DEMO environment where SOAP API CreateEnvelopeFromTemplates was giving an envelope synch error. PLAT-946: Corrected an issue in the DEMO environment where SOAP API CreateEnvelopeFromTempates was giving an object reference not found error. 16 Copyright 2009-2014 DocuSign, Inc. All rights reserved.
PLAT-947: Corrected an email issue where the personal note header is shown in the activation email for non-english-language signers when no note was added by sender. PLAT-960: Expanded the Date Signed Formatting Options by adding an option for dd-mmmyyyy (example: 10-JAN-2014). PLAT-966: Corrected a SOAP API issue where an exception was thrown for RequestStatuses calls with empty envelope IDs. PLAT-985: Corrected issues with REST API v2 composite templates. PLAT-1045: Added paymentmethod to the response for GET /accounts/:accountid/billing_plan. PLAT-1046: Corrected a mobile/rest API issue where an in-person signer recipient s signature was being added to signing host's account. PLAT-1058: Corrected an issue where the tamper seal was not being applied to PDFs when the PDF was being retrieved through DocuSign Correct for Salesforce. PLAT-1122: Corrected a SOAP API issue in the DEMO environment where CreateEnvelopeFromTemplates was giving a "Signer certificate type not supported" error when using a newly created server template. 17 Copyright 2009-2014 DocuSign, Inc. All rights reserved.
Service Pack Notes February 12, 2014 The following bug fixes were completed for the February 12, 2014 service pack. The name-number is the internal DocuSign tracking number for the bug. WAPP-2674: Corrected an issue in the DEMO environment where drop-downs fields were expanding. WAPP-2771: Corrected an API issue where when sending to multiple recipients with placeholder names the placeholder names were not being updated for subsequent recipients after the first recipient adds information and the envelope was corrected. WAPP-3013: Corrected an email issue where in the Sender Envelope Declined email, the sender name was not appearing. This issue only occurred for envelopes with multiple signers, when the first signer declines the envelope. WAPP-3026: Corrected an issue where the HTML formatting for a scheduled reports email was being stripped out in some versions of Outlook. WAPP-3083: Updated rules for how email message and subject information is handled with locked templates. When senders add or apply a template to an envelope and the template has a locked email subject and message, that subject and message is used for the envelope and cannot be changed even if another locked template is subsequently added or applied to the envelope. If the sender has entered an email subject or message before adding or applying a locked template, the sender will receive a warning that the email subject and message will be overwritten with the email subject and message from the locked template. WAPP-3137: Added additional information for the Account Suspended warning message. WAPP-3173: Corrected an issue where using the PowerForm option to download a copy after completing the PowerForm resulted in an error. WAPP-3230: Corrected an issue where using the Branding Signing Resource File to suppress sender information in the signing experience introduction also suppressed the list of documents to sign. WAPP-3260: Corrected an issue where the forgotten password question merge field text appeared in forgotten password emails for accounts that did not require a forgotten password question. WAPP-3503: Corrected an issue where the Status Date in the envelope history was using an inaccurate value. WAPP-3505: Corrected an issue in the DEMO environment where carriage returns and some spacing items entered in email messages and personal notes were not preserved when the email was generated for the recipient. SIGN-1544: Improved accessibility navigation for documents that do not have reading zones applied. SIGN-1780: Corrected an issue where Internet Explorer 11 was not recognizing the Topaz signature pad. SIGN-1812: Corrected an issue in the Android v2.3 mobile app where tag images were not displaying correctly. SIGN-1840: Corrected a mobile app signing issue where focus was locked in a text field when trying to sign a PDF with form fields. 18 Copyright 2009-2014 DocuSign, Inc. All rights reserved.
DSP-944: Improved image quality for DocuSign Express logo for recipient signature and in summary. DSP-949: Improved ability to select DocuSign Express logo when signature size is less than 65% of normal. DSP-994: Updated digital signature text for the Authorized and Applied events in the envelope history. DSP-1042: Updated DocuSign Express process by adding link to the Subscribers Agreement and a checkbox to show signer acceptance of the agreement. PLAT-347: Updated error message information when invalid recipientid is used for an offline signer. PLAT-355: Updated error message information when email is omitted for an offline signer. PLAT-689: Corrected an issue where user emails were be directed to the wrong user ID after the user had been removed from the account (by changing user name and email) and then added back to the account. PLAT-782: Modified tag placement when sending through the API so that if an anchor string y- offset would force a tag outside of the page boundaries, the tag will be placed at the page boundary instead of causing an error. This change does not impact the x-offset value. PLAT-872: Updated API components to function with changes to XMP data formats from Acrobat 11. PLAT-964: Corrected a Connect issue where DocuSign Status records were being duplicated for some customers. PLAT-994: Corrected a SOAP API issue where a ClientUserID appeared in the response without being provided in the original request. PLAT-1006: Corrected a REST API issue where GET page image was pointing to the wrong endpoint, causing an error message when used. PLAT-1081: Corrected an issue where some senders were not receiving an envelope completed email messages for envelopes sent through the DocuSign Mobile app. PLAT-1103: Corrected a REST API issue where modifying a recipient without including a routing order caused the routing order to change to 1. PLAT-1107: Corrected a REST API issue where the date-time for "statusdatetime" in the envelope creation response was two hours off from UTC. This is related to PLAT-1335. PLAT-1273: Corrected an API issue where an error was caused if special characters (@,, ) were used in passwords for the X-DocuSign-Authentication XML header. PLAT-1335: Corrected a REST API issue where the API Time Zone setting from the web console was inadvertently changing the UTC timestamp for envelopes requested through the REST API. This is related to PLAT-1107. ARCH-294: Updated Security Appliance error messages. ARCH-330: Added the ability to use TLS v1 protocol with DocuSign Security Appliance. 19 Copyright 2009-2014 DocuSign, Inc. All rights reserved.
Release Bug Fixes March 11, 2014 The following bug fixes were completed for the March 11, 2014 release. The name-number is the internal DocuSign tracking number for the bug. WAPP-2325: Improved error handling and reporting for SAML AuthNRequests. WAPP-2767: Corrected an issue where a user could not apply a template if the template name had special characters in the template name. WAPP-3172: Corrected an issue where the Next and Previous buttons were not functioning correctly when enabling user sharing settings. WAPP-3222: Corrected an issue where when cloning an envelope with custom messages for each recipient, the custom messages were not replicated in the cloned envelope. WAPP-3326: Corrected an issue when using Internet Explorer browser where an over-laid Data Field tag was disappearing when trying to cut and paste text into the tag. This is was resolved for IE version 9 and later, but not for IE8. Workarounds have been provided for IE8. WAPP-3356: Corrected an issue where a Single Sign On (SSO) user was unable to log on to the system after cancelling out of a Password Reset operation. WAPP-3368: Corrected an issue where a sender was unable to scroll to and tag the second page of a document when using the Salesforce1 integration on an ipad. WAPP-3376: Corrected an issue in the DEMO environment where DocuSign was unable to verify some Single Sign On (SSO) users. WAPP-3462: Corrected an issue where the This is a Payment Amount option was not appearing in Formula Tag and Drop Down Tag properties. WAPP-3499: Corrected an issue where the company name was not being updated from Branding when the Use Brand Company Name option is enabled. This is related to WAPP- 3500. WAPP-3500: Corrected an issue where the envelope signer Welcome screen was showing the Brand company name instead of the account name. This is related to WAPP-3499. WAPP-3584: Corrected an issue where the Anchor Text function was incorrectly centering tags on the anchor point. SIGN-1461: To provide more control for access code authentication requests on mobile devices, the <user> and <company> names display text has been added to the Branding Signing resource file ActivationSec_AccessCodeMsgDefault_Mobile string, allowing the information to be customized. Previously these items were not part of the editable string and were always displayed. Additionally, DocuSign has updated the resource files for customers that previously modified this information so the names are not shown twice. Note that a programmatic check has been put in place to watch for accounts that might have added <user> or <company> name information ahead of the change to ensure it doesn't display twice. This check will be in place for 1 month after the Spring 14 Release. SIGN-1505: Corrected an issue where when signing with some Android tablets the draw signature option allowed the signature to go outside the normal signing range. SIGN-1701: Corrected an issue on the Save a Copy dialog when signing is complete where pressing Enter did not always create an account. 20 Copyright 2009-2014 DocuSign, Inc. All rights reserved.
SIGN-1893: Corrected an issue where when signing with an Android device text tags that appear at the bottom of the display were being scrolled out of view when trying to select the text tag. SIGN-1899: Corrected an issue where images for tags on the free-form tag menu were missing when signing with older Android devices. SIGN-1900: Corrected an issue where the resize and delete images were missing from freeform tags when signing with older Android devices. SIGN-1922: Corrected an issue where the DocuSign logo was missing when using older Android devices. SIGN-2382: Corrected an issue in the DEMO environment where new strings in the Branding Signing resource file disabled other customizations. SIGN-2390: Corrected an issue where errors were caused when signing an envelope in a browser while also having the envelope open in an older version of a DocuSign mobile application that had timed out. SIGN-2405: Corrected an issue in the DEMO environment where the "Please Wait" dialogue displayed after clicking "Confirm Signing" had a close "x" button that could be clicked by a signer. PLAT-347: Improved the error messaging when there is an invalid recipientid for offline signing. PLAT-355: Improved the error messaging when the signer email is omitted for offline signing. PLAT-1053: Corrected an issue with Connect for Salesforce where some users were getting invalid type error messages when Connect for Salesforce was publishing to the Salesforce account. PLAT-1094: Corrected an issue where envelope history event shows signer event prior to envelope creation due to time zone setting correction issues. PLAT-1128: Corrected an issue where there was no PDF attachment with an email when using the Sign a Document Now function. PLAT-1229: Corrected a REST API issue where an unspecified error message was received when requesting recipient tabs. PLAT-1266: Corrected an issue where some template recipient role names were causing conflicts when sending an envelope through DocuSign mobile for ios. PLAT-1483: Corrected a PowerForms issue where senders were unable to pre-populate data fields using the URL syntax <RoleName>_<SecureFieldName>=<value>. PLAT-1492: Corrected an issue where some new users were receiving a system error when attempting to activate their membership. PLAT-1500: Corrected an issue where shared templates were missing from the folders to which they were shared. PLAT-1582: Corrected a SOAP API issue where RequestPDFWithOptions with multiple documents duplicated the first document. DSP-1083: Updated the text for the DocuSign Express Subscriber Agreement. MIS-752: Corrected an issue where the Save button was not being displayed when trying to update billing information in the console. 21 Copyright 2009-2014 DocuSign, Inc. All rights reserved.
ARCH-303: Corrected a SAML 2.0 issue where some user records with a created status were causing errors when attempting login. ARCH-369: Corrected a Single Sign On issue where DSAPI security session tokens generated by WIF 1.0 were unreadable by.net 4.5. 22 Copyright 2009-2014 DocuSign, Inc. All rights reserved.