Посібник користувача Скасувати

Adobe Acrobat Sign for Salesforce: Upgrade Guide

  1. Adobe Acrobat Sign Integrations
  2. What's New
  3. Product Versions and Lifecycle
  4. Acrobat Sign for Salesforce
    1. Installation Guide
    2. User Guide
    3. Developer Guide
    4. Advanced Customization Guide
    5. Field Mapping and Templates Guide
    6. Process Builder Guide
    7. Document Builder Guide
    8. Upgrade Guide
    9. Release Notes
    10. Troubleshooting Guide
    11. Additional Articles
  5. Acrobat Sign for Microsoft
    1. Acrobat Sign for Microsoft 365
      1. Installation Guide
    2. Acrobat Sign for Outlook
      1. User Guide
    3. Acrobat Sign for Word/PowerPoint
      1. User Guide
    4. Acrobat Sign for Teams
      1. User Guide
      2. Release Notes
      3. Microsoft Teams Approvals
    5. Acrobat Sign for Microsoft PowerApps and Power Automate
      1. User Guide
      2. Release Notes
    6. Acrobat Sign Connector for Microsoft Search
      1. User Guide
    7. Acrobat Sign for Microsoft Dynamics 
      1. Overview
      2. Dynamics Online: Installation Guide 
      3. Dynamics Online: User Guide 
      4. Dynamics On-Prem: Installation Guide 
      5. Dynamics On-Prem: User Guide
      6. Dynamics Workflow Guide
      7. Dynamics 365 for Talent
      8. Upgrade Guide
      9. Release Notes
    8. Acrobat Sign for Microsoft SharePoint 
      1. Overview
      2. SharePoint On-Prem: Installation Guide
      3. SharePoint On-Prem: Template Mapping Guide
      4. SharePoint On-Prem: User Guide
      5. SharePoint On-Prem: Release Notes
      6. SharePoint Online: Installation Guide
      7. SharePoint Online: Template Mapping Guide
      8. SharePoint Online: User Guide
      9. SharePoint Online: Web Form Mapping Guide
      10. SharePoint Online: Release Notes
  6. Acrobat Sign for ServiceNow
    1. Overview
    2. Installation Guide
    3. Release Notes
  7. Acrobat Sign for HR ServiceNow
    1. Installation Guide
  8. Acrobat Sign for SAP SuccessFactors
    1. Cockpit Installation Guide
    2. Recruiting Installation Guide
    3. Recruiting User Guide
    4. Cloud Foundry Installation Guide
  9. Acrobat Sign for Workday
    1. Installation Guide
    2. Quick Start Guide
    3. Configuration Tutorial
  10. Acrobat Sign for NetSuite
    1. Installation Guide
    2. Release Notes
  11. Acrobat Sign for SugarCRM
  12. Acrobat Sign for VeevaVault
    1. Installation Guide
    2. User Guide
  13. Acrobat Sign for Coupa BSM Suite
    1. Installation Guide
  14. Acrobat Sign Developer Documentation
    1. Overview
    2. Webhooks
    3. Text Tags


The Adobe Acrobat Sign for Salesforce: Upgrade Guide provides instructions on how to upgrade the Adobe Acrobat Sign for Salesforce package from an older version to the latest released version.

We strongly suggest that you upgrade to the latest version of Adobe Acrobat Sign for Salesforce because:

  • Each version of Adobe Acrobat Sign for Salesforce has new features and enhancements that can provide key improvements to your document workflows. 
  • We provide support only for the latest version (N) and two major versions before the latest version (N-1 and N-2). Unsupported versions have elevated security risks and are denied API access to the Adobe Acrobat Sign service.

