Adobe Acrobat Sign for Salesforce: Upgrade Guide

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.