User Guide Cancel

Adobe Acrobat Sign for Salesforce: Release notes

The Adobe Acrobat Sign for Salesforce release notes are ordered below with the current release at the top, and rolling back in time as you scroll down the page.

Adobe Acrobat Sign for Salesforce v25.2.1

End of support for S-controls

S-Controls, a legacy technology used for custom scripting in Salesforce Classic, has long been deprecated and will now be fully removed from the Acrobat Sign for Salesforce by July 2025. If you still use S-Controls, migrate to Visualforce or Lightning Web Components (LWC) for continued functionality.

Resolved issues

Issue number Corrected issue description
32486 Resolved a bug that occurred when establishing file mapping back to the agreement object.
32492 Fixed a data mapping issue specific to GovCloud.

Adobe Acrobat Sign for Salesforce v25.2

Acrobat Sign for Salesforce v25.2  includes the following enhancements and bug fixes.

Resolved issues

Issue number Corrected issue description
30861, 31508

Streamlined processing and improved notification handling ensure agreement updates are processed consistently, even during temporary failures. Improved accuracy of agreement status.

31223, 31589, 31605, 31706

Resolved document loading errors, improving document loading and document downloading.

32173 The Close button was previously hidden against the new white background after the Winter '25 Salesforce release. The design has been updated to make the Close button prominently visible.

Adobe Acrobat Sign for Salesforce v24.41

Acrobat Sign for Salesforce v24.41  includes minor bug fixes. 

Resolved issues

Issue number Corrected issue description
31834/32184 Fixed the issue where users weren't able to access host signing functionality on mobile and iPad devices. The host signing button and checkbox are now enabled for mobile users. Host signing error now displays an updated error string. 
32034 Added the missing country code for Andorra (+376).

Adobe Acrobat Sign for Salesforce v24.40

Adobe Acrobat Sign for Salesforce v24.40  includes minor bug fixes. The package features and user functionalities remain unchanged. 

Resolved issues

Issue number Corrected issue description
31421
Fixed the issue where the agreement status failed to update because reminders sent to groups with multiple members caused the event description to exceed 255 characters.
31603
Resolved the issue where signed documents and agreement status didn't update in Salesforce after offline signing. 
31818
Fixed the issue where the Opportunity Standard object was missing from the Salesforce Object picklist in the Agreement Templates object following the Salesforce Winter '25 Release.

Adobe Acrobat Sign for Salesforce v24.39

Support for Digital identity authentication

You can now verify signatures with Acrobat Sign Digital Identity Gateway on Acrobat Sign for Salesforce. With the new custom setting Enable Digital Identify Authentication, organizations can select from various third-party digital identity providers for identity verification, enhancing security and compliance. Learn how to enable authentication with digital identity providers.

Adobe Acrobat Sign for Salesforce v24.38

Adobe Acrobat Sign for Salesforce v24.38  includes minor bug fixes. The package features and user functionalities remain unchanged. 

Resolved issues

Issue number Corrected issue description
30692
Fixed the issue where users could not send agreements using Email as the authentication method.
30651
Fixed the issue where the Remind and Cancel buttons don't appear if we add the first recipient as a Delegator.
30394
Fixed the issue where users could not initiate an Agreement from Salesforce because a custom field on ContentVersion failed.
30770
Fixed the issue where agreements remained in the Created or the Presend state on Salesforce even though they were Out for Signature.

Adobe Acrobat Sign for Salesforce v24.37

Adobe Acrobat Sign for Salesforce v24.37 includes minor bug fixes. The package features and user functionalities remain unchanged. 

Resolved issues

Issue number

Corrected issue description

30097

Fixed the issue where signed files were not visible under Files on the agreement record page for web form agreements created via push mapping.

30150

Fixed the issue where tab icons were not displayed when an agreement was opened/created in the lightning console app with console navigation

30254

Fixed the issue where the Agreement names under the Files Related List were getting truncated if the length of the names was more than 80 characters. Now the recommended length is approximately 240 characters. 

30264

Fixed the issue where users could not delete agreements using the Delete draft option inside the agreement record.

30278

The character count limit for Agreement Template and Library Template names is up to 255 characters.

Adobe Acrobat Sign for Salesforce v24.35

Adobe Acrobat Sign for Salesforce v24.35  includes minor bug fixes. The package features and user functionalities remain unchanged. 

Resolved issues

Issue number Corrected issue description
29371 Fixed the issue where duplicate contacts were created on signature delegation.
29694 Resolved the issue where the Agreement record cannot be deleted from Salesforce org if the agreement is in a terminal state.
29839 Fixed the issue where users get a Permission denied error for the fields that are not related to the Agreements in Salesforce.
30071 Fixed the issue where users were unable to send agreements from Salesforce using FLOW Integrated with Adobe.
30096

Fixed the issue where agreements expire before the configured time in the 24-hour format.

Adobe Acrobat Sign for Salesforce v24.32

Support for ADobe Acrobat Sign Sandbox