Important upgrade notes 

  • Do not uninstall your existing Adobe Acrobat Sign for Salesforce package as it may result in the loss of your Acrobat Sign data in Salesforce.
  • If you have users in your Salesforce org who belong to multiple Acrobat Sign accounts, before upgrading contact your Adobe client success manager or Adobe support.
  • Before upgrading your production account, you must upgrade and test in your Sandbox environment.
    Ensure that your email address in the Sandbox environment is one that you have access to in case you need to change the email for your Acrobat Sign account.
  • Ensure that the 'Lock sessions to the IP address from which they originated' setting is disabled. To configure, go to Setup > Settings > Security > Session Settings.
  • Review the What's New sections below to determine if there are options that need to be manually configured.
    Each release has many new features and settings that may require a manual update.
  • To learn about the latest features in Adobe Acrobat Sign for Salesforce, see Adobe Acrobat Sign for Salesforce: Release Notes.
  • If you are installing a new instance of the package, refer to the Adobe Acrobat Sign for Salesforce: Installation Guide.
  • Before upgrading, find the version of the currently installed package:
    1. Log into Salesforce using your admin credentials.
    2. Navigate to Setup Platform Tools > Apps > Packaging > Installed Packages and then check the Version Number for the Adobe Acrobat Sign package.

Update the package

  1. Go to the Salesforce AppExchange to access the latest Adobe Acrobat Sign for Salesforce package and then select Get It Now.

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

  3. In the dialog that appears:

    • Select Install in Production to install the package in the production environment.
    • Select Install in Sandbox to install the package in a sandbox environment.

    We suggest that you test each install in the sandbox environment first.

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

  5. When prompted to log in to your Salesforce organization, enter your user credentials and then select Login to Salesforce.

  6. On the Upgrade Adobe Acrobat Sign page that appears, select Install for All Users and then select Upgrade.

    Note: Installation can take a few minutes.


  7. If the Approve Third Party Access popup displays:

    • Check Yes, grant access to these third-party websites.
    • Select Continue to start the installation.
  8. When you see the message saying the installation may take some time, select Done and wait to receive the email notifying you that the package has been installed successfully.

    Once you receive the confirmation email, the Installed Package page displays the current package version.

    To configure your new package, see Post-install configurations.


Configure the updated package

You must refresh the OAuth connection between Adobe Acrobat Sign and Salesforce. 

Adobe Acrobat Sign for Salesforce objects may change as the package evolves so you must verify your workflows. If you build a custom solution that depends on the changed objects, you may be required to update your customization.

  1. Navigate to Setup > Platform Tools > Apps > Packaging > Installed Packages.

  2. For the Adobe Acrobat Sign package, select Configure.

    It launches the Adobe Acrobat Sign for Salesforce Setup Wizard.

    Note: If the Setup Wizard doesn’t launch automatically, navigate to the Adobe Acrobat Sign Admin tab and select Launch Setup Wizard.

    Launch setup

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

    1. Select Sign in to Adobe. 
    2. Log in to Adobe Acrobat Sign using your admin credentials.
    3. When prompted, select Allow Access.

    It displays a message saying Success! You have successfully authorized your Adobe account.

  4. On the successful Step 1 notification, select Next.

  5. In “Step 2: Enable Adobe Sign Automatic Status Updates”:

    1. Select Enable.
    2. When asked to allow access to Adobe Acrobat Sign, select Allow.

    It displays a message saying Success! You have successfully enabled Automatic Status Updates for your account.

  6. Select Next.

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

  8. Configure any manual updates listed in the What's New section, as required.


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 previous versions.

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 v19 to v23, you should enable any manual edits listed for versions v20, v21, and v22.

What’s new

Package version 24.x

  • To enable the Acrobat Sign verification method, Salesforce admins must add the new 'Acrobat Sign' picklist value to the 'Signer Verification Method' (API name echosign_dev1_Signer_Verification_Methodc) field in the Recipient (API name echosign_dev1SIGN_Recipients_c) object.

  • To successfully implement the KBA name required setting, admins must add the new picklist value 'Acrobat Sign authentication' to the 'Internal Signers Verification Method' in Agreement and Agreement Template objects, as shown below. 


