Adobe Acrobat Sign Release Notes - 2025

Search

Adobe Acrobat Sign Release Notes: 2025

Production deployment: February 11, 2025

GovCloud deployment: February 18, 2025

Improved Functionality

  • Improved user interface for Custom Send Workflows - The Custom Workflow Designer has been updated to provide a better sender experience that aligns with the Request Signature look and feel.
    Available environments: Sandbox, Commercial, Government | Available tiers of service: Acrobat Sign Solutions | Configuration scope: Group, Account

Experience Changes

  • Agreement expiration may be delayed up to 12 hours - Starting with this release, the automatic expiration of an agreement will take place during non-peak hours for the environment that is managing the agreement. In practice, any agreement that expires during the peak traffic times of any given Acrobat Sign environment will be queued to execute once the environment enters the non-peak time window.

Integrations

  • Workday: Digital Signature support for the Aadhaar Identity Provider - Customers using the Workday integration can now use the Aadhaar Identity Provider as a method to authenticate their recipients.

REST API/Webhook Updates

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

  • A new accountId attribute is being added to all event notification payloads.
  • OEM Embed 2.0 partners will now be able to set up a webhook for their channel and listen in to all the asset notifications from each of their individual customer accounts.
  • New Settings APIs
    • POST /accounts/{accountId|me}/settings/search – Takes the identified account (accountId) and a list of setting names and returns the list of setting names with their values for the account specified. Only account-level values are returned. 
      • Available to non-admin users.
    • PUT /accounts/{accountId|me}/settings  - Applies a provided list of setting names and their values to the identified account (accountId).
  • New Logo APIs
    • POST /accounts/{accountId|me}/logo - Uploads the CoBrandingLogo file.
    • GET /accounts/{accountId|me}/logo - Returns the image data of the CoBrandingLogo image file in the same format that it was uploaded.
      • Available to non-admin users
    • DELETE /accounts/{accountId|me}/logo – Clears the CoBrandingLogo image for the account.
  • Signing Reason APIs
    • GET /accounts/{accountId|me}/signingReasons - Returns a list of signing reasons for the identified account (accountId). 
      • Available to non-admin users.
    • POST /accounts/{accountId|me}/signingReasons -  Creates a new signing reason for the identified account (accountId).
    • GET /accounts/{accountId|me}/signingReasons/{signingReasonId} - Retrieves the text of the identified signing reason (signingReasonId) from the identified account (accountId). account's identified signing reason.
      • Available to non-admin users
    • PUT /accounts/{accountId|me}/signingReasons/{signingReasonId} - Updates the identified signing reason (signingReasonId) from the identified account (accountId).
    • DELETE /accounts/{accountId|me}/signingReasons/{signingReasonId} - Removes the identified signing reason (signingReasonId) from the identified account (accountId).
  • Updated swagger pages to indicate me as a shorthand for the accountId.

Resolved Issues

