Adobe Acrobat Sign Release Notes

Keresés

Utoljára frissítve: 2025. máj. 20.

Megjegyzés:

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.

Adobe Acrobat Sign Release 16.0.1

Production deployment: May 20, 2025

GovCloud deployment: May 22, 2025

Improved Functionality

Improve recipient data security by configuring recipients with restricted access - The Restricted Access to Agreements feature enhances privacy by preventing agreements from being attached to a recipient's Acrobat Sign userID (if they have one). When enabled, the Recipient Agreement Access option appears in the Recipient Settings section on the Compose page. Administrators can configure this setting to enable it by default and make it editable by senders.
When a recipient is marked as restricted, they are treated as if they do not have an active Acrobat Sign user account. As a consequence, the agreement does not appear on their Manage page. This prevents accidental data leakage due to group-level sharing relationships.

Available environments: Sandbox, Commercial, Government | Available tiers of service: Acrobat Sign Solutions | Configuration scope: Account and Group
Review the Restricted access to agreements configuration controls >
Updated Request Signature documentation >

API support has been added for the Restricted Access to Agreements feature - Organizations that use the API to compose and send agreements can now use the Restricted Access to Agreements feature as part of their recipient configuration. The API implementation of this feature has one experiential difference with regards to when the document can be accessed if the authentication type is set to "None":
- Within the Acrobat Sign interface, the recipient may not View or Download the agreement until it is signed. Even if no authentication is configured, access to the agreement is disabled by suppressing the View and Download actions.
- When using the API, the agreement may be viewed and downloaded with the token after authentication is passed. In the case where no authentication is configured, the agreement can be viewed or downloaded before it is signed.

Available environments: Sandbox, Commercial, Government | Available tiers of service: Acrobat Sign Solutions | Configuration scope: Account and Group

Expanded Country support for Phone Authentication – Phone Authentication and agreement delivery via SMS now support these additional Countries and Country Phone codes:
- Falkland Islands (Malvinas) (+500)

Available environments: Commercial | Available tiers of service: Acrobat Sign Solutions | Configuration scope: Account and Group

Experience Changes

Webform support case submission now requires login for legacy enterprise accounts - Users with legacy enterprise accounts must now sign in with their Acrobat Sign credentials before using the online webform to submit a support case. This authentication step ensures the case is linked to the correct account and routed to the appropriate support team.

Available environments: Commercial | Available tiers of service: Acrobat Sign Solutions | Configuration scope: Enabled by default; Not editable
Review the new process >

REST API/Webhook Updates

API and webhook updates for this release can be found in the Acrobat Sign API documentation.

GET /agreements API Now Served from a Microservice - The GET /agreements endpoint is migrating from the Acrobat Sign core application to a dedicated microservice. As part of this transition, search requests will retrieve data from the search service (secondary storage) instead of the primary database. This change enhances service stability and prevents atypical API calls from affecting the Acrobat Sign experience.
- The maximum page size for the GET /agreements call is now 500 agreements per request. Historically, the search service did not fetch more than 100 agreements per page. If more agreements are required, multiple queries with a narrower scope may be necessary.
- Since searches now occur in secondary storage, minor additional latency may be observed when calling the GET /agreements endpoint.

Update to API throttling - After the May 2025 release, new API throttling rules will be applied:
- When high overall system load is detected, Acrobat Sign will throttle a subset of API requests across the entire system.
- When high-usage customers are identified as contributing to overall system slowness, Acrobat Sign will throttle a subset of API requests specifically for that customer.

When an API request is throttled, it will be rejected with a 429 HTTP status code, along with the following:

Response Body

    {
        "code":"THROTTLING_HIGH_SYSTEM_LOAD",
        "message":"Acrobat Sign system is experiencing high overall load, due to which subset of the requests are being throttled. Please try again in <wait_time_in_seconds> seconds.",
        "retryAfter": <wait_time_in_seconds>
    }

Response Header

        X-Throttling-Reason : "high-system-load"
        Retry-After : <wait_time_in_seconds>

Upon receiving the above response, you can use the Retry-After header or the retryAfter in the response body to determine when to attempt the request again.

Retry Penalty

For all new accounts created after the May 2025 release, a penalty will be applied if the account does not adhere to the specified retry time interval.
If the same request is attempted again within this interval, the request will be throttled again, and the retry time interval will be reset.

Resolved Issues

Issue	Description
4477748	Summary: Users are unable to create OAUTH ACCESS-TOKEN due to a malformed domain in the API call.
4477748	Fix: The domain list for the Swagger controller has been updated.
4480357	Summary: Keyboard handling within the "Start from library" dialog is not working properly when screen readers are running
4480357	Fix: Multiple fixes to screenreader navigation to ensure all pages start are read as expected.
4498103	Summary: Incorrect Role Assignment in Bulk Send Feature. Always assigning a "Signer" role when adding yourself as the last recipient.
4498103	Fix: Removed options for other roles for the sender when they are added to the last participant position as it is intended that the sender will always be a signer.
4501417	Summary: Placing a seal signature field with a field template triggers an error that blocks further authoring.
4501417	Fix: Added code to process text tag "signer1" text tag elements.
4506667	Summary: If a Sender needs a Webform's First signer to verify their email, Webhook notifications are delayed until the first signer verifies the email. If the first signer's email is bounced, the webhook notification is delayed for 2 hrs due to an expectation that the documentsInfo parameter will be filled.
4506667	Fix: If the Sender needs a Webform's First signer to verify email, documentsInfo will not be populated in the webhook notification payload for the Agreement events (until first signer verifies the email). If the first signer's email is bounced, *documentsInfo* will not be populated in the webhook notification payload for the Agreement events.
4511940	Summary: The default font size of a multi-line text field does not adjust to the screen size, so the text is cut off while signing an agreement using a mobile phone.
4511940	Fix: Multi-line text field can no longer override the base class method.
4513457	Summary: Issue with parsing JSON when group name contains double quote character(s) in the group name.
4513457	Fix: Improved parsing code for group names to manage double quotes.
4515610	Summary: Calculated field values are changed when the webform is sent to additional Participants due to how floating-point numbers are handled on the backend and front end.
4515610	Fix: Changing the implementation on the backend to use BigDecimal as the type for numbers
4516504	Summary: When you create a reusable template and use the New Experience view, the checkbox and radio buttons have pink borders instead of black borders due to the color value being truncated.
4516504	Fix: The hex value has been corrected to hold the correct value.
4520149	Summary: Some agreements do not update their status after being signed due to a rare race condition when setting the next_to_sign flag.
4520149	Fix: Additional logging has been added to catch this condition and resolve it before recipients interact with the agreement.
4521246	Summary: Template sharing within multiple groups is not working and throws errors when Advanced Account Sharing is enabled, and the sending process starts from the Home page.
4521246	Fix: The template picker sourced from the Home page has been updated to properly fetch the shared template.