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.

ملاحظة:

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

If you are on version 18 or older, please upgrade to the new package to ensure the continuation of support.

Upgrading from a previous release

تحذير:

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

تحذير:

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:

  1. Log into Salesforce as your account admin ID
  2. Navigate to Setup > Platform Tools > Apps > Installed Packages
Installed Package

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.

ملاحظة:

If you are upgrading from version 12 or prior and are sending large document transactions (greater than 2.0 MB), you must configure Salesforce to send large documents for signature. 

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.

For more information on managed versus unmanaged packages, visit: http://www.salesforce.com/us/developer/docs/packagingGuide/Content/packaging_about_packages.htm.

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.

Option 1: Install the new version and hide the old

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.

 

ملاحظة:

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: Export/import data from the old package into a new package

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:

1. Export the agreement data from the existing unmanaged package using a data loader tool like Jitterbit or Dataloader.io or the standard Salesforce Data Loader.

2. Uninstall your current unmanaged package.

3. Install the latest managed package version from the AppExchange.

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.

ملاحظة:

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.

For questions regarding upgrading from the unmanaged packages, contact your Adobe client success manager.

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
  • Install the Adobe Sign for Salesforce upgrade package from the App store
  • Configure the application

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

  1. Click here to access the Adobe Sign application package on the Salesforce AppExchange.
  2. Click the Get It Now button.
  3. Select Log in to the AppExchange and enter your credentials to continue.
  4. Determine where you would like to install the upgrade (production or sandbox).
  5. 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.
  6. When prompted to login to your Salesforce organization, enter your Salesforce Username and Password then click Login in to Salesforce.
  7.  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.

  1. Navigate to Setup > Platform Tools > Apps > Installed Packages
  2. Click the Configure link for the Adobe Sign package
    • The Adobe Sign for Salesforce Setup Wizard should launch.

ملاحظة:

If the Setup Wizard doesn’t launch automatically:

  1. Navigate to the Adobe Sign Admin tab
  2. Click the Launch Setup Wizard link

The Launch Setup Wizard

    3. In “Step 1: Link your Adobe account to Salesforce” of the Setup Wizard:

  • Click Sign in to Adobe 
  • Log in with your Adobe Sign admin user
  • Allow Access if challenged
    • You should get a message saying Success! You have successfully authorized your Adobe account.

    4. Click Next on the successful Step 1 notification

    5. In “Step 2: Enable Adobe Sign Automatic Status Updates”, click the Enable button

  • When challenged to allow access to Adobe Sign, click Allow
  • A message should pop up: Success! You have successfully enabled Automatic Status Updates for your account.

    6. Click Next at the bottom of the page to proceed

    7. When the Setup Wizard displays Congrats! Your setup is complete, click Done.

ملاحظة:

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

Be Advised - The order of updates to the Adobe Sign for Salesforce objects has changed

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

  1. Attachments 
  2. Recipients 
  3. Agreement (status and its other attributes)
  4. Agreement Events 
  5. Chatter Feeds 

Be Advised - Backward Compatibility Changes

  • 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
  • Maximum size of callout request or response is limited to 12MB for asynchronous Apex as per Salesforce governor limits: https://developer.salesforce.com/docs/atlas.en-us.210.0.apexcode.meta/apexcode/apex_gov_limits.htm
    • Documents larger than 12MB can not be fetched from Sign due to above limit.
  • Agreement event descriptions have changed. It now matches the description as returned by Sign API and with the audit reports.
  • The update process is now run as a native Apex batch process (which is an asynchronous process) within Salesforce
    • Before it was an update using API calls from outside of Salesforce
    • Triggers off these status updates which kick off async processes no longer work because Salesforce limits calling another async process from an already running async process
  • Prior to v21, the agreement attribute updates were split up into separate update calls, now agreement object is updated all in one transaction.
  • Prior to v21, failed agreements could be only retried by doing a manual update from within Salesforce
    • Now updates are more reliable as the Sign backend automatically retries failed events for a specified number of times.
  • Manual updates now update all aspects of agreements including the related objects.
  • Push agreements now run in async mode, same as regular updates and additional attributes are updated, the same as regular updates.
  • There are new settings introduced to enable disable updates of different aspects of the agreement.

Required - Re-Run the OAuth wizard after upgrading the package

After the upgrade is completed:

  • Navigate to the Adobe Sign Admin tab 
  • Click the Enable Automatic Status Updates link to reestablish the OAuth connection to Adobe Sign
  • Click Enable
  • Click Allow to allow access
enable_status_updates

Callback Users Updated - Possible action needed

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.

New Push Mapping behavior

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

Chatter feeds improved

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)

Improved representation of the Agreement View

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.

New Agreement Status - Waiting for My Delegation

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.

Agreement Template - Expiration Field changed to a text field

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.

Agreement Template - Account/Opportunity/Contract Fields have been removed

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

Agreement Template - "Sender Signature Order" has been removed

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.

Agreement Template - Signature Flow has been removed

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.

Settings Deprecated in v21

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

Large Document Service

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.

ملاحظة:

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:

 

1. Upgrade the Adobe Sign for Salesforce package to 20.9 (or later)

 