Issue Description
4479949 Summary: An OIDC API calls to an IDP contain the "charset=UTF-8" parameter in the "Content-type:application/x-www-form-urlencoded" header. This generates an error instead of a valid response.
Fix: The charset was removed as no charset should be specified.
4490523 Summary: A button to print the PDF is not available on the Read Agreement view.
Fix: A print button has been added to the Read Agreement view.
4494248 Summary: Incorrect Agreement Expiration Times in the agreement due to the client not passing timezone information.
Fix: The client has been updated to be timezone-aware.
4494297 Summary: When a user delegates an agreement on behalf of another user (using advanced account sharing), the audit report may not show the event of the delegation based on configured settings that omit or include data.
Fix: The function that omits data has been improved to account for situations where events take place that suppress some content, but retain the event.
4495537 Summary: Recipients get cancellation emails as CC'd participants when an agreement is sent via Workflow and subsequently canceled without the request to notify all parties when custom email templates are used.
Fix: The CSS for the CEMT templates has been updated to manage cancelation scenarios like non-custom templates do.
4495963 Summary: If delegation is disallowed for users in the account, the options to enable signing or e-sealing for a user profile is locked.
Fix: Dependency of delegation is removed in the UI and the setting can be updated
4496084 / 4510358 Summary: The correct selected radio button is not being set when the radio button is specified with an options list
Fix: When the option list is present in a radio button, we now get the selected radio button index from the list of options.
4497823 Summary: User message (“Invalid agreement id”) for a non-participating user session in the browser for GET /SigningUrls for a valid agreement.
Fix: Rephrase the user notification (“Invalid agreement ID”) to a meaningful message.
4498914 / 4501065 Summary: Users are not able to sign the document when the authentication type is Acrobat sign with bio pharma settings enabled due to an incorrect delimiter.
Fix: The delimited being used has been corrected.
4499847 Summary: The Digital settings are not honoring the UI settings, showing more providers than have been selected due to duplicate entries in the providers' list.
Fix: Cleanup code has been added to ensure duplicates are cleared before fetching the setting value, and before updating the setting value.
4500637 Summary: The creation data of a pdf is represented with a long value that is the milliseconds of Date, rather than using PDF date string format.
Fix: In the case that the Creation Date is represented by a CosNumeric, convert it to an ASDate by getting the CosNumeric as a String and then converting it to a long and then to Date object.
4500649 Summary: Auto-adjustment for font size is not functioning due to a bug in an upstream library
Fix: The library has been updated.
4501939 Summary: "Unexpected error" or "permission error" when the signer is making payment via Braintree due to unsupported configuration with AVS.
Fix: Some code has been added to ignore AVS where possible. Customers are cautioned that AVS configuration is incompatible with Acrobat Sign.
4502497 Summary: Initial field not set to Required by default in New Authoring layout
Fix: The default has been edited to be required.
4502759 Summary: Duplicated Japanese honorifics for Signers in Audit Report
Fix: We now use the user list string in all cases in createSignatureRequestedAuditEvent(). This will be accompanied by a string change where the honorific character is removed from all audit event strings used in the function.
4503010 Summary: Action GET /agreements/ID fails with 500 - Miscellaneous server error for a few agreements after September 17 due to an origin check.
Fix: The origin check has been removed.
4503107 Summary: When a sharee with SEND and SIGN permissions switches to the sharer's account and initiates a workflow where the sharer is the first signer, the user is redirected to the POST_SIGN page instead of the ESIGN page.
Fix: The in-place check has been updated to ensure that sharee has SIGN permissions for the group from which the agreement was sent are being used.
4503112 Summary: Auto-Cancellation of agreement - error AUTO_AUTHOR_FAIL due to an iText error.
Fix: iText has been removed where unrequited, resolving the error.
4503640 Summary: Form filler is unable to submit the document. Server error is seen after user clicks on 'Submit' on XFA documents
Fix: The library that evaluates PDFs for XFA has been improved to properly identify and remove XFA.
4504309 Summary:  Unable to send Draft folder agreements via Advanced Account Sharing due to missing endpoint in the filter.
Fix: Added the URL /account/requestSignatures/authoring in allowListedEndPointsBasedOnSendPermissions in filter.xml
4504567 Summary: Radio button values are being changed when agreements are generated via bulk send
Fix: Replaced the hashmap with linkedhashmap to maintain order of insertion when creating SiB child agreements
4504631 Summary: Processing workflow error Error message: Unhandled Error due to unsupported characters in an iText file
Fix: iText has been updated.
4504822 Summary: User Search is cleared if User list is taking too large, and a search is requested before a previous search is completed (such as the initial loading of users when the page is opened)
Fix: When data is received, we check if the requestID matches the most recent request. If it does, we process the response, if it doesn’t, we ignore it.
4504831 / 4507199 Summary: Signed agreement provides an invalid PDF 1kb in size due to a malformed PDFFont object that does not specify the required subtype of the font object.
Fix: The PDF-generating library has been updated to better manage malformed objects and provide a more graceful result.
4506230 Summary: Automatic Field recognition not working in Sandbox due to the annotation either being wrong or absent where we are looking for it.
Fix: We now seaarch each page and each annotation on that page to find the annotation of the form field to ensure we get the correct page.
4506959 Summary: Post-Sign Landing Page is showing HTML encoded characters
Fix: Fixed source template.
4508950 Summary: Fields that have a name containing an apostrophe throw an error in the new experience.
Fix: The field parsing code has been improved to manage apostrophes. 
4509503 Summary: Users are unable to sign documents through the Acrobat Sign application iOS due to a datafield being empty and throwing a null pointer exception
Fix: A null pointer check has been added to gracefully manage the circumstance.
4509713 Summary: Setting "Allow all users to share library documents with multiple groups" is being auto enabled when trying to enable "Allow administrator to share library documents with multiple groups" from Global settings due to an incorrect value being passed.
Fix: The correct value is now being used.
4510812 Summary: Aadhaar authentication in Workday is preventing signatures.
Fix: Aadhaar authentication support has bene added to Workday.
4512044 Summary: Modern esign throws error if the field name has a special character
Fix: Field name parsing has been improved to gracefully manage special characters in field names.
4516231 Summary: The wording in the Audit Report regarding the signing link "E-Signature hosted by (Sender name)" is thought to be too vague.
Fix: The string in the Audit Report has been updated to read "Signing link is created by (Sender name)".

 

Production deployment: March 17, 2025

GovCloud deployment: March 20, 2025

Experience Changes

  • New e-sign environment for OEM Partners - The new e-signing environment has been enabled for the Acrobat Sign OEM partners. This environment provides a superior signing environment for the recipients and includes the option to define a field layer that mobile customers can switch to, significantly improving the field-filling process.

Resolved Issues

