docusign for salesforce — 6.6

DocuSign for Salesforce — 6.6Published October 26, 2016

DocuSign for Salesforce version 6.6 adds two Lightning Experience components, plus the ability to addsigning groups through CRL, and to attach Salesforce Files to envelopes. These release notes provideinformation about the updates delivered in the release and any subsequent patch releases.

ReleasesStarting with the DocuSign for Salesforce 4.0.x release, DocuSign enforces major releases, as well aspatches. This is an important step to make sure all DocuSign for Salesforce customers are using thelatest, most up-to-date package. Product documentation, including these release notes and otheradministrator and user guides, is valid for installations that upgrade to the stated version.

For all v4.0.x and later customers, upgrades begin no sooner than 30 days after a new major release islisted to the AppExchange. Patches are pushed to customers immediately. Salesforce has a strict codechange limit for patches, making them safe and reliable.

Any customer using a version of DocuSign for Salesforce older than v4.0.x (v3.11.5 and below) will notbe upgraded automatically.

To receive Early Access notifications

For major releases, customers can opt into our Early Access list and receive pre-release versions twoweeks before they are listed in the AppExchange. To opt in, send an email request [email protected] with the names and emails to receive Early Access notifications.

To postpone a major release push upgrade

Customers can postpone a major release push upgrade for 30 days. To request a delay and receive a30-day extension, notify DocuSign by email at [email protected] within the original 30 day upgradewindow. The notification must include the Salesforce.com Organization ID, the reason for requestingthe delay, and confirmation that the reason for the delay will be resolved within the extension period.Notification is required for each major release and can be requested only once per release.

2

18

21

What's New

Known Issues

Bug Fixes

For More Information or Assistance

221 Main Street, Suite 1000, San Francisco, CA 94105 Ι www.docusign.com Ι © DocuSign, Inc.

22

Release Notes

mailto:[email protected]?subject=Request to join Early Access list

mailto:[email protected]?subject=Request to postpone upgrade

DocuSign for Salesforce Release Notes

What's NewThis section covers the new features and functionality delivered in the release.

DocuSign Lightning Components (6.6)Two Lightning Experience components are available:

l Send with DocuSign: Salesforce users can now send envelopes from Salesforce Lightning withthe DocuSign Sending Lightning component. The behavior of the component is similar to theSend with DocuSign button in Classic. When the button is clicked, a new window opens theDocuSign for Salesforce page where you can add documents, select recipients, set messages,reminders, and more. After the envelope is sent, a landing page confirms the envelope has beensent and allows the you to close the window and return to the Salesforce record. The DocuSignSending Lightning component is enabled by dragging and dropping the Lightning component ontothe record page from the Lightning App Builder.

l DocuSign Status: Available in the AppExchange for Components, the DocuSign Status displaysthe status of the last envelope sent and shows who still needs to take action on the envelope.

CRL for Signing Groups (6.6)As of DfS v6.6, Custom Recipient Lists support signing groups. In DocuSign for Salesforce, you can nowsend envelopes to signing groups using the CRL custom button parameter. This enables the ability tosend an envelope to a group where any member can open the envelope and act on the documents.

As a reminder, the Any Signer feature will be retired as of December 1, 2016. For more information,refer to the August 2016 Service Pack Notes and the support article, How to Transition from Any Signerto Signing Groups.

Salesforce Files Support (6.6)DfS in Salesforce Classic, by default, pulls only attachments into an envelope. Salesforce is movingfrom Attachments to Files, however, so we created the Add attach Files to envelopes setting inDocuSign Admin -> Settings to assist with the transition and enable pulling files as well as attachmentsinto an envelope.


2

https://www.docusign.com/supportdocs/pdf/release-notes/August-2016-ServicePackNotes.pdf

https://support.docusign.com/en/articles/How-to-Transition-from-Any-Signer-to-Signing-Groups

https://support.docusign.com/en/articles/How-to-Transition-from-Any-Signer-to-Signing-Groups


Envelope Custom Fields (6.4.1)Envelope custom fields are used to classify, record, and track information about documents sent by auser. These field values can be free-text entries, or selected from a list of possible values. Envelopecustom fields can be required or optional.

In DfS v6.4.1, you can now define envelope custom fields for the envelopes you send with DocuSignfrom a Salesforce object. When you send a document with DocuSign, the envelope prepare pageincludes a new section, Custom Field(s). Required fields are marked with an asterisk.

Envelope custom fields are created and managed by your DocuSign administrator in the DocuSign webapplication, as described in Envelope Custom Fields.


3

https://support.docusign.com/en/guides/cdse-admin-guide-envelope-custom-fields


