Get quick access to installation, user, and upgrade guides for current Adobe Sign integration products. Some of the more complex integrations will have commonly used knowledgebase articles also listed for convenience.
Adobe Sign integration product versioning and lifecycle:
The Adobe Sign versioning convention and support lifecycle for integrated services aligns with other Adobe products with which you may already be familiar.
Version numbers:
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:
N.m.p
Where N = Major version; m = Minor version; p = Patched version.
For example, an integration package version 23.2.1 indicates a release status of:
- Major version: 23
- Minor version: 2
- Patch version: 1
As engineers develop new “builds” of the package, they will increment the version number according to the nature of the updates to the code.
- Major version changes denote a significant addition in features or an important change to core systems
- Minor version updates typically include smaller feature updates and security patches. Adobe Sign may require an upgrade to the latest patched version in case of security or to address a reported item
- Patch versions are almost exclusively bug fixes and UI adjustments
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 recommended that admins keep their version as up-to-date as possible to ensure that the account has full access to all features and all known security issues are patched.
Adobe 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 support lifecycle
The support lifecycle of an Adobe Sign integration product is defined based on the major version of the package.
Adobe 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:
- Current version (N): The latest major version of the package
- Previous version (N-1): One major version behind the latest version
- Last supported version (N-2): Two major versions behind the current version
For example, if the current available version of the package is 23.2.1, then:
- Current major version (N) is 23
- Previous major version (N-1) of this package is 22
- Last supported major version (N-2) of this package is 21
- Every version older than 21.0.0 is unsupported
Contact your reseller or customer support if you have any questions.
Adobe Sign for Salesforce
All Organizations should upgrade to at least v21.5.11 as soon as possible.
v21.5.11 is a prerequisite for all later versions and must be installed before further upgrading to later versions.
Additional Articles
► Add Adobe Sign to your Salesforce email component
Send, Remind, Cancel, and more, all directly from your email client. Available for Outlook and Gmail
► Adobe Sign connector to Salesforce CPQ
Add a button to send your CPQ quotes directly from the quote page to Adobe Sign
► Adobe Sign for Self Signing (Community Cloud)
If you use community portals, and want to provide signable documents
► Adobe Sign for Simple Signing (Community Cloud)
A component for the Community Cloud that allows a developer to embed the signature Templates into other Lightning components
► Granting access to Salesforce users/profiles
If you didn't set up the Adobe Sign app for All Users
► Working with Agreements in Batch
For generating batches of agreements based on user defined criteria
If you use Adobe Sign with Leads in Salesforce, you probably want to take a look at this
Align users in Adobe Sign groups based on Salesforce user profiles
► Configure Salesforce to Send Large Documents
If you send documents over 2MB, you will need this configured
► Configure Push Agreements to create externally generated agreements in Salesforce
"Push agreements" are transactions that are initiated external to Salesforce, like the agreements created by web forms, and then are pushed in to Salesforce.
► Chatter & Salesforce1 enablement
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
Adobe Sign for Dropbox
Adobe Sign for Microsoft Office
Supported products:
- Exchange Online
Clients:
- Outlook 2013 (Windows v15+)
- Outlook 2016 (Windows v16+)
- Outlook Online – Using:
- Chrome - current version
- Firefox - current version
- Safari - current version
- Edge - current version
- Outlook 2016 (Mac v15.35+)
You also need to comply with the basic Microsoft requirements to use Office
Supported platforms:
- Word or PowerPoint 2013 (Windows v15+)
- Word or PowerPoint 2016 (Windows v16+)
- Word or PowerPoint Online (365) – Using:
- Chrome - current version
- Firefox - current version
- Safari - current version
- Edge - current version
- Word or PowerPoint 2016 (Mac v15.34+)
Supported platforms:
- Office 365 – Using:
- Chrome - current version
- Firefox - current version
- Microsoft Edge - current version
The Microsoft Approvals application allows users of the Microsoft Teams application to configure, send, and sign agreements within the Approvals hub.
Microsoft Teams makes the Approvals application available to all users.
Adobe Sign for Microsoft PowerApps and Power Automate (Formerly MS Flow)
Supported platforms:
- Office 365 – Using:
- Chrome - current version
- Firefox - current version
- Safari - current version
- Edge - current version
Adobe Sign for Microsoft Dynamics
Free Trial
Current Install Package for Dynamics 365 CRM
By downloading the Adobe Sign for MS Dynamics package, you acknowledge that you have read and accepted all of the Terms and Conditions:
Guides for Dynamics 365 CRM (v9.4)
- Installation Guide:
- User Guide:
- Dynamics Processes (Workflow) Guide
Release Notes
Microsoft Dynamics 365 for Talent
Adobe Sign for Microsoft SharePoint
The Adobe 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.
Guides
Guides
Workflow
Workflows are no longer supported for SharePoint Online.
Please refer to the Microsoft PowerApps and Power Automate guide for this functionality.
Adobe Sign for ServiceNow
Adobe Sign for HR (ServiceNow)
Adobe Sign for SAP SuccessFactors
Adobe Sign for Workday
Adobe Sign for NetSuite
- Installation and Configuration Guide (v4.0.5)
Release Notes
Support for the Adobe Sign for NetSuite integration v4.0.1 has ended
Due to a regression bug introduced when NetSuite updated their platform, technical support for Adobe Sign for NetSuite v4.0.1 and older has ended.
Please be sure to upgrade to v4.0.5 to ensure the continuation of functionality and support for this integration.
Adobe Sign for SugarCRM
Adobe Sign API
Adobe 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, Adobe Sign is ending support by May 2021 for older API authentication models that allowed sending username and password in the API call.
IMPACT
Clients currently using the older authentication model will need to move to the newer OAuth-based authentication.
ACTION REQUIRED
○ 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 Adobe Sign will need to update to the latest OAuth-based authentication. For more details, please refer to this Migration Guide.
○ Mobile users will need to upgrade to the latest version of the Adobe Sign app for iOS & Android.
Planned EOL of SOAP API in May2021
With the release of REST API Version 6 providing the best programming experience for Adobe 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.