Issue Description
4501733 Summary: Setting a custom email display value for a group does not apply to reminder and cancelation emails.
Fix: Reminder and Cancellation email templates updated to properly reflect the Display Email value.
4502251 Summary: Acrobat Sign authentication fails when the sending account is HIPAA enabled, and the sender and recipient have userIDs on different Acrobat Sign shards resulting in an Invalid access token error.
Fix: The Acrobat Sign authentication method has been improved to properly manage recipients with userIDs on different shards.
4504338 Summary: An unprocessed error is triggered when the first person signs an agreement, but the second recipient is delegated twice.
Fix: The delegation code has been rebuilt to ensure proper authority to the agreement is passed when chain delegating.
4504648 Summary: Checkboxes added through the API and that are enabled by default may retain their "checked" status on the final agreement even if unchecked during the signature process.
Fix: The inheritance of the checkbox value has been updated to ensure that the new values after a recipient is done are properly stored and reflected in the resulting PDF.
4506085 Summary: Error when copying large templates from sandbox to Production. Template created without fields due to timeouts in the process.
Fix: The time threshold has been extended for synching actions.
4507500 Summary: Acrobat (DC Web) users cannot upload attachments when applying a signature due to a missing path in the upload function.
Fix: The path to allow Acrobat users access to the upload functionality has been included.
4508102 Summary: The process of deleting pages from a combined agreement document can fail because an internal service can throw an exception when deleting page related objects such as bookmarks, structure, destinations which causes the entire operation of deleting a page from a PDF to fail.
Fix: The internal service has been improved to better manage bookmarks, and the like to  properly format the PDF to the Acrobat Sign expected standard.
4508673 Summary: When a signing reason is required, and a signature field is assigned to a non-signer role (e.g., Approver), if modern eSign is enabled, the user is redirected to the modern eSign page and is not given the option to enter the signing reason.
Fix: A check has been added for a requirement for signing reasons, and if present, the recipient defaults to the classic esign page.
4508674 Summary: Signed agreements with badly formatted destinations cannot be downloaded.
Fix: The internal library has been patched to better manage poorly formatted bookmarks and destinations.
4508934 Summary: In the Salesforce integration, the File Name is trimmed after "." in the Signed Pdf Email Notification
Fix: The string trimming function has been improved to identify strings after a period that are not extensions.
4509274 Summary: In the MS Teams environment, if the sender is the first (or only) signer, the agreement is not opened in a new tab after sending due to an empty value being passed in API redirection.
Fix: Improved the APi redirection by passing the correct values when triggering the signature process, and opening the new tab.
4509485 Summary: Deleting pages from a combined agreement document can fail because an internal service can throw an exception when deleting page-related objects such as bookmarks, structure, and destinations, causing the entire operation to fail. Users can be unable to download their agreement PDF with an error message: "The document is not yet available or will have no pages to view."
Fix: The internal service has been updated to wrap the deleting process in testing to better manage malformed PDFs.
4509562 Summary: Large agreements could present an issue where only the first several pages of the agreement would print to the PDF when opening the agreement on the Manage page due to an older sdk bundle.
Fix: The sdk bundle has been updated, resolving the issue.
4509684 Summary:  When calling GET /agreements/{agreementId}/documents/{documentId}) from the REST API, an error is triggered: "The server cannot send the response in a format requested in the Accept header" due to an incorrect content-type.
Fix: The content-type value has been corrected.
4509712 Summary: Only 100 groups are shown when trying to share templates with multiple groups.
Fix: The number of groups fetched from the API has been increased to 1000
4509989 Summary: If we have a Name field beside the Signature field on the Web form eSign page, after applying the signature, the Name field does not have the signer's name and it's not visible. 
Fix: An additional function was added to check the name value in the Name field and compare it to the existing value. If it has changed the field is populated with the new value.
4510498 Summary: Suppressing email notifications to recipients fails for Written signature agreements due to a lack of configurable settings to control it.
Fix: A new setting has bene added to explicitly manage this type of email distribution.
4511386 Summary: When a signer with a digital signature selects the option to download and sign, the participation counter increments before the signature is applied.
Fix: The logic that updates the system has been improved to better reflect the current status of the agreement.
4511390 Summary:  Group administrators don't have the authority to fully establish a share with their group users.
Fix: The sharing function for group admins has been updated to correct the issue.
4511902 Summary: The custom date tag is not working with the New experience when the display format includes quote marks (due to encoding).
Fix: Acrobat now decodes the value before saving it.
4517094 Summary: The link to the Terms of Use is failing due to the page being moved to a new source URL.
Fix: Updated the code to properly fetch the current URL.

Production deployment: April 22, 2025

GovCloud deployment: April 24, 2025

Improved Functionality

  • Send in Bulk: Bulk download - Senders can now download all completed child agreements from a Send in Bulk transaction directly from the Manage page. The ZIP file includes only completed agreements, named based on their transaction ID, while in-progress, canceled, declined, or expired agreements are excluded.
    Each download request supports up to 100 MB of data, offering a quick and efficient way to access finalized documents in a single step.
  • Enhanced Mobile Signing Experience - Senders can now enable and configure a mobile-optimized signing experience, giving recipients two viewing options:
    • PDF View – Displays the entire agreement for review and signing.
    • Field-Only View – Focuses on form fields, making completing and signing agreements on mobile devices easier.

This update streamlines the signing process, improving form completion rates and overall mobile experience.

  • CC’d parties for individual recipients in Custom Workflow Designer - The Custom Workflow Designer now allows each individual recipient to have dedicated CC’d parties. When enabled, CC’d parties receive notifications simultaneously with the intended recipient, ensuring better visibility and streamlined communication. This feature is available if the account is configured to allow it.
  • Checkbox and Radio Button: Show Field Border option - Checkbox and Radio Button fields now include an option to Show field border when viewing and printing the agreement. This option can be turned off when the uploaded document already contains pre-printed borders, ensuring a cleaner final document by preventing duplicate borders.
    The option is enabled by default and configured at the field level.  
  • Enhanced Automatic Form Field Detection  The automatic form field detection feature now places detected fields automatically, streamlining the form creation process. Users retain complete control and can edit, delete, or remove all placed fields with a single action.
  • New Option to Set Recipient Signature Type - Senders can now define the signature type for recipients when sending agreements through the modern Request Signature process. When enabled, a Signature Type drop-down appears in the Recipient settings section of the Compose page, showing the options allowed by group settings.
    • The setting defaults can be configured at the group level.
    • If the sender selects a signature type, the recipient must use that type.
      • The sender can select multiple options for the recipient.
    • The recipient can choose their preferred signature type if no selection is made.

