Instructions on upgrading your Adobe Sign for Salesforce package to the newest version.

The Adobe Sign for Salesforce integration package is available from the Salesforce AppExchange. This guide is designed to help current customers of Adobe Sign upgrade from an older release version to the most current released version of Adobe Sign services for Salesforce.

Refer to the release notes for additional information on the newest features in Adobe Sign for Salesforce. Also refer to the installation guide for more information.

Note:

Support for the Adobe Sign for Salesforce integration v18 has ended as of March 1, 2019

Product updates, security updates and technical support for Adobe Sign for Salesforce v18 has ended as of March 1, 2019

Upgrading from a previous release

Customers that have integrated with Apttus should not upgrade their Adobe Sign for Salesforce package to v21

Caution:

Be advised that the Adobe Sign for Salesforce objects may change as the package evolves.

If you build a custom solution that depends on these objects, and they change, you may be required to update your customization.

Each version of Adobe Sign for Salesforce has new features and enhancements that can provide key improvements to your document workflows. Adobe strongly recommends that you upgrade to the latest release, as Adobe will be discontinuing support of older releases over time.

Adobe Sign for Salesforce can be upgraded from any package named “EchoSign”, “Adobe Document Cloud eSign Services” or “Adobe Sign”. If you have an earlier version of EchoSign for Salesforce installed or need assistance for upgrades, contact the Adobe client success manager assigned to your account. That person will be able to help you or direct you to Adobe Sign support and/or Adobe Professional Services for assistance.

To find the version of the Adobe Sign services for Salesforce integration you currently have installed:

Log into Salesforce as your account admin ID

Navigate to Setup > Platform Tools > Apps > Installed Packages

Note the Package Name and the Version Number. The Package Name you have installed is either “Adobe Document Cloud eSign Services” or “Adobe Document Cloud eSign Services - Unmanaged.”

Older versions of the “EchoSign for Salesforce” packages are unmanaged packages. Newer versions are managed packages. This document includes instructions on how to update from a managed or an unmanaged package. Follow the instructions based on the package type installed currently.

Also, if you’re upgrading from version 12 or prior and have multiple Adobe Sign accounts sending from the same Salesforce org, you must consolidate these users under one Adobe Sign account before upgrading. After consolidating your users, you can use group mappings to map specific Salesforce profiles to Adobe Sign services groups. Contact Adobe Support if you have questions.

Important upgrade notes for all customers

1. If you have users in your Salesforce org who belong to multiple Adobe Sign accounts, reach out to your Adobe client success manager or to Adobe support before upgrading.

2. Before upgrading your production account, Adobe recommends testing the upgrade process in your Salesforce sandbox environment. Also, make sure your email address in the Sandbox environment is one that you have access to in case you ever need to change the email for your Adobe Sign account.

Upgrading from EchoSign unmanaged packages

If you have a package with the package name “EchoSign Unmanaged” currently installed, there are two possible approaches to upgrade to the latest version of the Adobe Sign managed package. You can decide which approach works better for your organization.

This option is much easier to set up than option 2, but the downside is that existing agreements in your org won’t be as easily accessible by your users in the future.

1. Install the latest version of the Adobe Sign managed package from the AppExchange into your org, configuring and exposing it to all relevant profiles and page layouts. Refer to the installation and customization guide for more information about setting up the new package. Once the latest Adobe Sign package is installed, your Salesforce users can immediately start using it.

2. After installing the new package, hide the old unmanaged package from users by removing it from their profiles and page layouts. This action is strongly suggested so users are not confused by seeing two similarly named tabs, related lists, objects, and so on, side-by-side when using Salesforce. This approach allows your Salesforce users to start using the new version of the Adobe Sign for Salesforce package while retaining the legacy agreement data from the older package in case it needs to be accessed.

Note:

Since the old package is hidden, accessing it must be a rare and special request. If those older agreements need to be referenced frequently, then hiding the old package may not be the right course of action for your organization.

Option 2 allows you to migrate your existing agreement data to the new package, but the downside is that it requires more effort than option 1. This approach involves the following steps:

4. Import the agreement data from the old unmanaged package into the new package.

A word of caution about this approach is that uninstalling a package removes all Adobe Sign data in that package (that is, agreements) from that org. Therefore, it requires that you export first and then import data back into Salesforce to retain the data when moving to the new managed package.

Note:

The agreements still exist on Adobe Sign servers, but they are not accessible from Salesforce once you remove them.

In addition, exporting and importing agreement data may include child objects, depending on requirements, and must be structured appropriately. One complication that arises when importing child objects is that the parent agreement ID has changed, so it needs to be updated appropriately for each imported row. There are two key child objects:

Agreement Event—Records the audit events for an agreement. If this is not required, it can be skipped.

Attachment—Contains the original sent document and the final signed PDF for the agreement. Some organizations may have a signed PDF link to echosign.adobe.com, which for many would be sufficient, so the attachment can be skipped.