Package version 23.x

This feature has been put in place to allow Adobe Sign to collect usage data to improve the product. This data is used only for development and not for marketing purposes.

Admins can enable or disable this feature on the Adobe Sign Admin tab or by running the set-up wizard.

Starting in v23 of the Adobe Sign for Salesforce package, the Files document storage object will be the primary object used in development.

Customers upgrading from versions prior to v23.0 will have their existing default storage type grandfathered into their upgrade (Attachments in most cases) to ensure no breakage of process is experienced.

Admins are advised to evaluate the impact of changing the document storage type to Files to best take advantage of future features.

To support the admin control of the document storage type, a new control has been added to the Custom Settings > Adobe Sign Settings set of controls.

This UI maps to the custom object Agreement_Document_Storage_Type__c

Viable setting values are:

  • {empty} - If the value is empty, the default behavior is based on the install version of the package
    • Version 23.0+ will default to Files as the default storage type
    • Versions prior to 23.0 will default to Attachments as the default storage type
  • Files - Strongly defines Files as the default storage object for Adobe Sign document
  • Attachments - Strongly defines Attachments as the default storage object for Adobe Sign document
Doc Type Setting

Package version 22.x

The introduction of Workflows into the Salesforce package requires additional access permissions to be enabled.

If you intend to use workflows,  then you must refresh the OAuth links.

No manual configurations or system changes are required

Package version 21.5.11
A required installation package for all versions that pre-date v21.5.9

Any existing installation that upgrades from a version prior to 21.5.9 must install the 21.5.11 package first.

After v21.5.11 is installed, the current package can be installed.

Any existing installation that upgrades from a version prior to 21.5.9 must install the 21.5.11 package first. After v21.5.9+ is installed, the current package can be installed.

Chatter must be enabled to install the v21.5.11 package

Before you start the upgrade process, verify that Chatter is enabled:

  • Navigate to: Setup > Platform Tools > Feature Settings > Chatter > Chatter Settings
  • If Chatter is Disabled, click the Edit button
    • Check the Enabled check box
    • Save the page
Enable Chatter

Package version v21.x


v21.x brings several updates to the way Adobe Sign for Salesforce operates. 

It is strongly recommended that you install v21.x into your sandbox environment first, to verify that all aspects of the application work as you expect. 

Developers should take care to review the changes to the update order, and the change in Apex method. 

As of v21.0, the SIGN_Signed_Agreement__c object (label name: Signed Agreement") has been deprecated.

Customers that would like to obtain the signed agreement URL should use the REST API agreement call GET /agreements/{agreementId}/combinedDocument/url

Note: The returned URL from the API call is secured, and only viable for a limited time.

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 

As of v21.x all asynchronous processes (which include automatic updates and data mappings) have been switched from future methods to queuebale, the new approach recommended by Salesforce.

Due to this change, any customizations in the subscriber org which add jobs to the Salesforce queue as part of the auto update and/or data mapping mapping process will fail with an error "System.LimitException: Too many queueable jobs added to the queue: 2"

This happens because a queuebale process can only add one child queueable job, which is already taken up by Adobe Sign (refer to the "Queueable Apex Limits" section here).

"When chaining jobs, you can add only one job from an executing job with System.enqueueJob, which means that only one child job can exist for each parent queueable job. Starting multiple child jobs from the same queueable job isn’t supported."

The symptom of this error is that the agreement status does not change and/or the data mapping does not run correctly. 

To resolve this error, look for the offending trigger, process builder, or workflow and deactivate it or switch it to use a synchronous call or schedule it in the future, for example 1 hr later.

  • 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.
  • When a signed PDF is stored in Salesforce, there will no longer be a descriptor (-signed or -approved) appended to the end of the PDF file name.

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

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

Логотип Adobe

Увійдіть до облікового запису