Have trouble installing and setting up the package? Get a smooth setup.
Last updated on
9 April 2024
- Adobe Acrobat Sign Integrations
- What's New
- Product Versions and Lifecycle
- Acrobat Sign for Salesforce
- Install the Package
- Configure the Package
- User Guide
- Enable Digital Authentication
- Developer Guide
- Advanced Customization Guide
- Field Mapping and Templates Guide
- Mobile App User Guide
- Flows Automation Guide
- Document Builder Guide
- Configure Large Documents
- Upgrade Guide
- Release Notes
- FAQs
- Troubleshooting Guide
- Additional Articles
- Acrobat Sign for Microsoft
- Acrobat Sign for Microsoft 365
- Acrobat Sign for Outlook
- Acrobat Sign for Word/PowerPoint
- Acrobat Sign for Teams
- Acrobat Sign for Microsoft PowerApps and Power Automate
- Acrobat Sign Connector for Microsoft Search
- Acrobat Sign for Microsoft Dynamics
- Acrobat Sign for Microsoft SharePoint
- Overview
- SharePoint On-Prem: Installation Guide
- SharePoint On-Prem: Template Mapping Guide
- SharePoint On-Prem: User Guide
- SharePoint On-Prem: Release Notes
- SharePoint Online: Installation Guide
- SharePoint Online: Template Mapping Guide
- SharePoint Online: User Guide
- SharePoint Online: Web Form Mapping Guide
- SharePoint Online: Release Notes
- Acrobat Sign for Microsoft 365
- Acrobat Sign for ServiceNow
- Acrobat Sign for HR ServiceNow
- Acrobat Sign for SAP SuccessFactors
- Acrobat Sign for Workday
- Acrobat Sign for NetSuite
- Acrobat Sign for SugarCRM
- Acrobat Sign for VeevaVault
- Acrobat Sign for Coupa BSM Suite
- Acrobat Sign for Zapier
- Acrobat Sign Developer Documentation
What can we help you with?
Struggling with user management? Learn to handle it effectively.
Trouble with agreements? Master efficient management now.
Are errors slowing you down? Acquire precision in issue resolution.
If your Acrobat Sign app isn't set for All Users, learn how to Grant access to Salesforce users/profiles.
To align users in Acrobat Sign groups based on Salesforce user profiles, learn more about Group Mappings.
Issue: An active Salesforce user is not getting auto-provisioned to the linked Adobe Acrobat Sign account.
Resolution steps:
- Verify that the Disable User Provisioning option is not enabled for the user.
- Verify that Adobe Acrobat Sign Email Verified check box is not selected.
- If the Adobe Acrobat Sign Email Verified checkbox is selected or was selected in the past, you must manually add the user from the Adobe Acrobat Sign UI.
- Update the User Details page of the user in Salesforce with a first name on the First Name field.
- If you do not see the Adobe Acrobat Sign Email Verified check box, you must manually add it to the User Details page layout. To do so:
- Navigate to Set up > Object Manager > User.
- Select User Page Layouts and then select User Layout for the user.
- Drag and drop the field named Adobe Acrobat Sign Email Verified field to the Additional Information section.
- Disable Send on behalf of... feature.
If you've enabled account sharing on your Acrobat Sign account, the users that are not included in the agreement can’t view the agreement in the Salesforce environment, unless:
- The agreement was created from a shared library template in the Adobe Acrobat Sign library.
- The library template is shared in a manner that includes the viewer via: (a) Shared for all users in the account, or (b) Shared at the group level, where the sender and viewer are in the same group.
Note: You can use Adobe Acrobat Sign to view the agreement.
If your agreements status is not getting updated even when the agreement is completed and signed, you must enable automatic status updates for your organization. If the agreement's status does not get updated even after enabling the setting, see how to troubleshoot failure in the automatic status udpate.
You can redirect the signers to a desired URL after they have completed the signing process. To do so:
- On the Acrobat Sign for Salesforce lighting page, select Agreements Templates > New Agreement Template.
- Select Rules tab.
- In the Post Sign Redirect URL field, enter the desired URL.
- Optionally, you can specify a delay (in seconds) before redirecting the users.
In case you do not see the post signing options, see how to enable post sign options.
| File type | Size limit |
|---|---|
| File uploaded to Salesforce Lightning from the computer |
700 KB |
| File uploaded to the Visual Force page from the computer |
2 MB |
| File sent from Acrobat Sign for Salesforce (v 18.00 or later) - without callback site |
4 MB |
| File sent from Acrobat Sign for Salesforce (v 18.00 or later) - with callback site |
10 MB default (can be increased) |
For sending documents over 2 MB, learn how to configure Salesforce to Send Large Documents.
A business contract process is a system of interconnected steps with various stages from initiating an agreement to the final steps of closing a deal. The tasks involved during the different stages of a contract are vital to contract management but instead of manually tracking each task, you can automate these tasks by configuring Flows on Adobe Acrobat Sign for Salesforce.
See how to Automate your contract processes.
Document Builder is an Adobe Acrobat Sign for Salesforce feature that provides the ability to automatically generate documents using Salesforce data. See how to use Document Builder.
Acrobat Sign Data Mappings update Salesforce objects when an Acrobat Sign agreement is signed or at a specified stage in the agreement workflow. Each Data Mapping is set up ahead of time and includes data mapping rules that define the data source and the target Salesforce field that it must update.
To share signable documents on community portals, see Adobe Acrobat Sign for Self Signing.
For generating batches of agreements based on user-defined criteria, learn how to Work with Agreements in Batch.
Professional and Enterprise editions can fail to do a Lead lookup if the user's profile does not permit access to the Mobile field of the Lead object.
To fix the issue:
- Navigate to Setup > Platform Tools > Objects and Fields > Object Manager.
- From the list of objects in the left panel, select Lead.
- From the left panel, select Fields & Relationships.
- Select the Field Label for the Mobile field.
- Select Set Field-Level Security.
- Set the appropriate Profiles to enable (check) Visible and Read-Only.
- Select Save.
In case of Data/Merge Mapping error in a record, you must look under the following columns in the Agreement list view for that record:
- Merge Mapping: To identify which Merge mapping is selected.
- Merge Mapping Result: Processing/Completed/Failed - This picklist tells the status of the Merge Mapping.
- Merge Mapping Error: To know the cause of Merge Mapping failure.
- Data Mapping: To know which Data mapping is selected.
- Data Mapping Error: To know the cause of Data Mapping failure.
- Data Mapping Result: Processing/Completed/Failed - This picklist tells the status of the Data Mapping.
By default, these fields (columns) are not added to the Agreement list view. See how to add these columns to the Agreement list view.
Adobe Acrobat Sign Authentication Error: access_denied error can occur while installing the Adobe Acrobat Sign package or when a user sends an agreement through the Acrobat Sign for Salesforce integration for the first time. This error indicates that the user lacks the necessary permissions for the action.
There are several possible reasons for authentication errors during package installation:
- Incorrect or restricted userID in Adobe Acrobat Sign.
- Improper configuration of the Adobe Acrobat Sign account as an enterprise account.
- The account not associated with the correct channel.
Authentication errors when sending an agreement can be attributed to:
- The user not being in the correct Adobe Acrobat Sign account.
- User's sending authority is revoked.
Invalid refresh token error indicates that the access tokens are not valid anymore. Admin-induced changes affecting the Acrobat Sign integration may result in the revocation of the access token.
To resolve the error, Salesforce admins must re-run the Acrobat Sign setup wizard using the steps below:
- Log into your Salesforce account and then select Adobe Acrobat Sign Admin tab.
- Under Account Settings, select Launch Setup Wizard.
- When prompted to sign in, enter your Acrobat Sign admin credentials.
- On the Enable Adobe Sign Automatic Status Updates page, enter your Salesforce credentials when prompted and then selct Enable.
Note: Only Adobe Acrobat Sign admin user credentials can be used to run the Acrobat Sign setup wizard.
IO Exception: Unauthorized endpoint, please check Setup->Security->Remote site settings. endpoint = <the missing endpoint url>
IO Exception error indicates since the end point is not added to the remote sites, it is detected as unauthorized by Salesforce. Hence, it does not allow you to access Adobe Acrobat Sign.
To resovle this error, you must add the endpoint to the Remote Sites using the following steps:
- Log into your Salesforce account.
- Go to Setup > Security > Remote Site Settings.
- Select New Remote Site.
- On the Remote Site Edit page, fill in the following details:
- In the Remote Site Name field, enter the site name.
- In the Remote Site URL field, enter the site URL.
- Select Save.
"Invalid user ID or email provided in x-API-user header" error can occur if the email address passed as a sender in x-api-user header is not part of the Acorbat Sign account with which the integration is set up in Salesforce. The Email address is x-api-user header, which is picked from the user profile in Salesforce.
To resolve the error, you must enter the Acrobat Sign account's registered email address in the Salesforce profile using these steps:
- From the Salesforce lightning page, select the profile icon and then select Settings.
- From the left panel, select My Personal Information > Personal Information.
- In the Email field, enter the email address that you used to register your Adobe Acrobat Sign account.
- Select Save.