You can now link Acrobat Sign for Salesforce with Acrobat Sign Sandbox environment. The Sandbox environment has the standard (default) configuration, allowing admins to test setting configurations, API calls, library templates, custom workflows, and new features.

Learn how to link to the Acrobat Sign Sandbox environment.

SUPPORT ON SALESFORCE MOBILE APP FOR ADOBE ACROBAT SIGN

This release introduces new features for the Salesforce Mobile app, including an improved user experience for the Agreement Editor, smooth navigation on mobile devices, and compatibility with native mobile file readers.

Learn how to use Acrobat Sign for Salesforce Mobile.

Resolved issues

Issue number Corrected issue description
29433
Resolved the issue where the Agreement template wasn't picking the actual sender but instead was selecting the user creating the template.
29455
Resolved the issue where the status of agreements remained stuck in the Pre-Send state, even after the signers received the document to sign.

Adobe Acrobat Sign for Salesforce v24.26

Support for Government cloud

Acrobat Sign for Salesforce now supports Acrobat Sign for Government Cloud, offering the following advantages:

  • Enhanced security: Government Cloud adheres to strict security and compliance standards of government agencies. It ensures protection of sensitive data and compliance with regulatory requirements.
  • Seamless integration: Government users can seamlessly integrate Adobe Acrobat Sign into their Salesforce environment. It allows users to efficiently manage agreements and collaborate within government organizations.
  • Customized solutions: Acrobat Sign for Government Cloud package can be tailored to align with the workflows and requirements of your agency.
  • Community collaboration: Government Cloud users gain access to a collaborative community of fellow government agencies and professionals. This community provides a network for sharing knowledge, best practices, and support, benefiting government organizations in their agreement management.

Note that the Acrobat Sign for Salesforce package for Government Cloud that has the following limitations:

  • Document Builder templates are not supported.
  • Group mapping is not available.
  • Push Agreements feature is not supported.
  • Chatter updates cannot be enabled.
  • Analytics cannot be enabled.

See how to set up the 'Acrobat Sign for Salescorce' package for Government Cloud.

access to agreement list from any object

The AgreementList can now appear on the Lightning pages for any Salesforce object. Previously, it was limited to Opportunity, Account, Contract, Contact, Lead, and User objects.

Resolved issues

Issue number Corrected issue description
28399 Resolved the issue where file mapping under data-mapping rules truncates the resulting filename if the original filename contains a '.' in the middle.  
28655
Fixed the issue where the "Host signing" option wasn’t being removed from the drop-down list next to an in-flight agreement in the agreement panel.
28968
Resolved the issue that was causing a "FILEINFO_LABEL_MISSING" error when sending agreements through a workflow-based Agreement Template.
29006
Fixed the error in the usage of the aura call AgreementSetupWizardComponentController.storeOauth, which resulted in the client ID/secret being leaked.
29035
Resolved the error where users were unable to send files larger than 4 Mb if there is extension '.pdf' appended to the file.
29134 Fixed the issue where Salesforce agreement status wan't getting updated for agreements with 'Documents_Viewed' status.
29183
When the agreement is being sent for signature, if the attached PDF files have ".pdf" in their file names, the "Signed Agreement" link now retrieves the latest PDF attachment from the list, instead of fetching it from the signing process.
29193
Fixed the 'Object row was retrieved via SOQL without querying the requested field: Contact.FirstName' error that occurred while attempting to generate an agreement.
29298 Fixed the issue where users were unable to send large files with the agreement associated with a workflow.
29333 Resolved the issue where Salesforce agreement status doesn't update when using Phone or Acrobat Sign as the identity authentication method.

Adobe Acrobat Sign for Salesforce v24.14

Support for sending agreements on behalf of user groups

With the release of v 24.14, Adobe Acrobat Sign for Salesforce now provides support for sending agreements from different user groups using the new custom setting called Adobe Acrobat Sign Group Settings. By associating agreements with user groups, admins can define and dictate the agreement-related properties such as available templates and workflows, branding, recipient roles, authentication methods, PDF security, and more for specific groups.

To learn how to enable Adobe Acrobat Sign Group Settings and send agreements from different user groups, see how to Create Agreement Templates for specific User Groups

Ending support for SOAP API-based agreement status update

Starting v 24.14, Adobe Acrobat Sign for Salesforce does not support the SOAP API-based push model for triggering automatic status updates. The automatic agreement status updates are now triggered using only the REST API-based pull model.

New picklist values for setting reminders

Adobe Acrobat Sign for Salesforce V 24.14 adds the following picklist values for sending reminders to recipients or for generating automatic reminders for agreement templates:

  • Every business day, until signed
  • Every other day, until signed
  • Every third day, until signed
  • Every fifth day, until signed

The new picklist values are available for users who do a clean install of the package v 24.14. Users upgrading from an older version are required to manually add the new picklist values to the custom fields.

support for recipient's name locking in KBA authentication