2. Create the new Callback User profile

ملاحظة:

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)
    • Edit the profile
      • Under Custom Tab Settings, ensure that both Adobe Sign Admin tabs are set to Default On
      • Under Custom Object Permissions, enable all values for the Agreement object
      • Ensure these Visualforce pages are enabled 
        • echosign_dev1.EchosignAdmin
        • echosign_dev1.SalesforceOAuthPage
      • Enable the echosign_dev1. AgreementAttachmentDownloadService Apex class
    • Save the profile

 

3. Enable the Attachment Service Invocation Count for the Callback User profile

  • Navigate to Object Manager > Agreement > Fields & Relationships 
  • Click on the Field Label Attachment Service Invocation Count
  • Click the Set Feild-Level Security button
  • Enable both Visible and Read-Only for the Callback User profile
  • Click Save

 

4. Create a new 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
  • Verify the user to establish the known password
  • Log out of Salesforce

 

5. Define the Callback User

  • Log in to Salesforce as the Callback User
  • Navigate to the Adobe Sign Admin page
  • Click Link an Account under the Callback User header
    • An Allow Access? page is presented seeking to link the currently authenticated userID
  • Click Allow
    • Verify that the callback user is correctly linked
  • Log out of Salesforce

 

5. Update the existing Site 

  • Log in as your Salesforce Admin
  • Navigate to Platform Tools > User Interface > Sites and Domains > Sites
  • Click the Site Label to open the site details
  • Click the Public Access Settings button
  • 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

Push Agreements

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.

ملاحظة:

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

ملاحظة:

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
    • Save the permission set

 

3. Upgrade the Adobe Sign for Salesforce package to 20.9 (or later)

 

4. Define the Callback User

  • Once the upgrade is complete, log in to Salesforce as the Callback User
  • Navigate to the Adobe Sign Admin page (App Launcher > Adobe Sign for Salesforce > Adobe Sign Admin)
  • Click Link an Account under the Callback User header
    • An Allow Access? page is presented seeking to link the currently authenticated userID
  • Click Allow
    • Verify that the callback user is correctly linked
  • Log out of Salesforce

 

5. Update the existing Site 

  • Log in to Salesforce as your admin user
  • Navigate to Platform Tools > User Interface > Sites and Domains > Sites
  • Click the Site Label to open the site details
  • Click the Public Access Settings button
  • Click the View Users button
  • Click on the Full Name link of the Site user
  • 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

Ensure that "My Domain" is configured (Required for Lightning)

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.

Add new recipient roles to the Agreement page (Optional)

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 the roles in Adobe Sign:

  1. Log in to Adobe Sign as an administrator
  2. Navigate to Account > Account Settings > Send Settings > Allowed Recipient Roles
  3. Enable the roles you need to support
  4. Click Save
navigate_to_rolesinadobesign

 

Enable the roles in the custom settings (Salesforce):

  1. Log into Salesforce as and administrator
  2. Navigate to Setup > Platform Tools > Custom Code > Custom Settings
  3. Click the label Adobe Sign Settings
  4. Click the Manage button
  5. Click New (or Edit, if you have configured settings before)

The setting values are: 

  • 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

ملاحظة:

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

Update picklist values to support new workflow roles (Optional)

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.

1. Navigate to Setup > Platform Tools > Objects and Fields > Object Manager

2. Select Recipient form the list on the left

3. Select Fields & Relationships form the left rail

4. Select the Recipient Role field

5. Scroll down the page to the Values section, and select New

6. Enter the new Role values that you have enabled. Valid values are:

  • Acceptor
  • Form Filler
  • Certified Recipient
  • Delegate to Acceptor
  • Delegate to Form Filler
  • Delegate to Certified Recipient

7. Click Save when done

role_picklist

 

The resulting picklist should look like this (assuming you added all roles):

full_role_picklist

 

Localize the role statuses through the translation workbench:

1. Navigate to: Setup > Platform Tools > User Interface > Translation Workbench > Translate

  • Select the Language that you want to localize to
  • Select the Setup Component as Picklist Value
  • Select Object as Recipient
  • In the Master Picklist table, expand the Recipient Role folder
  • 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

translate_recipientroles

Changes to how linked files are displayed (Informational)

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:

 

document_link_update-statusintext

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

document_link_update-nostatusintext

 

  • 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:

real-time_pdf_versions

Update tool tips for Chatter settings (Optional)

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

  1. Navigate to Setup > Platform Tools > Custom Code > Custom Settings
  2. Click the label Adobe Sign Chatter Settings
  3. Click the Edit link next to Post when Agreement Sent
edit_chatter_setting

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

5. Click Save

chatter_help_tectchange

Fetch and Update Legacy Document Keys (if updating from version 13 or older)

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:

  • Fetch Missing Document Keys – Clicking this link will perform a batch action for fetching missing document keys for existing agreements
  • 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.

ملاحظة:

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

fetch_and_updatekeys

What’s new in version 19

v19 Feature, Setting and Field Changes

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:

list_of_ip_ranges


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:

  • Navigate to Setup > Platform Tools > Objects and Fields > Object Manager
  • 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

 

