The integrations listed below are managed by the Adobe engineering teams. For a full listing of all integrations, to include the partner-owned and managed packages, please refer to the Adobe Exchange.
The Acrobat Sign Sandbox does not support integrations.
The Adobe Sign versioning convention and support life cycle for integrated services align with other Adobe products with which you may already be familiar.
The package version uses a three-part numbering system to identify the sequential build number of the released version and the relative import of the upgrade in terms of new or changing content. The number follows this pattern:
Where N = Major version; m = Minor version; p = Patched version.
For example, an integration package version 23.2.1 indicates a release status of:
As engineers develop new “builds” of the package, they will increment the version number according to the nature of the updates to the code.
Not all versions are released to the public as the product iterates in development. It is not uncommon to see significant jumps in the patch version between releases.
It is strongly recommended that admins keep their version up-to-date to ensure that the account has full access to all features and all known security issues are patched.
Acrobat Sign may require an upgrade to the latest patched version in the case of sufficient security concern or to address a critical system issue.
The version support life cycle of an Acrobat Sign integration product is defined based on the major version of the package, and indicates the time frame that Acrobat Sign is actively supporting the individual verion of the integration.
Acrobat Sign supports the current verison of a package, and the previous two major versions (inclusive with all related minor and patch updates). Major versions are expressed as follows:
For example, if the current available version of the package is 23.2.1, then:
The version service life cycle defines the full scope of when the service is usable. The timeline matches the version support life cycle with the addition of a 90-day grace period that allows customers to complete their upgrade.
Contact your reseller or customer support if you have any questions.
Send, Remind, Cancel, and more, all directly from your email client. Available for Outlook and Gmail
Add a button to send your CPQ quotes directly from the quote page to Acrobat Sign
If you use community portals, and want to provide signable documents
A component for the Community Cloud that allows a developer to embed the signature Templates into other Lightning components
If you didn't set up the Acrobat Sign app for All Users
For generating batches of agreements based on user defined criteria
If you use Acrobat Sign with Leads in Salesforce, you probably want to take a look at this
Align users in Acrobat Sign groups based on Salesforce user profiles
If you send documents over 2MB, you will need this configured
"Push agreements" are transactions that are initiated external to Salesforce, like the agreements created by web forms, and then are pushed in to Salesforce.
Settings to enable sending from Chatter or Salesforce1
► Page Layout configuration (Basic, Advanced and Lightning)
When you need to change your page layout to one of the other options
You also need to comply with the basic Microsoft requirements to use Office
The Microsoft Teams Approvals application allows users to configure, send, sign and track Acrobat Sign agreements right within the Approvals application.
Microsoft Teams makes the Approvals application and Acrobat Sign application available to all users. There is no additional software to download. If you do not see the Approvals application or Acrobat Sign as an option in the Approvals application, contact your Microsoft Teams administrator and request they are re-enabled.
The Adobe Acrobat Sign for SharePoint solution is supported in the SharePoint 2019 On-Premise Classic UI only.
Adobe and Microsoft are currently working to expand support to include the Modern UI.
Workflows are no longer supported for SharePoint Online.
Support for Adobe Sign for NetSuite integration v4.0.6 and older has ended.
You must upgrade to v4.0.7 to ensure the continuation of functionality and support of Adobe Sign for NetSuite integration.
Acrobat Sign is ending support for older API authentication models in May 2021
Adobe is committed to providing safe and secure product experience for our customers by adhering to the latest industry standard security protocols. As a part of that process, Acrobat Sign is ending support by May 2021 for older API authentication models that allowed sending username and password in the API call.
Clients currently using the older authentication model will need to move to the newer OAuth-based authentication.
○ Customers using an integration should upgrade to the latest version. Refer to reference guides for all the latest Adobe-built partner integrations.
○ Customers who have built their own custom integration with Acrobat Sign will need to update to the latest OAuth-based authentication. For more details, please refer to this Migration Guide.
Planned EOL of SOAP API in May2021
With the release of REST API Version 6 providing the best programming experience for Acrobat Sign developers, the SOAP API has been deprecated and will not be supported past May 2021. The REST API is now the preferred interface to integrators and application developers and future development should move to this API.