This feature provides greater control over signature methods while maintaining flexibility when needed.

  • Improved User Management in Acrobat Sign - The Acrobat Sign user administration view has been updated to enhance visibility into the users’ status. The improved interface provides easier access to review pending invites and clear indicators for provisioning issues. The new interface also highlights the prominent actions admins can perform for each of the status categories (Add User, Send reminder, and Contact support) to streamline the user provisioning process.
  • 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.
  • New WhatsApp Delivery for One-Time Passwords - Acrobat Sign now supports WhatsApp as a delivery method for one-time passwords (OTP) to recipients' phones. This feature functions similarly to SMS delivery but leverages WhatsApp's technology and infrastructure, providing additional stability and a convenient communication option. WhatsApp OTP authentication is a premium authentication type that is available when composing new agreements.
  • Revisit Recipient Configuration from the Authoring Page - Senders using the new Request Signature experience can now navigate back to the Compose page from the Authoring environment to reconfigure recipients and their properties without losing progress. This allows for adjustments to recipient order and details while ensuring that existing field assignments remain intact (e.g., Signer 1 remains Signer 1). (If a participant is removed, their related fields will also be removed.)
  • New Authoring Environment for Library Templates - The library template authoring environment now features the modern authoring experience for field placement, making creating and customizing templates easier. Enhancements include:
    • Updated field placement tools for improved accuracy and efficiency.
    • Mobile-focused authoring allows users to create mobile-friendly templates that optimize the signing experience on mobile devices.

These updates streamline template creation and ensure a seamless experience for both senders and recipients.

  • New Identity Providers (IdPs) Added to Acrobat Sign - Acrobat Sign is expanding its list of supported identity providers (IdPs) to enhance the recipient's authentication options. The following new IdPs are now available:
    • OneID ID Check
    • OneID ID Proof 
    • OneID ID Assure 
    • OneID Sign-Up Plus

These additions expand Acrobat Sign's compatibility with global identity verification standards, supporting seamless and secure authentication across multiple industries.

  •  Expanded Country support for Phone Authentication – Phone Authentication and agreement delivery via SMS now support these additional Countries and Country Phone codes: 
    • Isle of Man (+44)
    • Guernsey (+44)
    • Jersey (+44)

Experience Changes

  • The modern Request Signature environment has become the default experience when creating a new agreement. All existing accounts have been switched to the modern environment
    • Users can no longer access links to switch between the new and classic environments.
    • Administrators still have the option to enable the classic experience through the admin menu.
    • Customers using the Notarize integration will not be affected by this change.
  • System administrators of a VIP account in the Admin Console are automatically assigned an Acrobat Sign entitlement - When an account initially purchases the Acrobat Sign service under a VIP license, they will have their users with System Administrator privileges automatically assigned an Acrobat Sign license.
    • New organizations will have all existing assigned System Administrators provisioned with an Acrobat Sign administrator-level entitlement.
    • Existing organizations that purchase an Acrobat Sign license will have all existing System Administrators provisioned with an account administrator-level Acrobat Sign entitlement.

The Acrobat Sign license is automatically entitled only when the Acrobat Sign services are first purchased for the organization. Entitlement does not happen for subsequently promoted System Administrators.

  • Improved Administrator Onboarding Checklist and Communications - Acrobat Sign administrators now receive enhanced support for managing account onboarding, including new tools and improved email communications.
    Improved onboarding features include:
    • Onboarding Checklist – A new Get Started tab has been added under the Admin page, providing a short checklist of key actions for new administrators when they first take control of an account.
    • Updated Welcome and Reminder Emails – The initial email notifications sent to new administrators have been revised to support the onboarding checklist, offering clearer guidance on the next steps in account setup.
    • Monthly Overview Email – Administrators will receive a monthly summary detailing:
      • Visibility into all user statuses and where administrators need to take action.
      • Number of transactions/seats consumed since the start of the contract. Administrators no longer need to navigate to the admin console just for this information.
      • A quick snapshot of the contract including the anniversary date.
    • Intelligent Existing Entitlement Detection and Notification - If a user’s previous Acrobat Sign entitlement is detected, the affected user will be included in a weekly notification email sent to all account administrators. Each such user may appear in up to three notifications.

These improvements help administrators manage their accounts more efficiently and stay informed about system activity and potential issues.

  • Improved User Login Experience - Acrobat Sign has streamlined the login and authentication process through the Adobe Identity Management System (IMS).
    • The user's organizational profile is automatically selected during the login process to the ones entitled with the Acrobat Sign service ( Identifying the request as coming from an Acrobat Sign source)
    • Users who encounter errors during login will have links in their error messages to contact their Acrobat Sign administrators for assistance.
    • All users assigned an active entitlement but have not logged in to the service will be sent up to two email reminders. (This also applies to existing inactive users before the release date)

These improvements simplify login, reduce friction, and improve the overall user experience.

Available environments: Commercial | Available tiers of service: Acrobat Sign Solutions | Configuration scope: Enabled by default; Not configurable
 

  • The Account tab renamed to Admin - The Account tab, available to Acrobat Sign account-level administrators, has been renamed to Admin. This is a cosmetic change to the tab label in the Standalone web version of the application. This update is implemented for the Commercial environment in April 2025 and the Government environment in May 2025.