add_the_agreementtypefieldtothepagelayout


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 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:

  • Fetch Missing Document Keys – Clicking this link will perform a batch action for fetching missing document keys for existing agreements
  • 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.

ملاحظة:

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.

  • Navigate to: Setup > Administration > Users > Profile > {Profile name} 
  • Scroll down to the Custom Field-Level Security section and click the View action for the Agreement object
  • Provide Read and Edit access to relevant fields
enable_agreementfieldlevelsecurity
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. 

>> More details on the Written Signature

 

Deprecated custom settings and fields in version 19

There is one deprecated custom settings in version 19: Enable Send Written Signature To Fax  

New tab in version 19

There is one new tab in v19: Agreement Types

Deprecated tab in version 19

There are no deprecated tabs in v19.

Other field values added in version 19

None.

Setting up the Agreement page style

If you are a new customer, the “Lightning” page style is the default, and is the layout that will be developed going forward. 

Upgrading customers are strongly recommended to adopt use of the Lightning page to ensure that new features are available as development continues to improve the product.

That said, there may be very good reasons you need to stay on one of the older page layouts. Refer to the guide on adjusting your Salesforce page layout to determine if moving to the Lightning page is best.

Manual updates required for Group Mappings

Any user directly interacting with Group Mappings, will need to ensure that they have the correct permissions.

  • This is best achieved by adding the Adobe Sign Admin permission set to the user
  • The user's profile must have the View Setup and Configuration permission enabled

 

Below is an explicit listing of the objects, and the required fields, if using the permission set is not acceptable for any reason:

 

Object Field Required values Standard/Custom Adobe Sign Permission Set
Echo Sign Group Mapping   Read, Delete, Create, Modify Adobe Sign - Custom Adobe Sign Admin
  All Fields Read, Modify    
         
EchoSign User Sync Result   Read, Delete, Create Adobe Sign - Custom Adobe Sign Admin
  All Fields Read, Modify    

Manual updates required for API Services

Any user that uses the Adobe Sign API will require the Adobe Sign User permission set.

 

Below is an explicit listing of the objects, and the required fields, if using the permission set is not acceptable for any reason:

Object Field Required values Standard/Custom Adobe Sign Permission Set
Recipient   Read Adobe Sign - Custom Adobe Sign User
  Status Read    
  Order Number Read    
  Source Recipient Read    
  Agreement      
         
Agreement   Read Adobe Sign - Custom Adobe Sign User
  Authoring Read    

Manual updates required for the Self Sign Component

For users to interact with the Self Signing component for Adobe Sign:

  • The Adobe Sign User permission set should be applied to the user
  • The Salesforce Contact object must have Read enabled
    • The Email field on the Contact object must have Read enabled

 

Below is an explicit listing of the objects, and the required fields, if using the permission set is not acceptable for any reason:

Object Field Required values Standard/Custom Adobe Sign Permission Set
Contact   Read Salesforce -Standard  
  Email Read    
         
Agreement   Read Adobe Sign - Custom Adobe Sign User
  Name Read    
  Status Read    
  Date Signed Read    
  Error Message Read    
  Signed PDF Read    
  Document Key Read    
         
Agreement Template   Read Adobe Sign - Custom Adobe Sign User
  All Fields Read    
         
Agreement Type   Read Adobe Sign - Custom Adobe Sign User
  Name Read    
         
Recipient   Read Adobe Sign - Custom Adobe Sign User
  Agreement Read    
  Status      
  Date Time Complete      

Manual updates required for Agreement Template Batch

Users that interact with the Agreement Templates require:

  • The Adobe Sign Admin permission set to be added
  • Access to all fields for the specified Master Object in Salesforce

 

Below is an explicit listing of the objects, and the required fields, if using the permission set is not acceptable for any reason:

Object Field Required values Standard/Custom Adobe Sign Permission Set
Master Object Specified By User        
  All Fields Specified by User Read N/A  
         
Agreement template   Read Adobe Sign - Custom Adobe Sign Admin
  Name Read    
  Master Object Type Read    

Manual updates required for Batch Actions

Users that trigger batch actions will require:

  • The Adobe Sign Admin permission set

 

Below is an explicit listing of the objects, and the required fields, if using the permission set is not acceptable for any reason:

Object Field Required values Standard/Custom Adobe Sign Permission Set
Agreement   Read Adobe Sign - Custom Adobe Sign Admin
  Document Key Read    
  Cancel Delete Reason Read    
  Cancel Delete Notify Signer Read    
  Partner Server URL Read    
  Status Read    
  Last Event ID Read    

Manual updates required for S1 Mobile