The package now provides a 'KBA Recipient Name Required' custom setting that can be enabled to mandate the recipient's name for KBA authentication for all agreements.

See how to enable advanced authentication methods.

Resolved issues

Issue number Corrected issue description
22870 Fixed the issue where agreements generated by Salesforce ignored the replace recipient setting "Only the new recipient will be able to participate."
23085 Resolved the issue where 'Acrobat Sign for Salesforce V23.8' users were unable to change the order of the files in an agreement.
24106 Resolved the status update issue where agreements displayed incorrect status for signers when delegated to another signer.
25736 Resolved the issue where users got a 'read timed out' error when linking their Acrobat Sign account at Salesforce.
25846 Fixed the issue where agreement reminders weren’t displaying in the audit trail.
26180 Fixed the issue where agreements failed to map data with the error: "Failed to map data field: System.NullPointerException attempt to de-reference a null object (echosign_dev1) 656"
26294 Resolved the component error that occurred when using Document Builder to create templates.
26339 Resolved the issue where users get an error message when adding recipients with Group roles.
26371 The issue in linking callback users is resolved once you upgrade to Adobe Acrobat Sign for Salesforce package version 24.14 or later.
26673 Resolved the issue where Agreement Templates referenced and allowed sending deleted Acrobat Sign Library templates.
27421 Addressed the 'Days Unsigned' field issue where the field's value kept increasing even after the agreement is signed. Users can now use the 'Days Until Signed' field instead.
28061 Fixed the issue where documents give a Query rows limit error for a null document key in SOQL.

Adobe Acrobat Sign for Salesforce v24.2

Support for Document Builder

With the release of v 24.2, Adobe Acrobat Sign for Salesforce includes a new feature called Document Builder. Document Builder is available as an extension package to the base package and does not require any additional purchase.

Document Builder enables users to automatically generate documents using Salesforce data. It includes a step-by-step wizard for creating rules for merging data from Salesforce object fields into a word document template. The generated document is sent as an attachment with the Acrobat Sign Agreement template and can be easily managed in Salesforce.

To learn how to install and use Document Builder, refer to Adobe Acrobat Sign for Salesforce: Document Builder User Guide.

Resolved issues

Issue number Corrected issue description
23388 Users can now see all the library files on the advanced search in the Agreement Template editor.
23492 Fixed the issue where users were unable to send a document that is in the 'pre-send' state at Salesforce.
23510 Fixed the error where users were unable to download signed documents from Salesforce.
24028 Resolved the error where the system picks default Record Type from Salesforce profile even if users select any other record type at the time of sending the agreement.
24068 Fixed the issue where users get erroneous pop-up messages when they select 'Send Reminder' or 'Cancel Agreement' options for an agreement on the Agreement lightning panel.
24097 Fixed the issue where the Send page shows an error and fails to update the status of the agreement even when the agreement is sent from the authoring view on Salesforce.
24107 Resolved the issue where users were unable to delete an agreement from the Agreement Related list.
24163 Fixed the issue where the 'Private Messages to Recipients' option is enforced on the Send page even if it's disabled in Acrobat Sign settings.
24171 Users can now use Disable_Upload_Agreement_Attachments__c setting to hide 'Add' and 'Upload files' option at Salesforce. 
24488 Resolved the issue for Salesforce mobile app users where an attempt to copy and paste an email address into the email address field gave an 'Invalid recipient' error. 
25430 The 'Search Contacts' drop-down list now displays full account names instead of partial names.
25736 Fixed the issue in linking the Acrobat Sign account to Salesforce where users get a 'Read timed out' error.

Acrobat Sign for Salesforce v23.14.3

Adobe Sign for Salesforce v23.14.3 includes minor bug fixes. The package features and user functionalities remain unchanged. 

Resolved issues

Issue number Corrected issue description
20523 Fixed the issue where an email address overlaps with the 'Email' recipient type.
23000 Users can now see country names along with country codes when they manually add country codes.
23011 Fixed the issue where Data Mapping fails with "Aggregate query has too many rows for direct assignment, use FOR loop" error.
23040 Fixed the issue where a user gets an 'Apex Heap Size Too Large: 6088659' error when sending a document from Salesforce.
23122 Fixed the issue where users were unable to add a template from the Adobe Sign Document Library using classic interface.
23136 Fixed the error that occurred when sending agreements from Publish Action with an image file.
23289 Fixed the issue where workflow-based agreements couldn’t generate the correct missing file error.
23632 Fixed the error in sending a template-based agreement to a group of user.
23730 Fixed an issue where an agreement fails to generate when using Quote template with Adobe Sign library document.
23831 Resolved the "Too many SOQL queries" error that occurred after sending agreements via a custom process.
23833 Fixed an error that occurred when users tried to set the recipient as a group in an agreement template.
24003
Fixed an error that occurred while creating an agreement template, where a variable in the CC field failed to interpret a null value in the parent object. 


Previous releases

Get help faster and easier

New user?