Another consideration is mapping the fields from the exported unmanaged records to the latest managed record. All the fields in the old package still exist in the new package, so they can be mapped directly. An advanced tool like Dataloader.io will automatically match to the correct field based on the column name.

Upgrading from managed packages

If you have a package with the package name of “Adobe Document Cloud eSign Services“ or "Adobe Sign" currently installed, you must do the following to upgrade to the latest version of the Adobe Document Cloud eSign services package:

Review and understand the Important upgrade notes for managed packages prior to installation

Important upgrade notes for managed packages

1. Do not uninstall your existing EchoSign or Adobe Document Cloud eSign services for Salesforce package. Uninstalling the package will result in the loss of all your Adobe Sign data in Salesforce.

2. Ensure that the Lock sessions to the IP address from which they originated setting is disabled. To do this, click Setup then navigate to Administer -> Security Controls ->Session Settings.

3. Be aware that hosted agreements that were sent from “EchoSign for Salesforce” version 14 or earlier and are still out for signature during the time of upgrade will not be able to get status updates when they are signed after the upgrade. Make sure that agreements initiated as hosted agreements are signed before you upgrade.

4. Hosted agreements no longer need Sites in Salesforce, starting in version 13. Sites are required only if you need to send large document transactions—greater than 2.0 MB. Keep in mind that Professional Edition will not support sending large files because Sites are not supported. If you previously set up Sites for hosted agreements and do not need to send large transactions, you can deactivate the EchoSign Callback Site.

5. A number of new Adobe Sign services settings were added in versions 13, 14, 15, 17, 18, and 19. Make sure you review them and determine which you want to set for your org. The "What's New" sections below outline the most commonly used new settings and field values added in versions 13 to 19.

Installing the Adobe Sign for Salesforce update

Click here to access the Adobe Sign application package on the Salesforce AppExchange.

Click the Get It Now button.

Select Log in to the AppExchange and enter your credentials to continue.

Determine where you would like to install the upgrade (production or sandbox).

Review the installation information and terms and conditions, confirm that you have read and agree to the conditions, then click Confirm and Install! to start the installation process.

When prompted to login to your Salesforce organization, enter your Salesforce Username and Password then click Login in to Salesforce.

When the Upgrade Adobe Sign page displays:

Select Install for All Users

Click Upgrade

Installation can take a few minutes.

8. If the Approve Third Party Access popup displays:

Check Yes, grant access to these third-party web sites

Click Continue to start the installation.

9. During installation, a notification page displays telling you this all could take some time...

Click Done and then wait to receive the email notifying you that the package has been installed successfully.

The Installed Package page now displays your current package version.

Post-Install Configuration

A few simple setup steps are required before you can start sending Adobe Sign agreements from Salesforce.

Once the installation and configuration of the new package is complete, you should refer to the appropriate sections in this guide for information on which settings and fields were added in versions 13, 14, 15, 16, 17, 18, and 19.

You must manually enable these new settings and field values in your org in order for the new package to work correctly. For example, if you are upgrading from v15 to v19, you should enable the any new settings, fields, or both listed for versions v16, v17 and v18.

What’s new in version 21

Below is the new sequence (as of v21.0) in which the agreement and its related objects are updated:

Attachments

Recipients

Agreement (status and its other attributes)

Agreement Events

Chatter Feeds

The agreement status is now updated after the documents and recipients are updated

Prior to v21 the status was set before.

The Signed Agreement object (which stores the Image URLs) is now not inserted at all

Prior to v21 it was inserted after all of the other updates were completed

In v20, the Callback user in Salesforce was not required be an Adobe Sign licensed user.

The improvements to Push Mapping in v21 require that the Callback user have an active userID in the Adobe Sign account that is connected to the Salesforce organization.

v20 Customers using PushMapping should ensure that the Callback user is already provisioned in Adobe Sign prior to upgrading. Otherwise the PushMapping will stop functioning (until the user is provisioned) after upgrading to v21.

The Push Mapping functionality that automatically linked related objects using the setting ‘Copy Contact Account/Opportunity’ has been expanded to include Agreements sent from Salesforce.

e.g. Agreements sent from Salesforce will automatically copy the first Contact recipient’s Opportunity lookup to the Agreement’s Opportunity lookup and first Contact recipient’s Account lookup to the Agreement’s Account lookup, if the agreements sent do not have any linked Account/Opportunity

Prior to v21, Chatter feeds were only populated when the agreement was sent from within Salesforce.

This update expands the Chatter feed to include agreements sent from outside Salesforce (Push Agreements)

Prior to v21, the Agreement View only updated the PDF image and URL after the first recipient completed their action.

The image and URL now update earlier, when in a Prefill status, or when Out for Signature to the first recipient.

No configuration is required to enable this functionality.

A new Agreement status of Waiting for My Delegation is being introduced to reflect when an agreement is waiting for the Sender to delegate the current recipient authority.

No configuration is required to enable this status.

