Get quick access to installation, user, and upgrade guides for current Adobe Sign integrations. Some of the more complex integrations will have commonly used knowledgebase articles also listed for convenience.
Add a button to send your CPQ quotes directly from the quote page to Adobe 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 Adobe Sign app for All Users
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
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
Support for the Adobe Sign for Salesforce integration v18 has ended as of March1, 2019
Product updates, security updates and technical support for Adobe Sign for Salesforce v18 has ended as of March 1, 2019
If you are on version 18 or older, please upgrade to the new package to ensure the continuation of support.
- Word or PowerPoint 2013 (Windows v15+)
- Word or PowerPoint 2016 (Windows v16+)
- Word or PowerPoint Online (365) – Using:
- Chrome v59+
- Firefox v53+
- Safari 9+
- Edge 38+
- IE 11+
- Word or PowerPoint 2016 (Mac v15.34+)
Support for the Adobe Sign for NetSuite integration v4.0 has ended
Due to a regression bug introduced when NetSuite updated their platform, technical support for Adobe Sign for NetSuite v4.0 and older has ended.
Please be sure to upgrade to v4.0.1 to ensure the continuation of functionality and support for this integration.
Adobe Sign is ending support for older API authentication models in August 2019
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 August 2019 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 Adobe 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 June 2020
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 June 2020. The REST API is now the preferred interface to integrators and application developers and future development should move to this API.