Any user that uses Adobe Sign through S1 Mobile will require:

  • The Adobe Sign User permission set
  • The Salesforce Opportunity object must have Read enabled
    • The Name field on the Opportunity object must have Read enabled
  • The Salesforce Account object must have Read enabled
    • The Name field on the Account object must have Read enabled
  • The Salesforce Contract object must have Read enabled
    • The Name field on the Contract object must have Read enabled
    • The Contract Number field on the Contract object must have Read enabled
  • The Salesforce Contact object must have Read enabled
    • The Name field on the Contact object must have Read enabled
    • The Email field on the Contact object must have Read enabled
  • The Salesforce Lead object must have Read enabled
    • The Name field on the Lead object must have Read enabled
    • The Email field on the Lead object must have Read enabled
  • The Salesforce Document object must have Read enabled
    • The Name field on the Document object must have Read enabled
    • The Type field on the Document object must have Read enabled
    • The Content Type field on the Document object must have Read enabled
    • The Body field on the Document object must have Read enabled

 

Below is an explicit listing of the objects, and the required fields, if using the permission set is not acceptable for any reason:

Object Field Required values Standard/Custom Adobe Sign Permission Set
Opportunity   Read Salesforce -Standard  
  Name Read    
         
Account   Read Salesforce -Standard  
  Name Read    
         
Contract   Read Salesforce -Standard  
  Name Read    
  Contract Number Read    
         
Contact   Read Salesforce -Standard  
  Name Read    
  Email Read    
         
Lead   Read Salesforce -Standard  
  Name Read    
  Email Read    
         
Document   Read Salesforce -Standard  
  Name Read    
  Type Read    
  Content Type Read    
  Body Read    
         
Agreement Event   Read Adobe Sign - Custom Adobe Sign User
  All Fields Read    
         
Agreement Template   Read Adobe Sign - Custom Adobe Sign User
         
Agreement   Read, Create, Delete, Modify Adobe Sign - Custom Adobe Sign User
  All Fields Create, Modify    
         
Recipient   Read, Create, Delete, Modify Adobe Sign - Custom Adobe Sign User
  All Fields Create, Modify    
         
Library Templates   Read, Create, Delete, Modify Adobe Sign - Custom Adobe Sign User
  All Fields Create, Modify    

Manual updates required for Setup & Administration - Setup

User that access to the Administration tab require the Adobe Sign Admin permission set.

 

Below is an explicit listing of the objects, and the required fields, if using the permission set is not acceptable for any reason:

Object Field Required values Standard/Custom Adobe Sign Permission Set
Agreement Template   Read Adobe Sign - Custom Adobe Sign Admin
         
Agreement   Read Adobe Sign - Custom Adobe Sign Admin
         
Document   Read Adobe Sign - Custom Adobe Sign Admin
  Body Read    

Manual updates required for Publisher Actions - Setup & Adm

Users that leverage the Publisher actions require:

  • The Adobe Sign User permission set
  • The system permission Insert System Field Values for Chatter Feeds enabled 
  • The Salesforce Opportunity object must have Read enabled
    • The Name field on the Opportunity object must have Read enabled
  • The Salesforce Account object must have Read enabled
    • The Name field on the Account object must have Read enabled
  • The Salesforce Contact object must have Read enabled
    • The Name field on the Contact object must have Read enabled
    • The Email field on the Contact object must have Read enabled
  • The Salesforce Lead object must have Read enabled
    • The Name field on the Lead object must have Read enabled
    • The Email field on the Lead object must have Read enabled
  • The Salesforce Document object must have Read enabled
    • The Name field on the Document object must have Read enabled
    • The Type field on the Document object must have Read enabled
    • The Content Type field on the Document object must have Read enabled
    • The Body field on the Document object must have Read enabled
  • The Salesforce Quote object must have Read enabled

 

Below is an explicit listing of the objects, and the required fields, if using the permission set is not acceptable for any reason:

Object Field Required values Standard/Custom Adobe Sign Permission Set
Contact   Read Salesforce -Standard  
  Name Read    
  Email Read    
         
Lead   Read Salesforce -Standard  
  Name Read    
  Email Read    
         
Opportunity   Read Salesforce -Standard  
  Name Read    
         
Account   Read Salesforce -Standard  
  Name Read    
         
Document   Read Salesforce -Standard  
  Name Read    
  Content Type Read    
  Body Read    
  Type Read    
         
Quote   Read Salesforce -Standard  
         
Agreement   Create, Modify Adobe Sign - Custom Adobe Sign User
  All Fields Modify    
         
Agreement Template   Read Adobe Sign - Custom Adobe Sign User
  Password Read    
  Name Read    
  Default Read    
         
Recipient   Create Adobe Sign - Custom Adobe Sign User
  All Fields Modify    
         
Library Templates   Create Adobe Sign - Custom Adobe Sign User
  All Fields Modify    

Manual updates required for the Agreement Template Editor

Users that edit Templates will require:

  • The Adobe Sign Admin permission set
  • The Salesforce Contact object must have Read enabled
  • The Salesforce Lead object must have Read enabled
  • The Salesforce Document object must have Read enabled
    • The URL field on the Document object must have Read enabled

 

Below is an explicit listing of the objects, and the required fields, if using the permission set is not acceptable for any reason:

Object Field Required values Standard/Custom Adobe Sign Permission Set
Contact   Read Salesforce -Standard  
         
Lead   Read Salesforce -Standard  
         
Document   Read Salesforce -Standard  
  URL Read    
         
Agreement Template   Read, Delete, Create, Modify Adobe Sign - Custom Adobe Sign Admin
  All Fields Read, Modify    
         