Mobile application updates

  • Update to template file management - The template list in the Acrobat Sign mobile app now follows a structured format, making it easier to find specific templates. The structure aligns with the web version, organizing templates into sections such as:
    • My Templates
    • Group Templates
    • Account Templates

This update improves navigation and ensures consistency between the mobile and web experiences.

  • Improved Accessibility in Acrobat Sign Mobile Apps - The Acrobat Sign mobile applications now offer enhanced accessibility features, ensuring better compliance with accessibility standards. Updates include:
    • Improved color contrast for better visibility.
    • Keyboard shortcut support for easier navigation.
    • Enhanced screen reader compatibility for a more inclusive user experience.

These improvements make the mobile app more accessible to all users, providing a smoother and more user-friendly experience.

Available environments: iOS mobile application | Available tiers of service: Acrobat Standard, Acrobat Pro, Acrobat Sign Solutions | Configuration scope: Enabled by default

Integration Updates

  • Updated Acrobat Sign Connectors for Microsoft Power Automate - The Acrobat Sign connectors for Power Automate now support an improved agreement-sending process that allows documents to be loaded into the Compose page for editing recipient information and then sending the agreement to the Authoring environment for further field placement.
    Additionally, the Acrobat Sign connectors now support two advanced authentication methods:
    • Digital Identity Gateway
    • One-Time Password (OTP) via Email
  • Workday integration: Digital signatures with Aadhaar e-Sign - The Workday integration now fully supports the optional Aadhaar e-Sign service available in India, an online electronic signature service that facilitates digitally signing agreements based on OTP authentication and e-KYC verification.

REST API/Webhook Updates

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

  • GDPR Compliance: Delete User Info via API - Partners can now use the API to delete user information when removing a user's data in compliance with GDPR requirements. This enhancement streamlines data management and ensures regulatory compliance.
  • New Webhook Field: eventDateTimezoneOffset - Adobe Acrobat Sign introduces eventDateTimezoneOffset, a new field in the webhook payload for the AGREEMENT_ACTION_COMPLETED subscribed event.
    This field captures the recipient's timezone offset when they update the agreement, providing better visibility into the local signing time.
    • eventDateTimezoneOffset records the recipient's timezone offset in minutes relative to UTC (e.g., eventDateTimezoneOffset : "UTC-300")
    • The existing eventDate field remains unchanged and continues to store the action's UTC timestamp. The timezone offset does not modify the eventDate value.

This update enhances the tracking of signing activities across different time zones.

  • Migration of Acrobat Sign Developer Documentation - Acrobat Sign developer documentation is moving from opensource.adobe.com/acrobat-sign to developer.adobe.com/acrobat-sign. This migration ensures better integration with Adobe's developer resources, providing a more streamlined and centralized experience for developers.
     

Resolved Issues

Issue Description
4490799 Summary: Default Country Code can't be changed with New Experience Send page
Fix: The code was improved to ensure inherited group properties are pushed through all processes to complete agreement creation.
4501927 Summary: Discrepancy in PDF Handling Between Classic and New Authoring modes post release 
Fix: Improved the code to better access and use all field properties in the transformations of PDF files.
4503970 Summary: Inappropriate completion message when the 1st recipient is the Sender.
Fix: Updated the message to be role-aware so it shows the correct message.
4505208 Summary: [RequestSignature] CC field does not display Auto-complete options from the address book.
Fix: Addressbook functionality added to the CC field.
4507982 Summary: When multiple groups share with a user through advanced account sharing, a performance issue may happen when trying to access a Template under the Manage tab, Templates filter.
Fix: Refactored several functions to optimize for multiple group searching.
4508227 Summary: An unhandled error occurs when signing agreements originated through new authoring experience with payment fields.
Fix: Updated the endpoint to manage the field with less ambiguity,.
4508929 Summary: Error triggered for Custom Work Designer field labels that are under 100 characters due to special characters being encoded.
Fix: Special characters are decoded while validating the character limit.
4509141 Summary: An uni9nformative error triggers when sending an agreement with a witness, and the group is configured to require an authentication method, but the witness is configured for no authentication.
Fix: The configuration process now includes an error message indicating when two-factor authentication for all recipients is configured and a witness is used.
4509366 Summary: FedRAMP customer name update failed with special characters due to the characters not being replaced with their HTML entity numbers.
Fix: Updated the process to properly manage special characters in the FedRAMP environment.
4509680 Summary: Add countries Isle of Man, Guernsey, and Jersey for the country code +44.
Fix: Added the COUNTRY_CODE constants for Isle of Man, Guernsey, and Jersey
4510255 Summary: Attempting to create a user that already exists in another group appears to create the user in the group with no useful.
Fix: The error has been improved to indicate the user has been moved to the new group (not created).
4510309 Summary: When a signature block is added through API with inputType other than BLOCK, The signature process is routed to the classic experience due to the BLOCK not being identified properly.
Fix: Improved the condition to return additional information to properly identify the BLOCK object.
4510652 Summary: Digitally signed form fields need to be flattened prior to modifying the PDF for the next signer
Fix: Digital signature form fields that have been signed are invalidated when submitted by a written agreement workflow.
4511819 Summary: The signature's blue line appears in the PDF document for unsigned signature fields. 
Fix: Unsigned signature fields are skipped while rendering signature fields into the PDF document.
4511965 Summary: Digital Identity Gateway login hint isn't working due to applied ID checking when fetching the ID criteria.
Fix: Removed the email and name matching check while fetching auth criteria for DIG_ID.
4513228 Summary: Missing field value in pdf document when the field name contains extra space due to the field name being trimmed on the backend.
Fix: Trimming the field name on the front end to keep the field name consistent.
4513358 Summary: File processing issue in Adobe Sign Sandbox instances die to form fields with no references to pages. In such cases the page is null, and a null pointer is thrown.
Fix: Added a null check for this event to properly manage it.
4513464 Summary: Admin encounters multiple errors while interacting with templates via advanced account sharing because the API is evaluated under the session user's permissions (e.g., Editor_User) instead of the switched user's permissions (e.g., Creator_User).
Fix: Added the x-on-behalf-of-user header to the API request to ensure the request is evaluated under the switched user's (Creator_User) permissions.
4513575 Summary: Form field data is not resizing for multi-line fields.
Fix: Updated code with to allow auto sizing.
4513914 Summary: When number of ACTIVE users in account is equal to MAX_ACTIVE_USERS value, then changing a password is not allowed because of a MaxActiveUsers check.
Fix: Improved the function to properly ignore this check when the user is ACTIVE.
4514839 Summary: User cannot sign with multiple digital signatures on an agreement if the first field signed is not the first signature field at the top of the document. 
Fix: Added method to iterate over all fields and extract valid ticket that is further used for X-JWT-Assertion header.
4515343 Summary: Font size of multiline input field is changing on the e-sign page. Font size is multiplied by zoom factor, so the size of input varies depending on it - specifically, it is adjusting dimensions of a page.
Fix: The method for getting the font size of multiline field is returning font size in px, without multiplying it by a zoom factor.
4515735 Summary: After signing an agreement, the Manage button on the post-signing page returns a malformed page.
Fix: The post-sign page has been corrected to properly fetch the information needed to render the page.
4516641 Summary: It is possible for the annotation of a form field to not be attached to a page.
Fix: A null check has been added to the annotation list of the page.
4517113 Summary: Document problem email received when sending agreement via API through a developer account due to null pointer errors when checking form fields.
Fix: We are now checking if the list of form fields is null before asking if the list is empty.
4517156 Summary: When there are existing form fields on a set of input PDF's, form field generators are not allowed to run to produce additional form fields.
Fix: When there is a list of form field generators to process, we will add that task to the list of tasks to run after the ReadPDFTask

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
  • 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

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.
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
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.
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.
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.
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.
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.
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. 
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.
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.
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.
Fix: The template picker sourced from the Home page has been updated to properly fetch the shared template.