The Agreement Template has a "Days Until Expiration" field (echosign_dev1__Days_Until_Expiration__c). This is a numeric field, and has been deprecated in v21.

A new "Days Until Expiration" field (api name: echosign_dev1__Days_Until_Expiration2__c) has been added, but is a text field, allowing it to reference other fields in the Master Object (e.g.{!Expiry_Date__c})

When upgrading from a previous version, any form data mapped to the legacy expiration field is automatically copied to the new field, so no direct action is required.

The Account, Opportunity,and Contract fields are no longer available on the template page.

Admins can configure these fields in the template using the Map Data into Agreement Fields feature

Previously, Senders could define their absolute position in the signature stack as "Sender Signs First" or "Sender Signs Last".

This field is no longer available on the New Template pages. Senders have the option to insert themselves in any position of the signature stack.

The toggle to control the overall signature flow as "Sequential" or "Parallel" has been removed.

The new template style allows a fully configurable workflow that can be wholly sequential (Signer index 1 through 1+N), parallel (All Signer indexes are 1) or a mixture of sequential and parallel where the signature index is configured to the specific workflow.

Five settings have been deprecated in v21. All settings were in the Adobe Sign Settings section of Custom Settings.

The five settings are:

Add Audit PDF to Attachment List—Enable this setting to attach the PDF of the audit trail to the Agreement record after the agreement is signed.

Add Signed PDF as Separate Attachments—Enable this setting to attach the PDF of the signed agreements as separate attachments when there are multiple documents sent in a single transaction. To stop receiving the signed agreement as a merged PDF, please contact Adobe Support for assistance.

Add Supporting Files to Attachment List—Enable this setting to attach the PDFs of the supporting documents to the Agreement record after the agreement is signed. Through the supporting document fields in the agreement, the signers upload and attach the supporting documents to the agreement transaction.

Add Signed PDF Link for Pushed Agreements (Enabled by Default)—This setting applies only for pushed agreements sent outside of Salesforce. Enable this setting to add a link for signed PDF to the Agreement record.

Add Signed PDF for Pushed Agreements (Enabled by Default)—The setting applies to agreements sent from outside of Salesforce and pushed into Salesforce. Enable this setting to attach the signed PDF to the Agreement record.

Customers that are using the above settings can configure the new setting under Adobe Sign Agreement Update Settings.

Deprecated Setting (under Adobe Sign Settings)

New Setting (under Adobe Sign Agreement Update Settings)

Add Audit PDF to Attachment List

Add Audit Report

Add Signed PDF as Separate Attachments

Add Signed PDF as Separate Attachments

Add Supporting Files to Attachment List

Add Supporting Files

Add Signed PDF Link for Pushed Agreements

Add Signed PDF URL

Add Signed PDF for Pushed Agreements

Add Signed PDF

v20.9 Security Modifications for Callback Sites

Version 20.9 of the Adobe Sign for Salesforce package shifts the authorization for the objects used in large document support from the Site user to a licensed “callback” user that is explicitly granted authority.

Please remove all existing permissions on sensitive or nonpublic objects assigned to the site user on the respective site used for Large files or Push Agreement.

Note:

My Domain must be configured prior to configuring the Large Document Service to permit the OAuth authentication of the Callback User

For existing customers that are upgrading to 20.9 or beyond, the recommended process is to:

Mouse over the Enabled Apex Class Access link, and click the Edit button

Remove the AgreementAttachmentService class

Add the LargeFileDownloadService class

Save the page

Click the Edit button on the Adobe Sign Callback Profile page

Remove all permissions explicitly assigned to Site User

Click Save

Version 20.9 of the Adobe Sign for Salesforce package shifts the authorization for the objects used in push agreement support from the Site user to a licensed “callback” user that is explicitly granted authority.

Please remove all permissions assigned to site user on the respective sites.

Note:

My Domain must be configured prior to configuring Push Agreements to permit the OAuth authentication of the Callback User

For existing customers that are upgrading to 20.9 or beyond, the recommended process is to:

1. Create the new callback user

Note:

Only one Callback User is permitted for Adobe Sign. If you already have one established, configure that existing Profile/User.

Clone the Standard User profile

Name the new profile with an intuitive name (eg: Adobe Sign callback user)

Save the profile

2. Create a new “callback” user using a standard Salesforce license

Give the user an intuitive name (eg: Adobe Sign Callback)

Assign a Salesforce license

Assign the profile you created above

Save the new user

Assign the Adobe Sign Integration User permission set to the callback user created above

Mouse over the Permission Set Assignments link, and click the Edit Assignments button

Remove the Adobe Sign Integration User permission set

Remove all other permissions explicitly assigned to Site User

Click Save

What’s new in version 20

Organizations that use the Lightning interface in Salesforce must have My Domain enabled for v20 of the Adobe Sign package to function properly.

Organizations using the Classic interface are not required to have My Domain configured at this time.

v20 of the Adobe Sign package includes three new recipient roles:

Acceptor - The Acceptor role is appropriate when the Recipient needs to acknowledge an acceptance of the Agreement without formally approving the content