Add Recipients   Read, Delete, Create, Modify Adobe Sign - Custom Adobe Sign Admin
  All Fields Read, Modify    
         
File Attachments   Read, Delete, Create, Modify Adobe Sign - Custom Adobe Sign Admin
  All Fields Read, Modify    
         
Add Form Field Template   Read, Delete, Create, Modify Adobe Sign - Custom Adobe Sign Admin
  All Fields Read, Modify    
         
Map Data Into Agreement   Read, Delete, Create, Modify Adobe Sign - Custom Adobe Sign Admin
  All Fields Read, Modify    

Manual updates required for the Agreement Template Processor

The Agreement Template Processor requires:

  • The Adobe Sign Admin permission set
  • The Salesforce Contact object must have Read enabled
    • The Mobile Phone field on the Contact object must have Read enabled
  • The Salesforce Lead object must have Read enabled
    • The Mobile Phone field on the Lead object must have Read enabled
  • The Salesforce Opportunity object must have Read enabled
  • The Salesforce Account object must have Read enabled
  • The Salesforce Group object must have Read enabled
  • The Salesforce Quote object must have Read enabled

 

Below is an explicit listing of the objects, and the required fields, if using the permission set is not acceptable for any reason:

Object Field Required values Standard/Custom Adobe Sign Permission Set
Contact   Read Salesforce -Standard  
  Mobile Phone Read    
         
Lead   Read Salesforce -Standard  
  Mobile Phone Read    
         
Opportunity    Read Salesforce -Standard  
         
Account   Read Salesforce -Standard  
         
Quote   Read Salesforce -Standard  
         
Attachment   Access based on parent record.    
         
Agreement   Create, Modify Adobe Sign - Custom Adobe Sign User
  Signature Type Modify    
  Status Modify    
  Days Until Signing Deadline Modify    
  Enable Automatic Reminders Modify    
  Remind Recipient Modify    
  Recipient Addresses Modify    
  More Recipients Modify    
  Signature Order Modify    
  Authoring Modify    
  Process Template Modify    
         
Recipient   Create Adobe Sign - Custom Adobe Sign User
  Recipient Type Modify    
  Recipient Role Modify    
  Order Number Modify    
  Email Address Modify    
         
Library Template   Create Adobe Sign - Custom Adobe Sign User
  All Fields Modify    
         
         
Agreement Type    Read Adobe Sign - Custom Adobe Sign Admin
         
Agreement Template   Read Adobe Sign - Custom Adobe Sign Admin
  All Fields Read    
         
Add Recipients   Read Adobe Sign - Custom Adobe Sign Admin
  All Fields Read    
         
File Attachments   Read Adobe Sign - Custom Adobe Sign Admin
  All Fields Read    
         
Add Form Field Template   Read Adobe Sign - Custom Adobe Sign Admin
  All Fields Read    
         
Map Data Into Agreement   Read Adobe Sign - Custom Adobe Sign Admin
  All Fields Read    

Manual updates required for the Agreement Editor

Users that edit agreements require:

  • The Adobe Sign User permission set
  • The Salesforce Lead object must have Read enabled
    • The Company field on the Lead object must have Read enabled
  • The Salesforce Event object must have Create enabled
    • All fields on the Event object must have Modify enabled

 

Below is an explicit listing of the objects, and the required fields, if using the permission set is not acceptable for any reason:

Object Field Required values Standard/Custom Adobe Sign Permission Set
Lead   Read Salesforce -Standard
 
  Company Read    
         
Event   Create Salesforce -Standard  
  All Fields Modify    
         
Agreement   Read, Create, Modify, Delete Adobe Sign - Custom Adobe Sign User
  All Fields Read, Modify    
         
Recipient   Read, Create, Modify, Delete Adobe Sign - Custom Adobe Sign User
  Agreement Read    
  Status Read    
  Date Time Completed Read    
  Order Number Read    
  Recipient Type Read    
  Agreement Read    
  Email Address  Read    
  Recipient Type Modify    
  Recipient Role Modify    
  Order Number Modify    
  Email Address Modify    
         
Library Template   Create, Modify, Delete Adobe Sign - Custom Adobe Sign User
  All Fields Read, Modify    
         
Agreement Type    Read Adobe Sign - Custom Adobe Sign User
  Name Read    
         
Agreement Template   Read Adobe Sign - Custom Adobe Sign User
  Agreement Type Read    
  Name Read    
  Default Read    
  Auto Send Read    
         
Signed Agreement   Read    
         
Merge Mapping   Read Adobe Sign - Custom Adobe Sign User

Manual updates required for the Merge Mapping Editor

Users that edit the Merge Mappings require:

  • The Adobe Sign Admin permission set
  • Any object/field that the merge maps accesses requires Read and Modify enabled

 

Below is an explicit listing of the objects, and the required fields, if using the permission set is not acceptable for any reason:

Object Field Required values Standard/Custom Adobe Sign Permission Set
Any object which is mapped to.   Read, Modify    
  Any field which is mapped to. Read, Modify    
         
