- Adobe Acrobat Sign Integrations
- What's New
- Product Versions and Lifecycle
- Acrobat Sign for Salesforce
- Install the package
- Configure the package
- User Guide
- 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 Developer Documentation
The Adobe Acrobat Sign versioning convention and support lifecycle for integrated services align with other Adobe products that you may be familiar with.
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 version 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 increment the version number according to the nature of the updates to the code.
- Major version changes involve a significant feature addition or an important change to the core systems.
- Minor version updates include smaller feature updates and security patches. Adobe Acrobat Sign may require an upgrade to the latest patched version in case of security updates or to address a reported item.
- Patch versions are almost exclusively bug fixes and UI adjustments
All versions are not released to the public as the product iterates in development. So, there might be significant jumps in the patch version between releases.
The admins must keep their version up-to-date to ensure that the account has full access to all the features and all known security issues are patched. Adobe Acrobat Sign may require an upgrade to the latest patched version in the case of a security concern or to address a critical system issue.
Version support lifecycle
The version support lifecycle of an Adobe Acrobat Sign integration product is defined based on the major version of the package, and indicates the time frame that Adobe Acrobat Sign is actively supporting the individual version of the integration.
Adobe Acrobat Sign supports the current version 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
Version service lifecycle
The version service lifecycle defines the full scope of when the service is usable. The timeline matches the version support lifecycle with the addition of a 90-day grace period that allows customers to complete their upgrade.
During the grace period of an unsupported version, support is only provided to upgrade to a newer version, not to maintain an unsupported version
After the grace period, the version falls out of service
Adobe Acrobat Sign will not accept requests from versions that are out of service
Once the integration is upgraded to the current version, communications between Adobe Acrobat Sign and the integration will resume normally
Note: If you have any quesions, contact your reseller or customer support.