Extended List of Trusted IP Ranges (6.4.1)With DfS v6.4.1, the required list of Trusted IP Ranges is extended to include the following additionalentries:

l 54.149.21.90

l 54.69.114.54

l 52.25.122.31

l 52.25.145.215

l 52.26.192.160

l 52.24.91.157

l 52.27.126.9

l 52.11.152.229

l 52.28.168.105

Add additional IP RangesNew installs of DfS v6.4.1 will include these ranges as part of the installation process. However, for thefollowing two scenarios, you will need to add these ranges manually, as described here:

l Upgrading to DfS v6.4.1 - If you are upgrading your DfS installation from an earlier version, youwill add these additional entries, following the procedure in Add Trusted IP Ranges for DocuSignfrom the DocuSign for Salesforce Administration Guide.

l New install without the Salesforce Metadata API - If you are doing a new install into anorganization that does not support the Salesforce Metadata API, you will complete a portion ofthe configuration manually, including adding the Trusted IP Ranges, as described in Configure forOrganizations Without the Metadata API from the DocuSign for Salesforce Administration Guide.

Sending Documents for DocuSign Part 11 Accounts (6.4.1)If your DocuSign account has the DocuSign Part 11 module enabled, DfS v6.4.1 adds basic compliancesupport for sending documents. The Part 11 module imposes certain procedures and controls designedto ensure the authenticity, integrity, and, as appropriate, the confidentiality of electronic records.

In DfS v6.4.1, when sending with DocuSign, the following Part 11 controls are enforced:

l Recipients must have a DocuSign account

l Recipients must have a required Signature or Initial tag on the document


4

https://support.docusign.com/en/guides/dfs-admin-guide-add-ip-ranges

https://support.docusign.com/en/guides/dfs-admin-guide-configure-no-api

https://support.docusign.com/en/guides/dfs-admin-guide-configure-no-api


Custom Tags (6.3.0)With DfS v6.3, a new Custom Tags tab in DocuSign Admin allows you to add, edit, and delete yourcustom tags, including those with merged data, directly from within your Salesforce environment.Custom tags created in DocuSign and those created or edited in the new DocuSign Admin tab remain insync. You can edit and view custom tags from either place.


5


Add new custom tags directly from this new interface. Just click New , and complete the form. Or editan existing tag by locating the tag in the Custom Tags list and clicking on it to open the form.

To edit custom tags, from the Custom Tags list, click on the tag and make the desired changes in theform. To delete the tag, scroll to the bottom of the form and click Delete.

Verify with D&B (6.2.0)Verify with D&B is a fee-based Dun & Bradstreet service for Pre-Contract Risk Screening. With DfSv6.2, account administrators can add the Verify with D&B button to Opportunity and Account objects.For a separate fee per use, DfS users can use this button to acquire D&B's risk screening data,including the Financial Stress score and D&B PAYDEX score. Scoring is available for U.S.-basedcompanies only.


6


As a DfS administrator, you add the Verify with D&B button to the Opportunity and Account objectsfrom the DocuSign Admin Layouts tab:


7


As a DfS user, you select the Verify with D&B button on an Opportunity or Account to launch the D&Bwizard to identify an account and purchase and download the risk scores:

The D&B wizard receives the logged in user ID to check for an account. To purchase risk scores, youmust have a D&B account, or you can create a free trial account through the wizard.

Support for Salesforce Console (6.2.0)DfS v6.2 adds support for the Salesforce Service Cloud Console app. The Console is an app in theSalesforce Service Cloud which shows several objects on a single screen at a time. You can read moreabout the Console app in Salesforce.com's documentation.

Because the Console app operates within iFrames, if you use custom buttons to script your own DfSactions, and the buttons are available within a Console view, you must update your button scripts. Thechanges are to first check for an iFrame, and if true, set the button action to happen in a new window.

Add a check for an iFrameWithin a custom button that is available in a Console view, add code to check for an iFrame:function inIframe () {

try {

return window.self !== window.top;

} catch (e) {

return true;

}

}


8

https://help.salesforce.com/HTViewHelpDoc?id=console2_about.htm


Set the button action to occur in a new windowAny reference to window.location.ref must be replaced with window.open(). For example, thefollowing line of code (or similar ones):window.location.href = "{!BaseUrl}/apex/dsfs__DocuSign_CreateEnvelope?"

+[custom button parameters];