Agreement   Read Adobe Sign - Custom Adobe Sign Admin
  Document Key Read    
         
Form Field Import   Read, Delete, Create, Modify Adobe Sign - Custom Adobe Sign Admin
  All Fields Read, Modify    
         
Form Field Mapping   Read, Delete, Create, Modify Adobe Sign - Custom Adobe Sign Admin
  All Fields Read, Modify    
         
Form Field Mapping Entry   Read, Delete, Create, Modify Adobe Sign - Custom Adobe Sign Admin
  All Fields Read, Modify    
         
Form Field Child Mapping   Read, Delete, Create, Modify Adobe Sign - Custom Adobe Sign Admin
  All Fields Read, Modify    
         
Form Field Child Mapping Entry   Read, Delete, Create, Modify Adobe Sign - Custom Adobe Sign Admin
  All Fields Read, Modify    
         
Merge Mapping   Read, Delete, Create, Modify Adobe Sign - Custom Adobe Sign Admin
  All Fields Read, Modify    

Manual updates required for the Merge Mapping Processor

Users that leverage merge mappings require:

  • The Adobe Sign User permission set
  • The Salesforce Account object must have Read enabled
    • The Name field on the Account object must have Read enabled
  • The Salesforce Opportunity object must have Read enabled
    • The Name field on the Opportunity object must have Read enabled
  • Any object/field that the merge maps accesses requires Read and Modify enabled

 

Below is an explicit listing of the objects, and the required fields, if using the permission set is not acceptable for any reason:

Object Field Required values Standard/Custom Adobe Sign Permission Set
Any object which is mapped to   Read, Modify    
  Any field which is mapped to Read, Modify    
         
Account        
  Name Read Salesforce -Standard  
         
Opportunity        
  Name Read Salesforce -Standard  
         
Agreement   Read Adobe Sign - Custom Adobe Sign User
  Document Key Read    
  Additional Options Read    
  Name Read    
  Merge Mapping Read    
  Merge Mapping Error Read    
  Merge Mapping Result Read    
  Account Read    
  Opportunity Read    
         
Form Field Import   Read Adobe Sign - Custom Adobe Sign User
  All Fields Read    
         
Form Field Mapping   Read Adobe Sign - Custom Adobe Sign User
  All Fields Read    
         
Form Field Mapping Entry   Read Adobe Sign - Custom Adobe Sign User
  All Fields Read    
         
Form Field Child Mapping   Read Adobe Sign - Custom Adobe Sign User
  All Fields Read    
         
Form Field Child Mapping Entry   Read Adobe Sign - Custom Adobe Sign User
  All Fields Read    
         
Merge Mapping   Read Adobe Sign - Custom Adobe Sign User
  All Fields Read    

Manual updates required for the Data Mapping Editor

Users that edit the Data Mappings require:

  • The Adobe Sign Admin permission set
  • Any object/field that the merge maps accesses requires Read and Modify enabled

 

Below is an explicit listing of the objects, and the required fields, if using the permission set is not acceptable for any reason:

Object Field Required values Standard/Custom Adobe Sign Permission Set
Any object which is mapped to   Read, Modify    
  Any field which is mapped to Read, Modify    
         
Agreement   Read Adobe Sign - Custom Adobe Sign Admin
  Document Key Read    
         
File Mapping   Read, Delete, Create, Modify Adobe Sign - Custom Adobe Sign Admin
  All Fields Read, Modify    
         
Field Mapping   Read, Delete, Create, Modify Adobe Sign - Custom Adobe Sign Admin
  All Fields Read, Modify    
         
Object Mapping   Read, Delete, Create, Modify Adobe Sign - Custom Adobe Sign Admin
  All Fields Read, Modify    
         
Data Mapping   Read, Delete, Create, Modify Adobe Sign - Custom Adobe Sign Admin
  All Fields Read, Modify    

Manual updates required for the Data Mapping Processor

Data Mapping processing requires:

  • The Adobe Sign Integration User permission set
  • Any object/field that the data maps accesses requires Read and Modify enabled
  • The Salesforce Attachment object requires access based on the parent record

 

Below is an explicit listing of the objects, and the required fields, if using the permission set is not acceptable for any reason:

Object Field Required values Standard/Custom Adobe Sign Permission Set
Any object which is mapped to   Read, Modify    
  Any field which is mapped to Read, Modify    
         
Attachment   Access based on parent record.    
         
Agreement   Read, Modify Adobe Sign - Custom Adobe Sign Integration
  All Fields Read, Modify    
         
File Mapping   Read Adobe Sign - Custom Adobe Sign Integration
  All Fields Read    
         
Field Mapping   Read Adobe Sign - Custom Adobe Sign Integration
  All Fields Read    
         
Object Mapping   Read Adobe Sign - Custom Adobe Sign Integration
  All Fields Read    
         
Data Mapping   Read Adobe Sign - Custom Adobe Sign Integration
  All Fields Read    

Manual updates required for Chatter Integration

The Chatter integrations requires:

  • The Adobe Sign Integration User permission set
  • The Salesforce system permission Insert System Field Values for Chatter Feeds enabled

 

