DocuSign Release Notes April 7 2012

• update the name (if allowed), email address (if allowed), note, and access code for recipients• void the envelope• re-send the envelope invitationsThis new recipient action and recipient type is available to be selected when creating an envelope or atemplate from the web console or through the DocuSign API. Implementing this feature will requirechanges to your API. Click here for more information on the API changes for this feature.ConnectorsDocuSign for Alfresco v1.0DocuSign for SugarCRM v2.01- Added support for leads and contractsDocuSign for Sharepoint v1.1- Added support for Microsoft SharePoint Online Code Analysis FrameworkDocuSign for Salesforce v3.5.2 and 3.5.3- Fixed issue where an error was received when adding a user to DocuSign for Salesforce if theyalready have an active existing DocuSign membership. (Bug 14660)- Fixed issue where sending from a template with anchor tags fails. (Bug 11779)- Resolved an issue where a user experiences an error when editing recipient who has no emailaddress. (Bug 7917)- Fixed an issue where too many script statements were firing. (Bug 9202)- Fixed an error where installing a new package over an old package caused the sign in personrecipient role type to be missing. (Bug 12010)- Resolved a problem where users were unable to select cancel or next while adding a recipient.(Bug 12196)- Fixed an issue where selecting “tag” relayed out of Salesforce to a DocuSign URL. (Bug 13481)- Implemented a fix to resolve SDO installation issues. (Bug 13598)- Added in person signer to the recipient screen. (Bug 14416)- Fixed an issue where the custom email message did not support newlines. (Bug 14684)- Resolved an issue where custom objects threw an error about row assignment. (Bug 14905)- Fixed an issue where the DocuSign account failed to open in the console. (Bug 15148)7 Copyright © 2009-2012 DocuSign, Inc. All rights reserved.