Must be replaced with the following code:if(inIframe()){

window.open("{!BaseUrl}/apex/dsfs__DocuSign_CreateEnvelope?nw=1"+[custom buttonparameters], "Popup", "location=1, status=1, scrollbars=1, resizable=1,directories=1, toolbar=1, titlebar=1, width=1200");

} else {

window.location.href = "{!BaseUrl}/apex/dsfs_DocuSign_CreateEnvelope?"+[custombutton parameters];

}

Always remember to replace [custom button parameters] with your own custom buttonparameters.

Now Available in 13 Languages (6.1.0)DocuSign for Salesforce now provides localized support in several languages for both Salesforce andSalesforce1.

PrerequisitesTo enable translated content for your DocuSign for Salesforce users, as the Salesforce administrator,you must select the languages to activate for translation in the Salesforce Translation Settings.

1. Enable the Translation Workbench: at Setup > Administration Setup> Translation Workbench,click Enable.

2. Select Translation Settings in the Translation Workbench menu.


9


3. Activate the required languages: select Edit for each language you want to activate, and thenmark the Active check box:

Select and activate any of the 13 supported languages in DocuSign for Salesforce, as listed belowin the "Display Language" section.

Display LanguageIf users select one of the 13 supported languages for their Salesforce Language setting, then theDocuSign for Salesforce views, pages, and out-of-the-box elements such as the Send With DocuSignbuttons, all display in the matching language. If a non-supported language is selected, DocuSign forSalesforce displays in English.

DocuSign for Salesforce supports the following display languages:

l English

l Chinese (Simplified)

l Chinese (Traditional)

l Dutch

l French

l German

l Italian

l Japanese

l Korean


10


l Portuguese

l Portuguese (Brazil)

l Russian

l Spanish

Note: The tagging view, where you add fields for your recipients to complete, is not translated, andremains an English only view. Likewise, the signing language for recipients is not affected by thedisplay language setting.

The tagging view language is set by either your browser's language preference, or your DocuSigndisplay language selection, set from the language menu in the footer of the application.

Chatter Language SettingSeparate from the display language support, the DocuSign administrator can set a new languagepreference for the envelope and recipient event posts in Chatter feeds. This setting applies to allDocuSign users in the organization.


11


Changing the Chatter Language Setting populates the default Chatter message in the selectedlanguage.

This setting is located on the DocuSign Admin tab, in the Settings view, and offers the following 11language selections:

l English

l Chinese (Simplified)

l Dutch

l French

l German

l Italian

l Japanese

l Korean

l Portuguese (Brazil)

l Russian

l Spanish


12


Send with DocuSign (6.0.1)For users, sending envelopes is easier and offers a cleaner interface. The process to send an envelopeusing the out-of-the-box Send with DocuSign button has been revamped with an updated UI and newfeatures.

EnhancementsHere's a summary of the version 6.0.1 enhancements to the standard sending process. For completeinformation on sending documents, please see the DocuSign for Salesforce User Guide.

l Reorder documents or recipients attached to an envelope. If there are two or moredocuments, or multiple recipients, those line items can be reordered by drag-and-drop, or bymanually changing the order number.

l New Quick Add option to add recipients. Senders can add a recipient to an envelope with onlytheir name and email address. With Quick Add, you can add a recipient who is not a Salesforcecontact.

l Add a recipient to Salesforce Contacts. Senders can add a recipient to Salesforce Contactsdirectly from the Add Recipient > Contacts option:


13


From the Add Contact dialog, click the New Recipient link. Then fill in the new contact'sinformation, and click Save. The contact is added to both the envelope in progress, and as a newrecord in Salesforce Contacts.

Simplified Installation (6.0.1)For Salesforce administrators, v6.0.1 delivers improvements to the DocuSign for Salesforce installationflow. The overall process is still the same, but the steps have been reduced and simplified.

Note: This updated installation and configuration is only available for Salesforce editions whichsupport the Salesforce Metadata API.

EnhancementsHere's a summary of the version 6.0.1 enhancements to the installation process. For completeinformation on sending documents, please see the DocuSign for Salesforce Administrator Guide.

Redesigned interfaceConnecting your Salesforce and DocuSign accounts is easier than ever, with a clearer and simpler setof steps.


14


Automatic configuration of trusted network settingsVersion 6.0 uses the Salesforce Metadata API to add IP ranges automatically to your Salesforce TrustedNetwork list.

This enhancement replaces the previous process, which required you to manually add DocuSign IPranges.

Redesigned DocuSign Admin Tab (6.0.1)The DocuSign Admin tab is completely redesigned, making it easier to manage DocuSign forSalesforce. In addition to a better and more intuitive interface, version 6.0 offers major improvementsin functionality as described below.


15