Below is an explicit listing of the objects, and the required fields, if using the permission set is not acceptable for any reason:

Object Field Required values Standard/Custom Adobe Sign Permission Set
Agreement Event   Read Adobe Sign - Custom Adobe Sign Integration
  Type Read    
  Description Read    
         
Recipients     Adobe Sign - Custom Adobe Sign Integration
  Recipient Type Read    
  Email Address Read    
  Order Number Read    
  Use Email Address Read    

Manual updates required for Push Agreements

Push Agreements require that the linked Callback User have:

  • The Adobe Sign Integration User permission set
  • The Salesforce Account object must have Read and Create enabled
  • The Salesforce Contract object must have Read and Create enabled
  • The Salesforce Opportunity object must have Read and Create enabled
  • The Salesforce Contact object must have Read and Create enabled
    • The Name field on the Contact object must have Read and Modify enabled
    • The Email field on the Contact object must have Read and Modify enabled
    • The Account field on the Contact object must have Read and Modify enabled
  • The Salesforce Lead object must have Read and Create enabled
    • The Name field on the Lead object must have Read and Modify enabled
    • The Email field on the Lead object must have Read and Modify enabled
    • The Company field on the Lead object must have Read and Modify enabled

 

Below is an explicit listing of the objects, and the required fields, if using the permission set is not acceptable for any reason:

Object Field Required values Standard/Custom Adobe Sign Permission Set
Account   Read Salesforce -Standard  
         
Contract   Read Salesforce -Standard  
         
Opportunity   Read Salesforce -Standard  
         
Lead   Read, Create Salesforce -Standard  
  Email Read, Modify    
  Name Read, Modify    
  Company Read, Modify    
         
Contact   Read, Create Salesforce -Standard  
  Email Read, Modify    
  Name Read, Modify    
  Account Read, Modify    
         
Agreement   Read, Create, Modify Adobe Sign - Custom
Adobe Integration User
  All Fields Read, Modify    
         
Agreement Type   Read Adobe Sign - Custom Adobe Integration User
         
Mutexes   Read, Create, Modify Adobe Sign - Custom Adobe Integration User
  All Fields Read, Modify    
         
Triggers   Create Adobe Sign - Custom Adobe Integration User
  All Fields Modify    
         
Recipient   Create Adobe Sign - Custom Adobe Integration User
  All Fields Modify    
         
Agreement Event   Create Adobe Sign - Custom Adobe Integration User
  All Fields Modify    
         
Data Mapping   Read Adobe Sign - Custom Adobe Integration User
         
Merge Mapping   Read Adobe Sign - Custom Adobe Integration User

Manual updates required for Large Document Service

The Callback User must be configured and linked:

  • The Adobe Sign Integration User permission set added
  • The Callback User profile must enable the Administrative Permission for Modify Metadata

Additionally, the Site profile must be edited to:

  • Add the LargeFileDownloadService class
  • Remove the AgreementAttaqchmentService class

 

Below is an explicit listing of the objects, and the required fields, if using the permission set is not acceptable for any reason:

Object Field Required values Standard/Custom Adobe Sign Permission Set
Agreement   Read, Modify Adobe Sign - Custom Adobe Integration User
  Attachment Service Invocation Count Read, Modify    

What’s new in version 18

v18 Feature, Setting and Field Changes

New settings in version 18

Review the new settings added in version 18 to determine if you want to enable/disable any of these capabilities. 

Things to note:

Version 18 of the Adobe Sign for Salesforce application launches along side the Salesforce release of the new Lightning experience.  As a result, this new version has a few quirks to be aware of:
 
Update your Admin tab:
 
Lightning has limitations:
  • 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.

To get to this setting:

  • Navigate to Develop > Custom Settings > (Manage) Adobe Sign Settings
  • Click New to open the Adobe Sign Settings Edit page

New Adobe Sign Environment Settings

Config Oauth API URL— Enter a URL to override the default Adobe Sign API URL for the specified environment.

Note: These settings should not be altered without instruction from Adobe Sign support

To get to this setting:

  • Navigate to Develop > Custom Settings > (Manage) Adobe Sign Environment Settings
  • Click New to open the Adobe Sign Environment Settings Edit page

New Adobe Sign Template Setting - Active Flag

To add the "Active" flag to your templates, you will need to edit the Agreement Template page layout:

  • Navigate to Setup > Create > Objects > Agreement Template (Click the label, not the edit link)
  • Click Page Layouts at the top of the window to jump to the section
  • Click Edit for the Page Layout
  • With Fields selected, find and drag the Active field onto your page layout.
  • Click Save
Drag Active field to the page layout

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

Deprecated tab in version 18

Delete eSign Services Admin Tab

  1. Navigate to Setup > Create > Tabs
  2. Delete the eSign Services Admin tab (Replaced by the Adobe Sign Admin tab)

Other field values added in version 18

None.

Setting up the Agreement page style

If you are a new customer, the “Lightning” page style is the default, and is the layout that will be developed going forward. 

Upgrading customers are strongly recommended to adopt use of the Lightning page to ensure that new features are available as development continues to improve the product.