Adobe Acrobat Sign Release 16.1

Production deployment: July 22, 2025

GovCloud deployment: August 5, 2025

Improved Functionality

  • Use WhatsApp to send agreement links directly to a recipient's mobile device - The WhatsApp integration in Acrobat Sign has been expanded to include the option to send agreement notification and reminder links directly to a recipient's WhatsApp enabled device.
  • Native PDF/A support for long-term document preservation - Acrobat Sign now supports validation and export of documents in PDF/A-2b format (ISO 19005), helping organizations meet stringent archiving standards and regulatory requirements. Documents retain their PDF/A conformity across the full agreement lifecycle—upload, signing, and storage.
  • Prevent Adobe Acrobat Sign from being embedded in third-party websites - Clickjacking Defense adds iframe protection to Acrobat Sign pages accessed through REST API v5+. Framing is only allowed when using auto login with a declared parent domain, helping prevent deceptive or unauthorized embedding.
  • Improved control over group-based sharing - Organizations using advanced account sharing can now optionally restrict the shared view of their agreements to only those agreements sent from the user's group. Agreements sent to a user from an external group will be filtered out to protect potentially private user communications that would be inappropriate to share generally. This filter only applies to the group-level shares (sharing a group to another group or user), and does not apply to user-based shared (sharing a user to a group or another user).
  • Updates for VIP-licensed customers:
    • Streamlined admin setup from the Home Page - Acrobat Sign introduces a new Account management section to help account admins quickly access key configuration tools. Add users, organize groups, connect integrations, and migrate templates directly from the Home Page—no digging required.
    • Add users to the Admin Console from Acrobat Sign – Admins can now add users directly from the Users page in Acrobat Sign, automatically updating the Adobe Admin Console.
    • Admin Console Role assignment now available through Acrobat Sign  - To streamline setup, Acrobat Sign now allows account admins to assign key Admin Console roles—Product and Support Admin—without leaving the product interface.
    • Easier access to the suite of third-party integrations - A new Integrations page has been added to the admin menu, providing direct, intuitive links to the setup files for the individual integrations.
    • Easier HIPAA onboarding through in-product guidance - Organizations subject to HIPAA can now begin the enablement process within Acrobat Sign via a new self-service workflow through the Get Started admin menu. The system sends an automated request to Support and tracks progress based on the BAA signature and system configuration.
    • Fast-track your template migration to Acrobat Sign with automated template conversion - The new template migration feature helps account admins quickly bring their templates into Acrobat Sign. Upload a template ZIP file, convert it automatically, and review results in the authoring environment—no technical expertise needed.
    • Acrobat Sign Smart Assistant Chatbot - The new Smart Assistant gives you in-app answers to common questions like how to add users, check usage, or update settings. Ask your question in plain language and get step-by-step guidance, relevant HelpX articles, or links to support pages. 
  • Acrobat Sign for Government gets updated to the modern experience:
    • Acrobat Sign for Government: Access to the modern Request Signature interface - GovernmentCloud administrators can now enable their account or groups to use the modern Request Signature interface.
    • Acrobat Sign for Government: Mobile-first upgrade for recipients - Government users can now access the modern interface, designed to simplify signing on mobile devices through an easy-to-configure, form field-only interface.
    • Acrobat Sign for Government: New Create Template interface available - Government users now have access to the modern Create Template interface, which streamlines the template design process and improves usability.
  • New Trust Service Provider (TSP) - Acrobat Sign is expanding its list of supported Trust Service Providers (TSPs) to enhance the recipient's authentication options. The following new TSP is now available:
    • eID Easy