Layouts - add DocuSign features to Salesforce layoutsLayouts is a brand new page on the DocuSign Admin tab. This new page simplifies the configurationprocess for adding standard DocuSign features, such as the Send with DocuSign button or Salesforce1mobile actions, to Salesforce layouts. As a DocuSign admin, you can add and remove these basicDocuSign elements to layouts by simply checking or clearing the check boxes.

No more manually editing each layout to add buttons and related lists. The new Layouts page brings itall together in one central location, and offers a tremendous improvement to configuring yourDocuSign for Salesforce installation.

Note: The new Layouts view is only available for Salesforce editions which support the SalesforceMetadata API.


16


Account - modify your account configurationThe Account page offers a newModify Account Configuration option. You can use this option toquickly and easily update the Salesforce or DocuSign credentials used to configure DocuSign forSalesforce.


17


Known IssuesThis section covers any known issues present in the release which are likely to impact users.

Drop-down menus on list views are not translated (6.1.0)Due to a blocking bug in Salesforce, the drop-down menus on list views, such as the View filter on theDocuSign Admin Users page, cannot be translated. These list menus remain in English regardless of theuser's Language setting in their Salesforce profile. (DFS-2991)

DocuSign images are not translated for BrazilianPortuguese (6.1.0)Due to a Salesforce limitation, the DocuSign logo, as shown in the DfS page header and page loadingscreens, are not translated to the appropriate image for Brazilian Portuguese. (DFS-3014)

DocuSign custom objects are not translated (6.1.0)DocuSign custom objects that come with the managed package are not translated. (DFS-3163)

Parameters in email message do not pull values whenlanguage selection is changed (6.1.0)If the Email message settings include optional language settings, plus parameters (such as [FirstName]), if the sender selects an alternate recipient language, then the parameter codes are used inthe message and are not populated with actual values. (DFS-3212)

Page layouts from other managed packages are notincluded in the DocuSign Admin Layouts page (6.0.12)If you have installed other managed packages in your organization that have their own custom layoutsfor any of the standard Salesforce objects, those layouts are not included in the DocuSign AdminLayouts page. (DFS-2989)

DocuSign mobile app tagging does not handle anchortags correctlyFor accounts which have enabled mobile app tagging, there is a known issue with using anchor tags.Specifically, if you use the standard or custom anchor tags in the documents you upload, the automatictagging does not work properly in the DocuSign mobile app. If you use anchor tags, you may end up


18


with duplicate tags or experience other, anomalous behavior. For more information on anchor tags seeAutomatic Anchor Text and Tags in the DocuSign for Salesforce User Guide.

Get DocuSign Mobile App warning screen appears whenapp is already installedFor Salesforce1 mobile users (iOS and Android) using the new DocuSign mobile app taggingintegration, during the setup and after sending, a warning screen is displayed, instructing the user todownload the DocuSign mobile app. This mobile app is required to use the new tagging integration.

In the Beta release, this warning appears even if the app is already installed on the mobile device. Inthis case, the message automatically dismisses after a few seconds. If users have installed theDocuSign mobile app, and they receive this message, they should just wait a few seconds for thewarning to close.

Salesforce1 error when DocuSign mobile app is notinstalled (Android)For Salesforce1 mobile users on Android only, if the DocuSign mobile app is not installed, an initialSalesforce1 error displays: "An error has occurred. Please try again." Users can disregard this errormessage. The message closes after a few seconds, and the Get DocuSign Mobile message appears,with an action to download the required mobile app.

Contact's email address is not included for in personsigning events (Android)For Salesforce1 mobile users on Android only, the email address for any contact selected for in personsigning is not automatically included on the envelope, and must be manually entered.

In the Beta release, for any in person signer, on the tagging page, the recipients list shows only thesigner's name and does not include the email address from the contact record. When you finishtagging your document and tap Host Signing, the Begin Signing dialog appears, and you must enterthe signer's email address manually.

DocuSign Recipient Status related list displays only onerecipientWhen sending an envelope to more than one recipient from a Leads object, the DocuSign RecipientStatus related list is only updated with the first recipient.


19

https://www.docusign.com/support/salesforce/documentation/dfs-user-guide/user-guide/automatic-anchor-text-and-tags-user


Solution: Modify Connect object settings for DocuSign_status_cUntil this issue is resolved in a future release, you can modify the Connect object dsfs_DocuSign_Status_c in your DocuSign account to allow the full list of recipients to display. You must be a DocuSignadministrator to make these changes. For more information about DocuSign Connect, see the DocuSignfor Salesforce Administrator Guide.

To modify Connect object settings1. In Salesforce, click the DocuSign Admin tab.

