تاريخ آخر تحديث
17 سبتمبر 2025
ملاحظة:
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: September 16, 2025
GovCloud deployment: September 18, 2025
Improved Functionality
- Custom Email Templates available for Acrobat Sign for Government - Customers on the GovCloud platform can now create custom email templates for their agreement notifications and reminders.
Available environments: Government | Available tiers of service: Acrobat Sign for Government | Configuration scope: Account or Group
- What's new banner on the Home page—A new What's new banner can be enabled at the account level to inform users about new product notifications like release notes, training, and system events. This helps drive awareness of new features and options, improve engagement, and ensure important updates aren't missed. All accounts will be enabled after release and can be disabled by the account-level administrator. There are a few exceptions to the "enabled by default" rule:
- The Australian shard (AU1) will have the feature opted out by default.
- Any account identified as a "Government" account will be opted out.
Available environments: Sandbox, Commercial | Available tiers of service: Acrobat Sign Solutions | Configuration scope: Account
Review the updated documentation for in-product messages and guidance >
Experience Changes
- Rebranding of the Notarize integration to Proof - The integration to the online notarization service has been updated to reflect the service's new branding, Proof, for all customer-facing communications.
Updates to the Acrobat Sign UI are expected in the next (v16.2) release in October.|
Available environments: Sandbox, Commercial | Available tiers of service: Acrobat Sign Solutions | Configuration scope: Account or Group
- Stricter locale validation when creating agreements via API - The language settings validation for agreements created via API has been tightened. When using the API to create an agreement, and the 'Allow users in your account to select a different signing language' option is disabled, the API will reject any request where the agreement locale doesn't match the 'Signing language' selected by the admin.
Note that sending through the web interface is not impacted.
Available environments: Sandbox, Commercial | Available tiers of service: Acrobat Sign Solutions | Configuration scope: API
Resolved Issues
| Issue | Description |
|---|---|
| 4511940 | Summary: When a sender creates a text field with Multi-line data entry enabled and the font set to Auto, signers using a mobile browser see text cut off at the bottom of the field. |
| Fix: Overrode the base method to get the field size to handle fontSize < 0 (auto) using a modified formula specific to multiline fields. | |
| 4516038 | Summary: When sending agreements with Send in Bulk, users see an error: "You have exceeded the maximum number of days allowed for document expiration." even though Document Expiration Settings are disabled at both the Group and Account level. |
| Fix: Corrected code to properly evaluate the agreement expiration values for the group/account. | |
| 4522265 | Summary: When a PDF contains both fillable fields and text tags, the text tags are not processed. |
| Fix: Created a task in the flattened case regardless of the presence of form field generators. Allows a PDF with form fields to process a formify artifact if needed. | |
| 4522645 / 4527073 |
Summary: Signed PDF includes a blank third page after the sender uploaded a document on behalf of the final signer. |
| Fix: Improved the managing function to properly handle small streams. Written Signature uploads use the repaired document and not the original upload if any issue is detected with the uploaded document. | |
| 4524437 | Summary: New users are not logged into Adobe Sign after accepting the invite due to a bogus URL. |
| Fix: Fixed the URL. | |
| 4525093 | Summary: The consumer disclosure link is not clickable. The link is present, but clicking it just toggles the checkbox instead of opening the link. |
| Fix: Modified the link CSS to allow the link to open a new page. | |
| 4525099 | Summary: Customers who require SMS delivery but have disabled email notifications cannot send agreements by SMS. |
| Fix: SMS /WhatsApp delivery is no longer dependent on the email settings. | |
| 4525328 | Summary: Using two or more templates that contain hyperlinks with the same name generates a server error when trying to sign |
| Fix: If duplicate hyperlink names are found, the link names will be modified to ensure they are uniquely identified. | |
| 4525510 | Summary: Payment form field fails to retain the USD currency type in New Authoring Experience, leading to an 'Unexpected error' failure. |
| Fix: The conversions for payment fields have been updated. | |
| 4525544 | Summary: Unable to edit the Active or Draft Webforms |
| Fix: We now preserve the existing settings and send them to the server, instead of using the UI data. | |
| 4525901 / 4532254 |
Summary: Agreement is not getting assigned to the remaining signer because of an incorrect workflow role when new participants are added after entering field authoring. |
| Fix: Improved the code to better evaluate the participant roles when new participants are added after authoring. | |
| 4526300 | Summary: Unable to create a custom agreement URL with the workflow ID with new experience |
| Fix: When custom URLs are created with only the workflow ID, the agreement creation form reloads and calls the backend to fetch the workflow and draft agreement again during form loading. | |
| 4526756 | Summary: GovCloud API Swagger Page documentation is incorrect regarding creating new applications |
| Fix: Added an additional phrase to avoid any confusion for FedRAMP customers. | |
| 4527340 | Summary: When users apply Fill & Sign in Acrobat web and then select Invite to e-sign, the values entered during Fill & Sign do not appear when the agreement transitions into the Acrobat Sign authoring page. The authoring view shows blank fields instead of the filled values. |
| Fix: The default font size value has been correct, thereby allowing the content to display properly. | |
| 4528835 | Summary: "MISC_SERVER_ERROR for GET formData Some miscellaneous error has occurred" error when calling GET /formData for a specific Cursor due to a null pointer error. |
| Fix: Added an NPE check and log. | |
| 4528902 | Summary: When an agreement is sent for sequential signing to 2 participants, the "recipient name" field assigned to the first participant is lost during PDF model processing. When setting the role of the "recipient name" field, the participation set role stored in the PDF model fails to convert. |
| Fix: Numerous functions have been updated to properly manage this type of conversion. | |
| 4531278 | Summary: Some email addresses added as CCs are removed automatically after sending the transaction if they were created before Acrobat Sign added automatic lowercasing of email addresses in user creation. |
| Fix: Updated the email address lookup/comparison in the CC removal code to be insensitive | |
| 4531669 | Summary: Agreements cannot be sent using PDF documents when processing form fields with names exceeding PDF specification limits. |
| Fix: NPE checks added for the appearance of an annotation. | |
| 4531998 | Summary: Unable to Access Child Agreements Via API - "Invalid Document ID" Error due to a null bookmark title. |
| Fix: Removed debug statement that can fail with an NPE if the bookmark title is null. | |
| 4532642 | Summary: When attempting to replace one of the counter signers in a web form that includes additional unknown signers and recipient group for counter signers, the update method attempts to read email from unknown participants (additional unknown signers), who have no user/email data, causing a NullPointerException. |
| Fix: Added a filter condition to exclude unknown participations from the email collection stream, preventing NPE when processing participations that don't have user/email data yet. |