Form Filler - Designed specifically for customers that have a need to fill in form content during the signature process

Certified Recipient - Certified Recipients can have no (zero) form fields assigned to them. During their "signature" process, they will be asked to either delegate, decline or acknowledge the agreement

To gain access to these roles, they must be added in a three step process (four steps if you want to localize the roles to non-english languages).

Enable Acceptor Role - Recipients marked as acceptors accept the document. They may be required to enter field data

Enable Form Filler Role - Form fillers are enabled to fill in field level data

Enable Certified Recipient Role - Certified Recipients acknowledge the agreement, but do not sign. They may be required to fill in field data

Note:

Delegators – All recipient roles have a "delegator" version. Delegator roles are used when the known recipients are not expected to complete the identified role. Rather, they will delegate their role to another party.

Delegator roles are enabled by the same process described above.

The available delegator setting values are:

Enable Delegate Acceptor Role - Needed when you want to delegate an Acceptor role

Enable Delegate Certified Recipient Role - Needed when you plan to delegate a certified recipient

Enable Delegate Form Filler Role - Used when you have to delegate a Form Filler role

Enable Recipient Delegate Approver Role – Needed when you plan to delegate to Approvers

Enable Recipient Delegate Signer Role – Needed when you are going to delegate to Signers

The status values of the recipient and agreement objects are tied directly to the roles that are enabled in the system. If you are enabling additional roles, then you also need to add the associated role values to various object picklists. The process is consistent for each object, with some variation in the values added depending on the context of the object.

The object > fields that need to be updated are:

Recipient > Recipient Role

Recipient > Status

Add Recipient > Recipient Role

Agreement > Agreement Status

Field Mapping > Map on Events

File Mapping > Map on Events

The field values that should be added are:

Object Name

Field

New Values to be Added

Agreement

Agreement Status

Out for Form-Filling

Waiting for Counter-Form-Filling

Form-Filled

Out for Acceptance

Waiting for Counter-Acceptance

Accepted

Out for Delivery

Waiting for Counter-Delivery

Delivered

Recipient

Recipient Role

Acceptor

Form Filler

Certified Recipient

Delegate to Acceptor

Delegate to Form Filler

Delegate to Certified Recipient

Recipient

Status

Accepted

Form-Filled

Delivered

Waiting for Acceptance

Waiting for Form-Filling

Waiting for Delivery

Add Recipient

Recipient Role

Acceptor

Form Filler

Certified Recipient

Delegate to Acceptor

Delegate to Form Filler

Delegate to Certified Recipient

Field Mapping

Map on Events

Out for Form-Filling

Waiting for Counter-Form-Filling

Form-Filled

Out for Acceptance

Waiting for Counter-Acceptance

Accepted

Out for Delivery

Waiting for Counter-Delivery

Delivered

File Mapping

Map on Events

Out for Form-Filling

Waiting for Counter-Form-Filling

Form-Filled

Out for Acceptance

Waiting for Counter-Acceptance

Accepted

Out for Delivery

Waiting for Counter-Delivery

Delivered

The process to add the values and localize them is consistent across all objects.

Below is the process for Recipient > Recipient Role, and can be applied for each object in turn.

Add the roles to the Recipient picklist:

Once the new roles are enabled, the pick list values for the fields must be updated to include them.

Double-click the column space next to the English status to open the text field where the translation can be entered, and enter the appropriate localized value

2. Click Save when done

The Document field of the Agreement object contains a hyperlink to the agreement. There are two changes to this field in the v20 release:

The hyperlink text no longer has the status of the agreement appended to it.

Prior to v20, hyperlink text contained the agreement name and the status “- signed” or “- approved” appended to the end:

Version 20 removes the appended status, leaving just the agreement name:

Prior to v20, the Document field contained the hyperlink only when the agreement transaction was completed successfully.

In the v20 package, the Document field always contains the latest PDF version of the Agreement:

The Help Text for the Chatter event Post when Agreement Sent can be updated to remain consistent with the new recipient roles.

Navigate to Setup > Platform Tools > Custom Code > Custom Settings

Click the label Adobe Sign Chatter Settings

Click the Edit link next to Post when Agreement Sent

4. Update the Help Text to read: Post Chatter update when agreement is sent for signature/approval/acceptance/ form-filling/delivery.

5. Click Save

When the Adobe Sign application for Salesforce is upgraded from versions older than v14 to the current build, users might not be able to perform actions such as Delete, Cancel, View, Remind, or Update on the existing agreements that were sent by other users before upgrade.

Users may prompt an error when one of these actions is executed, similar to:

“INVALID_DOCUMENT_KEY” or “An internal server error has occurred”

This happens due to a legacy document key style that was used in versions of the application before version 14.

A one-time migration of those legacy keys is required. To this end, a new affordance as described below:

After completing the set-up steps, the following links will be available on the Adobe Sign Admin page:

Update Legacy Document Keys - Clicking this link will flush out the existing legacy document keys and fetch the new document keys for all the agreements existing in the org.

In case there are any agreements that don’t have associated document keys, it will fetch document keys for them as well

Once the agreements have new document keys, users will be able to perform all agreement actions on existing agreements sent by other users.

Note:

The v20 package improves the Fetch/Update Legacy Document Keys features (introduces in v19.4):

The two links are always available, never hidden under a private setting

Manages within governor limits. Will not fail for agreement count greater than 50k

Can execute batch apex job from developer console using the code

Will accept filters as input (can update a particular chunk of agreements from developer console).

Sends an email notification to the submitter on completion with status and data counts

What’s new in version 19

Manual adjustments that should be done after upgrade

Update processes to explicitly grant access to objects/fields

With the v19 release, the organization's CRUD and FLS settings on both standard and custom objects are enforced. As a result, many configured features must be updated to include explicit access to the various objects needed.

Two steps may be involved:

All features can be updated using a Permission Set to grant access to the Adobe Sign objects

Some features that must access Salesforce objects may require enablement of specific objects and/or fields

Please see the Manual Update listings below for the various features/processes that are impacted.

IP Range update

As Adobe Sign has expanded, the infrastructure has shifted to more robust data centers, and this has caused some changes in the IP ranges that your Salesforce organization needs to trust to ensure optimal communication between the services.

Below are the incremental changes from v18 to v19. Ensure that any sites configured are updated in addition to the core trusted networks.

ADD:

India:

13.126.23.0/27

REMOVE:

North America:

166.78.79.112/28

207.97.227.112/28

Your final list of approved IP ranges for the Adobe Sign service should look like this:

Add the Agreement Type field to the Agreement Template page layout

Add the parent lookup field called Agreement Type (Agreement_Type__c) to the Agreement Template Page Layout:

Select Agreement Template from the list of objects on the left side of the page

Select Page Layouts from the left rail

Click the Page Layout Name: Agreement Template Layout

Select the Fields option

Click the Agreement Type field and drag it onto the page layout

Click Save

Update Legacy Document keys if upgrading from a version older than v14 - Added in v19.4

When the Adobe Sign application for Salesforce is upgraded from versions lower than v14 to the current build, users might not be able to perform actions such as Delete, Cancel, View, Remind, or Update on the existing agreements that were sent by other users before upgrade.

Users may prompt an error when one of these actions is executed, similar to:

“INVALID_DOCUMENT_KEY” or “An internal server error has occurred”

This happens due to a legacy document key stylethat was used in versions of the application before version 14.

A one-time migration of those legacy keys is required. To this end, a new affordance as described below:

After completing the set-up steps, the following links will be available on the Adobe Sign Admin page:

Update Legacy Document Keys - Clicking this link will flush out the existing legacy document keys and fetch the new document keys for all the agreements existing in the org.

In case there are any agreements that don’t have associated document keys, it will fetch document keys for them as well

Once the agreements have new document keys, users will be able to perform all agreement actions on existing agreements sent by other users.

Note:

The links for Fetch Missing Document keys and Update Legacy Document keys are only visible when the admin upgrades from a version lower than v14 to v19.4.

If the admin updates a package between v14 and v19.2, the links are hidden by default. In this case, the admin can contact Adobe Sign Support to manually expose the links.

This action requires that you grant log in access to Adobe Sign Support.

Things to note:

With the v19 release, the organization's CRUD and FLS settings on both standard and custom objects are enforced. The App checks object and field level, read and write permissions. If the user doesn't have appropriate access, a permission denied error is shown.

After upgrading to v19, if a salesforce users gets permission denied error similar to:

Permission denied. Unable to insert field echosign_dev1__Contract__c in object: echosign_dev1__SIGN_Agreement__c

then the salesforce admin needs to add both read and write permissions to the agreement object, and for any custom fields they have created, to the relevant profiles.

Scroll down to the Custom Field-Level Security section and click the View actionfor the Agreement object

Provide Read and Edit access to relevant fields

New Tab:

v19 brings a new Agreement Types tab.

A new custom object called Agreement Type (Agreement_Type__c) has been introduced to define an agreement type. It has one standard Name field, but additional fields can be added later to define your own custom fields. An object is used instead of a simple text field because this allows a unique record to define a type, which is more flexible and extensible. It also separates the type from the agreement template and the agreement, so the agreement template can change without being tied to the type and multiple templates can set the same type.

A new parent lookup field called Agreement Type (Agreement_Type__c) has been added to the Agreement Template object, which points to the Agreement Type object. The field will appear in the Agreement Template Detail section on the agreement template page.

A new parent lookup field called Agreement Type (Agreement_Type__c) has been added to the Agreement object, which points to the Agreement Type object. The field will not appear on the Agreement editor page.

Automatic Status Updates are more secure:

v19 uses OAuth to establish the trusted relationship between Adobe Sign and Salesforce to facilitate the on-going automatic status updates to your agreements.

One new Custom Settings:

Add Signed PDF Link for Pushed Agreement - This setting applies only for pushed agreements sent outside of Salesforce. Enable this setting to add a link for signed PDF to the Agreement record.

And one setting removed:

Enable Send Written Signature To Fax – Adobe Sign no longer supports sending an agreement to a phone number. Written signatures instead follow the same process as electronic signature until the first signer has to apply their signature. Then they download, sign, scan and upload that file back to Adobe Sign.

Admins will have to enable My domain in order to use the Adobe Sign Custom Lightning Components.

The Salesforce file upload size has been reduced to 1MB. Because Adobe Sign uses Base64 encoding, your actual file size will need to be somewhat less than 1MB (~700KB). Larger documents should be sent from the Salesforce library and have large documents enabled

The Lightning environment does not support publisher actions

The Lightning page does not support field sets, so no custom fields can be added.

The Chatter feed does not work on the Lightning page

The Hide Sidebar for Agreement Editor Page setting does not work with the Lightning page layout

The Lightning Lock Security Service must be disable

Hierarchies do not work with groups

Access for users is more secure:

v18 uses a REST based API, and as a result, all actions are sent as the current context user (vs. Admin authenticated). Users will no longer be able to invoke actions for agreements (eg. Update, Remind) they are not party to.

API Users:

If you call the echosign_dev1.EchoSignApiUtilities.getSigningUrls API in the package, note that the simpleEsignUrl field on the EchoSignApiService.SigningUrl returned object is deprecated and will not be set. If you use this field, switch to using the esignUrl field instead.

New Adobe Sign Settings

Disable Group Recipient Type—Check this setting to disable Group as a Recipient Type on agreements.

With Fields selected, find and drag the Active field onto your page layout.

Click Save

New field values in version 18

Salesforce by default does not enable field values that were added to Adobe Sign for Salesforce when you upgrade from an older version. Therefore, you need to enable the following field values that were added in version 18:

Navigate to Setup > Create > Objects

Object: Add Recipient (echosign_dev1__Recipient_Template__c)

Fields:

Recipient_Message__c

Group_Recipient__c

Uniform_Index__c

Values to add:

New Picklist Field values:

Recipient_Type__c - Added: Group

Object: Recipient (echosign_dev1__SIGN_Recipients__c)

Fields:

Recipient_Message__c

Group_Recipient__c

Values to add:

New Picklist Field values:

Recipient_Type__c - Added: Group

Deprecated custom settings and fields in version 18

There are no deprecated custom settings in version 18.

New tab in version 18

The new Adobe Sign Admin tab is replacing the eSign Services Admin tab

Editing the page layout for a master object record

Select a record for a standard object type, such as Opportunity, from the Lightning navigation menu at the top of the window

2. Select Edit Page from the gear icon

3. In the Components panel on the left side, select AgreementPanel (same width as the highlights panel) or AgreementPanelWide (matches the width of the page) under Custom – Managed. The selected component is added to the preview view in the middle of the page. You can click and drag the panel to other positions on the page Panel, Panel Wide, and a couple other options.

4. On the right side, you’ll see Record Field Name and Agreement Template Record ID.

Leave Record Field Name blank. It will be used for non-standard and custom objects.

For Agreement Template Record ID, leave it blank to link the layout with templates that have Opportunity as a Master Object Type and templates that have a blank Master Object Type. Or, you can optionally list the templates—comma separated—that should be used.

5. Click Save. When prompted to Activate, click Activate

6. In the Activation for Opportunity Record Page dialog, select the Assign this page as the default record page option, andthen click Save.

Editing the page layout for a non-standard object record

Select a record for a non-standard object type, such as Case, from the Lightning navigation menu at the top of the window

2. Select Edit Page from the gear icon

3. In the Components panel on the left side, select AgreementPanel (same width as the highlights panel) or AgreementPanelWide (matches the width of the page) under Custom – Managed. The selected component is added to the preview view in the middle of the page. You can click and drag the panel to other positions on the page Panel, Panel side, and a couple other options.

4. On the right side, you’ll see Record Field Name and Agreement Template Record ID.

The Record Field Name should contain the API name of the lookup field from the Agreement object to your custom object.

If not entered and the record ID matches up to one of the standard lookup fields (Account, Opportunity, Contract, Lead, Contact, User), then that lookup relationship will be used.

For Agreement Template Record ID, leave it blank to link the layout which has the name of your custom object as a Master object type. Or, you can optionally list the templates—comma separated—that should be used.

5. Click Save. When prompted to Activate, click Activate

6. In the Activation for Opportunity Record Page dialog, select the Assign this page as the default record page option, andthen click Save.

What’s new in version 17

New settings in version 17

Review the new settings added in version 17 to determine if you want to enable any of these capabilities. To go to the settings, choose Develop > Custom Settings > (Manage) Document Cloud Settings.

Create Sign Deadline Reminder Event—Enable this setting to display Salesforce alerts reminding users when sent agreements are about to expire. Specify the number of days before agreement expiration that the alert is shown using the Days Sign Deadline Reminder Event setting.

