Salesforce Guides - v20
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
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
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 v16 and v17 will be ending on November 15, 2018
Product updates, security updates and technical support for Adobe Sign for Salesforce v16 and v17 is ending November 15, 2018.
If you are on version 17 or older, please upgrade to the new package to ensure the continuation of support.
Word / PowerPoint
- 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+)
MS Dynamics CRM Guides (365, On-line and On-Premises)
Adobe Sign for Microsoft Dynamics v5 and earlier (on premise and online versions) has been discontinued as of March 31, 2018.
All existing customers should have the new solution installed and operational, or risk losing Adobe Sign functionality.
SharePoint On-Premises 2013 & 2016
Adobe Sign for Microsoft SharePoint v3 and earlier (on premise) has been discontinued as of November 30, 2017.
All existing customers should have the new solution (linked above) installed and operational, or risk losing Adobe Sign functionality.
Support for the Adobe Sign for NetSuite integration v3.x has ended
Product updates, security updates and technical support for Adobe Sign for NetSuite v3.x and older has ended.
Please be sure to upgrade to v4 to ensure the continuation of support for this integration.