This addition expands Acrobat Sign's compatibility with global standards, supporting seamless and secure digital signatures across multiple industries.

Experience Changes

  • Improved digital signature experience - The process for applying a cloud-based digital signature has been refined to reduce the number of interactions the signer must complete when applying a digital signature.
  • The character limit for labels in the Workflow Designer has been increased to 500 characters -  When creating or editing a custom workflow in the Workflow Designer, the labels used to describe fields can now accept up to 500 characters (improved from 100 characters).
  • The New custom workflow experience control has moved to the Global Settings menu - The configurable option to Set the new custom workflow as the default experience has moved from the Send Settings page to the Global Settings page.
    A new control has been added to expose "switch links" for users to switch between the new experience and the classic version.

Resolved Issues

Issue Description
4501772 Summary: For the modern request signature experience, the recipient message does not update when the language is changed in the Agreement settings.
Fix: The code to accept the new language preference has been updated to address the change for messages when a new language is selected.
4503504 Summary: In rare cases, retries during agreement creation can result in multiple copies of the same child agreement being generated using Send in Bulk
Fix: Multiple updates to how child agreements are generated and listed internally with checks to ensure no duplicates can be created.
4511072 Summary:  Transaction Consumption Report emails are not received after using the "Send it now" option.
Fix: The mailing system was updated to resolve a delivery issue.
4511224 Summary: PDF files set to "Inherited" zoom before sending the default to "Fit to page" after signing,
Fix: Annotation handling has been improved to ensure properties are correctly confirmed to the resulting PDF.
4512546 /
4522458		 Summary: Shared workflows do not display field templates as expected for accounts sharing through Advanced Account Sharing.
Fix: The GET /libraryDocuments/id/formFields request has been updated for the x-on-behalf-of-user header that is required for the advanced account sharing use case.
4515020 Summary: The PUT /users/{id}/groups API call returns a 403 error when attempting to move a user who is not in the Default Group by a group level admin
Fix: Aurthority has been extended to Group admins, who are now able to add users to their group, even if the assigned user is currently in another non-default group.
4516121 Summary: When a group of radio buttons has individual tooltips, only the first tooltip displays for all options during signing.
Fix: The radio button code strictly employed one tooltip for the array of buttons. It has been updated to allow individual representation.
4516129 Summary: Agreements expire based on the UTC equivalent of the sender’s local time, not the intended local time. 
Fix: The logic that checks expiration time is no longer based on the browser time, instead allowing the core application to do the validation.
4518192 Summary: Signers are intermittently unable to complete the signing process when using Adobe Sign Authentication with Okta SSO.
Fix: Remove the crossShardLoginPage attribute from the session after successful login.
4521018 Summary: When using the modern signing experience, dropdown fields configured with export values return the visible label instead of the export value in the /formData API response.
Fix: Hidden (export) values are now being sent instead of the visible values.
4521111 Summary: In the new authoring experience, users are unable to scroll through and view all available field templates from the Field Templates dropdown.
Fix: The modern authoring experience has been updated to load more than just the first page of field templates.
4521311 Summary: Due to a known 12-hour delay in the agreement expiration mechanism, reminders are being sent after the effective expiration time, resulting in failed signing attempts and user confusion.
Fix: For recurring "Until Signed" reminders, the signing deadline is checked and will no longer send the reminder, but will leave it active so it can be picked up if the sender edits the signing deadline before it actually expires during the 12-hour grace period.
4522059 Summary: When a signer uploads a file using an Attachment field and then completes a Digital Signature, the Download Document link results in a "Page Not Found" error.
Fix: The checksum was eliminated from duplicate detection, as it's an optional property in the PDF spec. Acrobat Sign continues to use the file name and size to identify duplicates.
4522382 Summary: Users are unable to complete transactions when using Click to Sign with authentication enabled. After signing in, the transaction does not complete and must be retried
Fix: The crossShardLandingPage URL parameter was removed from the session post login.
4522384 /
4523594 /
4523900		 Summary: When using the Bulk Send feature, no agreements are sent on the initial attempt, but a second attempt works as expected due to task queuing on the local shard.
Fix: Task queuing has been refined to ensure tasks aren't delayed.
4522497 Summary: The timestamp format on agreements changes from HH:MM:SS to HH:MM after the document is signed, resulting in loss of seconds in the final audit trail.
Fix:  Seconds have been added to the timePatern.
4522509 Summary: CC recipients can not view the agreement context board when accessing LDV-enabled agreements via the email link. Instead, they receive a "Document not yet visible" error.
Fix: Code amended to provide the needed access to view the context board.
4522547 Summary: When using a template, the final PDF may display misaligned or missing form field data after signing due to page rotation being applied after every annotation.
Fix: Page rotation has been corrected.
4522914 Summary: When using the new Send in Bulk feature, customers may encounter an error during CSV upload if the values in the Agreement_Message or Private_Message columns exceed a certain character limit. 
Fix: The character limit was documented in customer-facing collateral.
4522945 Summary: When trying to edit the reusable document as an account/group admin and trying to apply a field template NullPointerException occurs when checking origin participation
Fix: Added method to find origin participation when editing library documents as account/group admin
4523043 Summary: When editing a web form that includes a participant with the role set to Delegator, the Modify Web Form page fails to load. A console error is triggered, preventing any edits.
Fix: Added a check which ensures that if the ROLE_MAP is undefined, the code does not read the className as undefined and throw an error. Instead, it returns undefined.
4523061 Summary: Signed documents attached to emails retain their original file extensions in the filename, resulting in redundant naming 
Fix: No longer trim the filename substring if it starts with '.' and it is different from the extension.
4524122 Summary: In the New Experience, attempting to start an agreement from a saved Workflow results in a system error due to an exceeded character limit.
Fix: Label limits have been updated to allow 500 characters.
4524162 Summary: Link validation prevents sending agreement on New Authoring Experience
Fix: A parameter has been added to the new experience to check for the Errors hook, allowing for a more relaxed management of hyperlink validations.
4524356 Summary: Users encounter a "Server Error: We encountered an error while processing your request" message when attempting to sign agreements due to the -1 border width not being interpreted correctly.
Fix: Now interpreting -1 as a default 1pt border and only added a border if the border was greater than zero.
4524410 Summary: In the New Send experience, when using a workflow and uploading a new file after deleting the preset agreement name, the Agreement Name field does not update automatically. 
Fix: Added a fix to remove the default value for the onBlur event and introduced logic to set the first uploaded document's name in the document name text field.
4524614 Summary: The font used by text form fields in the PDF does not match the font chosen on the authoring page. The text field font is always SourceSansPro-Regular.
Fix: Extended the ExternalFont.getFontReplacementMapping to include regular, bold, and italic fonts. 
4525098 Summary: The signature-requested email is not sent to signer2 when the sender is signer 2 and the sender replaces signer 1.
Fix: Parallel recipient lists have been improved to manage the use case where an existing recipient is used to replace another recipient in the same recipient set.
4525377 Summary: Electronic seals (eSeals) not working with the Modern Request Signature Experience
Fix: Add a test case to verify electronic seal recipient in a non-UMG workflow, where the seal is restricted to group access.
4525491 Summary: Agreement names containing non-Latin characters (e.g., Chinese, Japanese, Thai, Korean) appear as ?????? in the recipient's Manage tab and email notifications when sent via Send in Bulk.
Fix: Documentation has been updated to indicate that the UTF-8 format is needed
4525653 Summary: Agreements sent using the API with JPEG files are being automatically canceled due to a document processing error. The issue occurs after the files are uploaded successfully but before the agreement is sent.
Fix: Added support for JPEG SOI app0-15
4526153 Summary: The scale of the stamp field behaves differently in the old and new authoring screens.
Fix: The new authoring environment has been updated to scale the stamp field consistently with the classic version.
4527031 Summary: When the "Allow senders to select signing order" is unchecked in New experience, the option "Recipients must Sign in order" remains visible
Fix: The code regarding access to this control has been improved to properly suppress the option when the setting dictates.
4527284 Summary: Agreements that include certain scanned or flattened PDF files are failing during authoring and are automatically cancelled with the error AUTO_AUTHOR_FAIL due to an internal library that is not managed.
Fix: Implemented a method that catches any exception and logs it, but does not interrupt the generation of an agreement.
4527948 Summary: When a calculated Acroform field is imported into Sign, the REST API returns a field containing { calculated: true, valueExpression: '' }, which causes the field to be displayed with a validation error.
Fix: Fields identified in this use case are now updated to be manually entered, not calculated.
4528062 Summary: Get /users API call failing for Salesforce users with very large user numbers
Fix: A new version of the Salesforce integration improves the process for getting the list of users to be more efficient.
4528284 Summary: Incorrect country code of the Cayman Islands for Phone Authentication under New Experience
Fix: The country code has been updated.
4529259 /
4529319		 Summary: Optional Signers' Names and 2FA Required Despite Workflow Configuration in New Custom Workflow Send Experience
Fix: Provided a check for optional recipients so whenever no email ID is present, the auth verification (phone, password, kba) will not fail any validation. Similarly, the name will also not be mandatory for optional recipients unless the email ID field has some input.
4530084 Summary: Some users are experiencing a blank screen when accessing Recipient Settings in the New Send Experience. The issue is caused by a missing translation for a specific country code label, and it affects all locales except en-US.
Fix: The correct translations have been published and pinned to the appropriate functions.
4530537 Summary: An NPE is produced when trying to convert a named destination into a location, preventing agreements from being sent.
Fix: A new check is in place to determine if the destination is a named destination and skip it.

Previous Releases

RELEASE NOTES: 2025

RELEASE NOTES: 2024

RELEASE NOTES: 2023

RELEASE NOTES: 2022

RELEASE NOTES: 2021

RELEASE NOTES: 2020

RELEASE NOTES: 2019

RELEASE NOTES: 2018

RELEASE NOTES: 2017

RELEASE NOTES: 2016

RELEASE NOTES: 2015

RELEASE NOTES: 2014

Get help faster and easier

New user?

Quick links

View all your plans Manage your plans
View quick links
Hide quick links

Legal Notices    |    Online Privacy Policy