Days Sign Deadline Reminder Event­—Enter a number of days and enable the Create Sign Deadline Reminder Event setting. This allows ‘agreement about-to-expire alerts’ to be shown to your users in Salesforce. Alerts are shown the specified number of days before agreement expiration.

Disable User Provisioning—Enable this setting to prevent users from being auto-provisioned with an Adobe user account when they send or manage agreements. This setting does not prevent the auto- provisioning of users that occurs when Update Agreement is clicked from the Agreement list.

Enable Post Sign Options—Enable this option to take your singers to a landing page of your choice. This makes the ‘Post Sign Redirect URL’ and ‘Post Sign Redirect Delay’ options available on the send agreement page. Signers of an agreement are redirected to the specified URL after they sign. For example, you could redirect them to your company web site or a survey page. This option can be made read only for senders using the Read Only Post Sign Options setting.

Enable Sender Signs Only—Enable this setting to display and enable the ‘Sender Signs Only’ option in the Recipients section of the send agreement page. When the ‘Sender Signs Only’ option is used, the agreement or document is presented to the sender to sign. This functionality is similar to the ‘Only I Sign’ functionality in Adobe services. This option can be set to read only using the Read Only Sender Signs Only setting.

Hide Sidebar for Agreement Editor Page—Enable this setting to hide the sidebar in the Agreement Editor page. The Agreement Editor page can be accessed by clicking the name of an agreement displayed in the sidebar, in the Agreements Home page, or in the list of agreements for a related object.

Read Only Post Sign Options—Enable this setting to display the ‘Post Sign Redirect URL’ and ‘Post Sign Redirect Delay’ options as read-only in the Recipients section of the send agreement page. This setting works in conjunction with the Enable Post Sign Options setting.

Read Only Sender Signs Only—Enable this setting to display the ‘Sender Signs Only’ option as read-only in the Recipients section of the send agreement page. This setting works in conjunction with the Enable Sender Signs Only setting.

New field values in version 17

There are no field values in version 17.

Deprecated custom settings and fields in version 17

There are no deprecated custom settings in version 17.

Agreement Template field values added in version 17

If you are using Agreement Templates and are upgrading from version 12, 13, 14, 15, or 16, edit the Agreement Template layout and drag the new fields introduced in version 17 to the layout.

Other field values added in version 17

Salesforce by default does not enable field values that were added to EchoSign (now eSign services) for Salesforce version 17 when you upgrade from an older version to the latest version. Therefore, you need to add the following field values that were added in version 17:

Object: Add File Attachment

(Attachment_Template__c)

Field: Attachment Type (Type__c)

Value to add: Quote Document from Master Quote

Quote Document from Opportunity Quote

Runtime Variable

What’s new in version 16

Enhanced security with OAuth 2.0

To improve data security, Adobe Sign now uses OAuth 2.0 to authenticate your eSign services account within Salesforce. This new protocol lets Salesforce talk to Adobe Sign without requesting your password. Since sensitive information is not being shared directly between the apps, your account is less likely to be compromised. This improvement will not impact your implementation, but you will need to do a one-time setup to authorize your installed Salesforce package to communicate with Adobe Sign.

New settings in version 16

There are no new settings in version 16.

Agreement Template field values added in version 16

There are no new template field values in version 16.

What’s new in version 15

New settings in version 15

Review the new settings added in version 15 to determine if you want to enable any of these capabilities. To go to the settings, choose Develop > Custom Settings > (Manage) EchoSign Settings.

2. Add the following version 15 field to the Agreement Options section:

Signature Flow

Manage and send agreements in batch in version 15

Version 15 introduces new functionality for sending agreements, deleting agreements, sending reminders, and managing agreements in batch. To enable these Batch Agreement buttons after upgrading:

1. Choose Setup > Create > Objects > Agreement > Search Layouts.

2. Edit the Search Results and Agreements List View layouts.

3. Add the five buttons.

4. Click Save.

New field values in version 15

Salesforce by default does not enable field values that were added to EchoSign (now Adobe Sign services) for Salesforce version 15 when you upgrade from an older version to the latest version.

Therefore, you need to enable the following field values that were added in version 15:

Object: Add File Attachment(Attachment_Template__c)

Field: Attachment Type
(Type__c)

Values to add:

Document from EchoSign Library

Object: Agreement (SIGN_Agreement__c)

Field: Agreement Status
(Status__c)

Values to add:

Created

Object: Agreement Template(Agreement_Template__c)

Field: Language (Language__c)

Values to add:

Vietnamese (Vietnam)

Object: EchoSign Field Mapping(SIGN_Field_Mapping__c)

Field: Map on Events
(Map_on_Events__c)

Values to add:

Expired

Object: EchoSign File Mapping(SIGN_File_Mapping__c)

Field: Map on Events
(Map_on_Events__c)

Values to add:

Expired

Delete custom settings and fields deprecated in version 15