2. Click the Console tab to open DocuSign in a new window.

3. From DocuSign, click your profile image at the top of the console and select Preferences.The DocuSign Account Preferences page is displayed.

4. In the navigation bar on the left side of the page, under the Account Administration heading,click Connect.

5. Click Salesforce to open the DocuSign Connect for Salesforce configuration. The configurationpage appears.

6. Click the Edit link next to the DocuSign_status_c or dsfsDocuSign_Status_c object.

7. In Update Fields, click Add and add two new Salesforce/DocuSign paired fields as follows:

l Lead (reference) / Envelope External Source ID

l Contact (reference) / Envelope External Source ID

8. Click Save.

For all future envelopes with multiple recipients sent from the Leads object, you can now see allrecipients from the DocuSign Recipient Status related list.


20


Bug FixesThis release includes the following bug fixes. The ID number refers to DocuSign’s internal trackinginformation.

ID # Release Description

DFS-3891 6.6.1 Add friendly warning message for DfS Trial expiration on Admin page.

DFS-4038 6.6.1 Update Salesforce1 to pull Salesforce Files.

DFS-4044 6.6.1 Lightning Tagger page only fills one-half the screen.

DFS-4068 6.6.1In Lightning, DocuSign Admin page loads but the user is unable to navigate to a newtab within the page.

DFS-3496 6.3 Missing localization strings in Edit Recipient dialog box.

DFS-3448 6.2.1For a custom button configured to send from a Quote, the latest quote is not addedto the envelope.

DFS-3447 6.2.1When using the standard Send with DocuSign from an object with at least oneRelated Content document, the document appears twice in the DocuSign envel-ope.

DFS-3418 6.2.1When using Send with DocuSign in the Salesforce Service Console view, if theobject contains Related Content documents, they are not included in the DocuSignenvelope.

DFS-3347 6.2.1Senders cannot edit recipient roles to enter actual recipient name and emailaddress.

DFS-2960 6.2.0When passing the parameter "RSL" as a custom button, the RSL does not appear inthe URL.

DFS-3229 6.2.0 When configuring DfS, the Environment option "Other" does not work.

DFS-3146 6.2.0Salesforce users with an apostrophe in their email address are unable to sendusing custom buttons or the default Send With DocuSign button.

DFS-3207 6.1.2In the Add Recipients dialog, searching for a contact with an apostrophe in theirname results in an error.

DFS-3146 6.1.1Salesforce users with an apostrophe in their name are unable to send using custombuttons or the default Send With DocuSign button.

DFS-3143 6.1.0The Add Contact dialog for choosing contacts to add to a document only shows thecontact's name. If you have multiple contacts with the same name, there is no wayto distinguish between them.

DFS-2948 6.0.17 If you attempt to access any Visualforce page from the DocuSign for Salesforce


21


ID # Release Description

managed package, an error message appears: "Attempt to de-reference a nullobject".

DFS-2936 6.0.16

For new trial organizations, the personal information in the profile of the Sales-force admin is created with location data (state, country) that causes the followingerror message: There's a problem with this country, even though it may appearcorrect.

DFS-1677 6.0.16 System.LimitException: Apex CPU time limit exceeded.

DFS-2958 6.0.13 DocuSign Admin Layouts page error: "Error reading layouts."

DFS-2947 6.0.12Send With DocuSign button can cause long page load times and generate the fol-lowing error "Apex CPU time limit exceeded"

DFS-2934 6.0.11Layouts page error: Maximum view state size limit exceeded. Orgs with a sig-nificant number of custom layout views may encounter this error and be unable todisplay and use the new Layouts page in the DocuSign Admin tab.

DFS-2933 6.0.10 Fix installer for Salesforce organizations that do not support Metadata API.

DFS-382 6.0.1 Reduce the number of clicks to add a recipient.

DFS-419 6.0.1 Allow a DfS sender to type the email address and name of a signer.

DFS-444 6.0.1 Design better display of templates (DS templates) in DfS when choosing.

DFS-2138 6.0.1Remove "Edit" permissions for DocuSign Status within "DocuSign User" PermissionSet.

DFS-2898 6.0.1 Can't clear values from Remind and Expire settings

For More Information or AssistanceFor more information or assistance, visit DocuSign Salesforce Support, the DocuSign Community,docusign.com, or contact DocuSign Support.

Send us your feedbackWe love to hear from our customers. To provide feedback on any aspect of this application, pleaseemail us at [email protected].


22

https://www.docusign.com/support/salesforce

https://support.docusign.com/community

https://www.docusign.com/

mailto:[email protected]