That said, there may be very good reasons you need to stay on one of the older page layouts. Refer to the guide on adjusting your Salesforce page layout to determine if moving to the Lightning page is best.

Implementing the Lightning Experience

If you plan to use the Lightning experience, you can customize the home page layouts for objects so you can work with your agreements. Before doing so, you must deploy your domain to all customers. (See https://developer.salesforce.com/docs/atlas.en-us.200.0.identityImplGuide.meta/identityImplGuide/domain_name_testing_and_rollout.htm).

If you have not defined a domain name, you must define one and deploy it (See https://developer.salesforce.com/docs/atlas.en-us.200.0.identityImplGuide.meta/identityImplGuide/domain_name_define.htm

You can customize both standard objects (Opportunity, Contract, Account, Lead, User, Contact) and non-standard objects (Case, Quote, ….) 

Editing the page layout for a master object record

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

2. Select Edit Page from the gear icon

Edit Page Link

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. 

Drag and Drop Agreement Panel

    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, and then click Save.

Assign the page as the default layout

Editing the page layout for a non-standard object record

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

2. Select Edit Page from the gear icon

Edit the Case page layout

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. 

Drag and Drop Agreement Panel

    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, and then click Save.

Assign the page as the default layout

What’s new in version 17

v17 Feature, Setting and Field Changes

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.

1. Choose Setup > Create > Objects > Agreement Templates > Page Layout > (Edit) Agreement Template Layout.

2. Add the new version 17 fields to the Information section:

  • Post Sign Redirect Delay (seconds)
  • Post Sign Redirect URL
  • Sender Signs Only

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

v16 Feature, Setting and Field Changes

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

v15 Feature, Setting and Field Changes

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.

  • Show EchoSign Library Attachments—Show the option to add EchoSign document templates.
  • Show EchoSign Field Templates—Show the option to select and apply EchoSign form field layer templates on documents.
  • Hide Ability to Add EchoSign Field Templates—Hide the link that allows senders to “Add Form Field Template” on draft documents.
  • Hide Reorder Attachments—Hide the sort attachments option for draft agreements.
  • Hide Reorder Recipients—Hide the sort recipients option for draft agreements.
  • Show Recipient Signing Order Options—Show two options for recipient signing: serial (ordered entered) and parallel (in any order).
  • Read Only Recipient Signing Order Options—Make the options for recipient signing order read-only on an agreement.
  • Enable Per Signer Identity Verification—Allow each signer to have a different identity verification method (for example, password, phone, social identity, KBA).
  • Enable Phone Authentication—Show the phone authentication option for verifying recipient identity. Usage of this feature is limited and may incur added costs.

Agreement Template field values added in version 15

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

1. Choose Setup > Create > Objects > Agreement Templates > Page Layout > (Edit) Agreement Template Layout.

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.

ملاحظة:

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

v14 Feature, Setting and Field Changes

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.
  • Read Only Email Copies—Make the “Send email copies to” field a read-only agreement field.
  • Read Only Field Set—Make the Additional Fields section read-only on an agreement.
  • Read Only Hosted Signing—Make the Hosted Signing checkbox a read-only agreement field. 
  • Read Only Language—Make the Language field a read-only agreement field.
  • Read Only Message—Make the Message field a read-only agreement field.
  • Read Only Opportunity—Make the Opportunity lookup field a read-only agreement field.
  • Read Only Preview or Position—Make the “Preview document or position signature fields” checkbox a read-only agreement field.
  • Read Only Recipient—Make the Recipients section read-only on an agreement.
  • Read Only Security Options—Make the Security Options section read-only on an agreement.
  • Read Only Sender Signs—Make the “I also need to sign this document” checkbox a read-only agreement field.
  • Read Only Sign Expiration—Make the “Allow signers X days to sign this document.” a read-only agreement field.
  • Read Only Sign Reminder—Make the “Remind recipient to sign” checkbox a read-only agreement field.
  • Read Only Signature Type—Make the Signature Type field a read-only agreement field.

Agreement Template field values added in version 14

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

1. Choose Setup > Create > Objects > Agreement Templates > Page Layout > (Edit) Agreement Template Layout.

2. Add the following version 14 field to the Information section:

  • Available for Publisher Actions

ملاحظة:

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

v13 Feature, Setting and Field Changes

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 Send Email Copies—Hide the “Send email copies to:” field on the send agreement page.        
  • 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.

1. Choose Setup > Create > Objects > Agreement Templates > Page Layout > (Edit) Agreement Template 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:

Object: Add File Attachment

Field: Attachment Type

Value to add: Quote Document from Master Quote

 

Object: Agreement Template

Field: Language

Values to add:

  • Chinese (Taiwan)
  • English (United Kingdom)
  • Korean (South Korea)
  • Polish (Poland)

تم ترخيص هذا العمل بموجب الترخيص العام غير المعدل الخاص بالإسناد وعدم التجارة والمشاركة الإصدار 3.0 ‏من ‏‏Creative Commons‏‏  إن بنود Creative Commons لا تشمل منشورات Twitter™‎ وFacebook.

إشعارات قانونية   |   سياسة الخصوصية على الإنترنت