- Adobe Acrobat Sign Integrations
- What's New
- Product Versions and Lifecycle
- Acrobat Sign for Salesforce
- Install the Package
- Configure the Package
- User Guide
- Enable Digital Authentication
- 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
Adobe Acrobat Sign for Veeva Vault: Release Notes provides information about the new features and changes that are included in the current release of the Adobe Acrobat Sign integration for Veeva Vault. You can access the new features after downloading and installing the new package.
Note: Acrobat Sign + Veeva Vault release changes are aligned and deployed with the Acrobat Sign major release schedule. Testing of Acrobat Sign Integration changes are performed:
- Prior to release into production.
- In Veeva Vault sandbox environment prior to Veeva Vault’s major release to production.
Acrobat Sign for Veeva Vault v 1.3.4
Adobe Acrobat Sign for Veeva Vault v 1.3.4 includes minor bug fixes. The package features and user functionalities remain unchanged.
RESOLVED ISSUES
| Issue number | Description |
|---|---|
| 31517 | Fixed an issue when the agreement is canceled by the sender; the status of the document and signature takes more time to reflect in Veeva Vault in the remote scenario. |
31601 |
Fixed an issue where active agreement events were not processed in certain cases when the sender of an agreement was no longer an active user in Veeva Vault. |
Acrobat Sign for Veeva Vault v 1.3.3
Adobe Acrobat Sign for Veeva Vault v 1.3.3 includes minor bug fixes. The package features and user functionalities remain unchanged.
RESOLVED ISSUES
| Issue number | Description |
|---|---|
| 30775 |
Fixed an issue where a Veeva Vault task wasn't created to sign the agreement within Veeva in a remote scenario. |
31028 |
Updated the character limit of the "event_type__c" field to 100 within the 'Signature event' object in the VPK package to accommodate the event types exceeding 40 characters in length during processing. |
Acrobat Sign for Veeva Vault v 1.3.1
Adobe Acrobat Sign for Veeva Vault v 1.3.1 includes minor bug fixes. The package features and user functionalities remain unchanged.
RESOLVED ISSUES
| Issue number | Description |
|---|---|
| 30596 | Optimized the process for obtaining users from the Veeva vault. |
Acrobat Sign for Veeva Vault v 1.3.0
Veeva Vault Library Upgrade
Acrobat Sign for Veeva Vault package is now migrated to a more modern and efficient Vault API library (VAPIL) for enhanced integration.
Veeva Vault API version Upgrade
The Veeva Vault API version is now upgraded from v21.3 to v23.1.
Support for Restart Agreement Workflow
Acrobat Sign for Veeva Vault now supports agreement restart workflow where the recipient can restart an agreement except for the first recipient, granting them the ability to make any required modifications.
Resolved Issues
| Issue number | Description |
|---|---|
| 29542 |
Enhanced the package to ensure it no longer requires customers to use the latest document version, as this was found to be unsupported by some Veeva Vault products. |
| 29374 |
Fixed an issue where the Document state changed from "In Adobe Signing" to "Draft" even after signing the agreement. |
| 30047 |
Fixed an issue where Signature Status was not updated in a remote scenario when the sender canceled the agreement. |
Acrobat Sign for Veeva Vault v 1.2.1
Adobe Sign Rebranded to Adobe acrobat sign
We have renamed the Adobe Sign brand to Adobe Acrobat Sign to better emphasize the significance of e-signatures in complete document processes. As a result of this brand update, we are changing the name of Sign objects Labels in the Veeva Vault instance to Adobe Acrobat Sign.
Prevent users from sending document's older version for signature
In Veeva Vault, a document can have multiple versions. Latest package of Acrobat Sign for Veeva Vault enables you to prevent users from sending old documents for signature. If a user tries to use an older version of the document to create an agreement, they will receive an error message.
Resolved Issues
| Issue number | Description |
|---|---|
| 28390 |
Fixed an issue where the document state remains 'In Adobe Sign Draft' when sender is the only signer even after signing the agreement. |
Acrobat Sign for Veeva Vault v 1.2.0
New Features
With the release of Acrobat Sign for Veeva Vault package v 1.2.0, users can sign agreements from within the Veeva Vault environment without having to retrieve the email link.
Resolved Issues
| Issue Number | Description |
|---|---|
| 27377 |
Veeva Vault Sign Integration VPK now includes the missing picklist components: Task Type & Task status. |
| 27807 |
Fixed an issue where the document state remains 'In Adobe Sign Draft' when the Veeva Vault API is unable to retrieve the document while processing the webhook event. |
| 28170 |
Fixed the issue where users were not able to retrieve the agreements that were left in the 'Authoring' state before sending them for signature. |