Feature
This document highlights the new features, experience changes, and resolved issues in the customer-facing application for the most recent release.
Developer-centric updates to the API and Webhooks are documented in the Acrobat Sign developer guide.
Not all features/changes are guaranteed to be enabled on the date of the release.
Production deployment: August 22, 2023
GovCloud deployment: August 24, 2023
- Audit report logging of enforced authentication challenges - Enhanced audit report logging has been expanded to include support for SAML and Admin Console authentications. Customers that have enabled the Enforce identity authentication feature (on the Bio-Pharma Settings tab) will have each authentication event explicitly logged in the audit report, including the stage at which the authentication was captured (opening the agreement, applying a signature, and selecting the Click to Sign button). The agreement's activity list also reflects each authentication (albeit in a shorter format).
- The From header in all outbound emails has been updated to a more consistent format to reduce issues with email servers. There are two forms of the header:
- When the recipient has a known name, such as a registered user, or when the Required recipient name setting is in use, the header will read as Adobe Sign on behalf of firstname lastname <adobesign@adobesign.com>
- When the name value of the recipient is unknown, the header will read as Adobe Sign <adobesign@adobesign.com>
- When the recipient has a known name, such as a registered user, or when the Required recipient name setting is in use, the header will read as Adobe Sign on behalf of firstname lastname <adobesign@adobesign.com>
REST API/Webhook Updates
- The API functionality to place a form field relative to a specified "anchor" text string has been improved to allow for the identification of the file where the string is present and the page within that file if such granularity is needed. The important structures are:
- POST /agreements - The API call to create the agreement.
- formFieldGenerators - Provides the list of fields to be generated.
- fileInfos - Provides the label parameter for the file information of the anchor fields when specific recipients are expected to interact with specific files.
- anchorText - Defines the specific string that defines the relative location of the generated field.
- anchorTextInfo - defines the position of the generated field relative to the anchor string.
- formFieldDescription - Provides the information for the type of field to be generated.
|
Enablement date |
Available to (service type) |
Configuration level |
---|---|---|---|
Expanded audit reporting for enforced identity authentication |
With the release |
Enterprise and Business tiers |
Account and Group |
ISO 8601 date format |
With the release |
Teams and Acrobat Sign Solutions |
Account and Group |
Consistent email header |
With the release |
All tiers of service |
Not configurable |
Identification of individual anchor text for field placement via REST v6 API |
With the release |
Enterprise tier |
Available in the REST v6 API |
Issue |
Description |
---|---|
4425785 |
Summary: Date fields with the format 'dd/mmm/yyyy' cannot be populated in the Czech language when using the čvn value. |
Fix: The locale providers for the date functionality have been updated to properly manage this use case. | |
4429246 |
Summary: Editing the recipient list of a workflow may impact the agreements sent by that workflow, resulting in agreements being stuck in an In Progress status. |
Fix: The code that manages how an agreement understands the recipient list for agreements has been improved to manage the recipient list within the transaction, ignoring edits made to the template. | |
4432494 |
Summary: Agreements in the Acrobat environment may fail to load the view of the agreement image when opened on the Manage page due to an unhandled exception. |
Fix: The method used to populate the image has been updated to properly manage the exception. | |
4436936 |
Summary: Webforms with mandatory hyperlink fields throw an error when users try to save them. |
Fix: A condition has been added to allow for saving the webform despite the hyperlink not being selected. | |
4437223 |
Summary: Signing an agreement on Adobe Sign using an iOS device may prompt a Server error due to the API not properly /PUTing read-only fields. |
Fix: Updated the API used to place the fields for the agreement. | |
4441057 |
Summary: Reminder email notification sent to a recipient who is not yet the active recipient when the reminder is created using REST v5 and the future recipient has been replaced by the sender. |
Fix: Added a condition to send the reminder only to delegate participations who can potentially sign the agreement at that point in time. |
|
4442166 |
Summary: Archived agreements are not purged from the system when added to the Delete queue. |
Fix: Archived agreements are purged immediately when sent to delete instead of holding it in queue for 14 days. | |
4444011 |
Summary: HTTP 501 access_denied error while using Intesi as an Electronic Seal due to an invalid endpoint token. |
Fix: How the token is built has been updated to be more robust and provide version tolerance. | |
4447727 |
Summary: Some web forms from 2018 and before may fail to load with a generic error message due to a null pointer error. |
Fix: The problematic code has been identified and corrected. |