In version 15, some EchoSign (now Adobe Sign services) custom settings and fields were deprecated and are no longer relevant.

Note:

Before deleting fields, make sure that the values of these fields are not being used anywhere in your organization, for example, reports. This action is permanent and cannot be undone.

Deleting deprecated fields

After the upgrade, you should delete the deprecated custom settings by choosing Setup > Develop > Custom Settings > EchoSign Settings. Under the Actions column, click Del for the following fields:

echosign_dev1__API_Key__c

echosign_dev1__Enable_Suggest_Revisions_Field__c

echosign_dev1__Reset_API_Security_Key__c

echosign_dev1__Security_Shared_Token__c

echosign_dev1__API_Server_URL__c

echosign_dev1__Server_URL__c

Deleting deprecated custom settings

After the upgrade, you should delete the deprecated fields by choosing Setup > Create > Object. Select the object from the following list, navigate to the Custom Fields section, and click Del from the Actions column.

Agreement Template

echosign_dev1__Suggest_Revisions__c

Agreement

echosign_dev1__Enable_Revisions__c

echosign_dev1__Recipient_Signing_Order__c

echosign_dev1__Merge__c

What’s new in version 14

New settings in version 14

Review the settings added in version 14 to determine if you want to enable any of these capabilities. To go to the settings, choose Develop > Custom Settings > (Manage) EchoSign Settings.

Read Only Account—Make the Account field a read-only agreement field. This is useful if you want to prepopulate the field but not allow the sender to edit it.

Read Only Agreement Name—Make the Agreement Name field a read-only agreement field.

If you are using version 12, remove the Password to Sign Agreement field used in version 12, as the previous fields replace it. Also, the option to Allow Signers to Suggest Revisions is no longer available in EchoSign (now Adobe Sign services), so you can remove it if it appears in your Agreement Template UI.

Other field values added in version 14

Salesforce by default does not enable field values that were added to EchoSign (now Adobe Sign services) for Salesforce version 14 when you upgrade from an older version to the latest version. Therefore, you need to add the following field values that were added in version 14:

Object: Add File Attachment
(Attachment_Template__c)

Field: Attachment Type
(Type__c)

Values to add:

Quote Document from Opportunity Quote

Runtime Variable

Object: Add Recipient (Recipient_Template__c)

Field: Source of Recipient
(Type__c)

Values to add:

All Opportunity Contact Roles

Account Primary Contact Role

Account Contact Role

All Account Contact Roles

Runtime Variable

Object: Agreement (SIGN_Agreement c)

Field: Language

(AgreementLocale__c)

Values to add:

Czech (Czech Republic)

Turkish (Turkey)

Object: Agreement Template
(Agreement_Template__c)

Field: Language (Language__c)

Values to add:

Czech (Czech Republic)

Turkish (Turkey)

What’s new in version 13

New settings in version 13

Review the settings added in version 13 to determine if you want to enable any of these capabilities. To go to the settings, choose Develop > Custom Settings > (Manage) EchoSign Settings.

Auto-Sync Group Mappings—Automatically move the correct EchoSign groups when their Salesforce user profiles are updated.

Disable Knowledge Based Authentication—Hide the knowledge-based authentication (KBA) identity verification option for agreements. This is a signer identity verification method that requires signers to provide and verify personal information to sign the document. Usage of this feature is limited and may incur added costs. Also, make sure your account send settings on EchoSign.com have KBA enabled so you can use it in Salesforce.

Disable Web Identity Verification—Hide the web identity verification option for agreements. Web identity verification requires signers to verify their identity by signing into one of the following sites: Facebook, Google, LinkedIn, Twitter, Yahoo!, or Microsoft Live. Also, make sure your account send settings on echosign.adobe.com have web identity enabled so you can use it in Salesforce.

Enable Mapping Error Notification—Send email notifications to the data mapping or merge mapping owner any time there are errors when the mappings are executed.

Enable Recipient Approver Role—Enable the option to mark any recipient as an Approver. Approvers view and approve the document, but they are not required to sign it.

Enable Separate Signer Identity Methods—Enable the option to select different identity verification methods for recipients in your EchoSign (now Adobe Sign services) account and those outside your eSign services account. This applies to KBA, web identity verification, and password to sign. For example, you can require that a customer be verified with Knowledge Based Identity before signing the document but require that your sales manager instead provide a password to sign the document. If you don’t select this option, then all signers or approvers will verify using the same method, as selected by the sender.

Agreement Template field values added in version 13

If you are using Agreement Templates and are upgrading from version 12, edit the Agreement Template layout and drag the fields introduced in version 13 to the layout.

2. Add the following version 13 fields to the Agreement Security Options section:

External Signers Verification Method

Internal Signers Verification Method

Other field values added in version 13

Salesforce by default does not enable field values that were added to EchoSign (now Adobe Sign services) for Salesforce version 13 when you upgrade from an older version to the latest version. Therefore, you need to add the following field values that were added in version 13: