Adobe Acrobat Sign rolls out at least three updates per year, categorized as major or minor releases. Additional minor updates may be introduced as needed to address system or customer issues.

Major Releases bring significant updates, new features, and multiple enhancements.
Minor Releases focus on smaller improvements and user experience tweaks. These occur between major updates, typically one to two times per cycle.

To prevent disruptions, new features are disabled by default and must be manually enabled by an account or group admin.

For Health and Life Sciences customers requiring compliance validation, Acrobat Sign partners with a third-party vendor to provide a validation package for every major release containing features to minimize your risk factor.

Note

This Prerelease Notes page is regularly updated as new information becomes available, so its content is relatively dynamic.

While this page is localized, the process takes time, which may result in localized versions differing slightly from the authoritative US English version.

For the most accurate and up-to-date information, we recommend referring only to the US English page.

The prerelease schedule and notes are listed below.

Adobe Acrobat Sign follows a structured schedule for publishing release notes and documentation updates:

8 Weeks Before Production Release

The prerelease page publishes a summary of expected features and updates, typically four weeks before the Sandbox launch.
Any feature changes after this point are noted in the Errata section.
Resolved issues are not included at this stage.

4 Weeks Before Production Release (Sandbox Launch)

The prerelease page is updated with detailed documentation on new and updated features.
Links to prerelease support documentation (available in US English only) are added as needed.
The initial Resolved issues section is published, with ongoing updates over the next four weeks.

Launch Day

The official release notes are updated with final feature details and links to production support documentation.
The prerelease page is refreshed to highlight the next release cycle.
Documentation is published after release verification in the live system, typically after 7 pm PT, though complex updates may take longer.
The final Resolved issues list is added to the US English release notes, with localized versions updated later.

Government Cloud Release

The Government Cloud environment typically updates between two days and several weeks after the production release, as some features may require additional evaluation before deployment.

Note

Sandbox documentation is designed for the production environment. Links found in the prerelease content target production URLs, meaning those links may lead to older existing documentation or 404 results if the target page is new and hasn't been published yet (e.g., when the link is pointing to a new feature in the same release).

The new pages will be published when the release is published, and links will properly resolve to their production URLs.

Sandbox availability

Customers accessing the Acrobat Sign Sandbox environment can typically access the new release functionality four weeks before launch.

The Sandbox environment must pass all production quality assurance procedures at the same quality level as the regular production environment.
Adobe strives to have 99.9% availability in the Sandbox environment, but customers should note that the Adobe Unified SLA does not formally cover the Sandbox.
The Sandbox environment uses the same status page and outage procedures as the regular Production environment.

Releases

Alert

This article contains prerelease information. Release dates, features, and other information are subject to change without notice.

May 5, 2026 (Major release) v17.1

Adobe Acrobat Sign release v17.1

Sandbox deployment: April 7, 2026

Production deployment: May 5, 2026

GovCloud deployment: May 12, 2026

Improved Functionality

In-Person Signing – Enable hosted signing sessions in the web application
In-Person Signing allows a sender to designate an internal host who facilitates an in-person signing session using a web browser. The host launches a controlled signing session from the Manage page or an email notification, temporarily hands the device to the signer to complete required actions, and regains control at completion. Session creation and completion are recorded in the audit trail, and signers may optionally provide an email address to receive a copy of the agreement.

Available environments: Sandbox, Commercial | Available tiers of service: Acrobat Sign Solutions | Configuration scope: Account and Group
Review how to enable the in-person signing role >
Review how to configure an agreement to allow in-person signing >
Review how to host in-person signing >

Bulk Digital Signature from the Manage page – Apply a digital signature to multiple agreements with a single authorization
Signers can select multiple agreements in the Waiting for you view and apply digital signatures as a bulk action using a single signing authorization. This reduces repetitive signing steps for high-volume workflows while preserving existing cloud signing security, authentication, and audit controls. Bulk signing requires signers to review or skip all agreements before completing the bulk action.

Available environments: Sandbox, Commercial, Government | Available tiers of service: Acrobat Sign Solutions | Configuration scope: Account and Group
Review the How to enable bulk digital signatures documentation >
Review the How to sign with bulk digital signatures documentation >

Send Only to Internal Recipients – Restrict agreements to be sent to recipients within the same Acrobat Sign account.
The Send Only to Internal Recipients setting prevents users from sending agreements to recipients outside their Acrobat Sign account. When enabled, agreements can be sent only to recipients whose account IDs match the sender’s. This control supports internal security requirements and prevents agreements from being shared externally.

Available environments: Sandbox, Commercial, Government | Available tiers of service: Acrobat Sign Solutions | Configuration scope: Account and Group
Review the configuration document to limit a group to internal recipients only >

Phone Transaction Usage Reporting – Expanded reporting with group-level visibility and scheduled report access
Phone transaction reporting now provides visibility into purchased quantities, quota start dates, and detailed consumption across SMS and WhatsApp transactions. Customers can track usage at the group level and access scheduled CSV reports through a unified reporting experience, enabling more accurate budgeting, internal allocation, and proactive monitoring to prevent service disruption when transaction limits are reached.
Reporting is now generated through scheduled reports in the reporting interface, with API access available to retrieve the latest report output.

New endpoint: POST /api/rest/v6/reportDownload
This endpoint accepts a scheduleId and returns the download URL for the most recently generated CSV report associated with that schedule.

Available environments: Sandbox, Commercial, Government | Available tiers of service: Acrobat Sign Solutions | Configuration scope: v6 REST API
Review the documentation for the SMS consumption report >

Experience Changes

Signature Appearance in Audit Reports – Logs the signature input method used by each signer, increasing compliance visibility and reducing manual verification
Audit reports now record the signature appearance method used when a signer applies their signature. For each ESIGNED event, the audit trail identifies whether the signer used a typed signature, a drawn signature, an uploaded image, or a mobile-based draw or image capture. This enhancement enables compliance and operations teams to verify signature methods directly from the audit report, reducing ambiguity and preventing unnecessary agreement rejections.
Signature appearance types:
- Type: Signer types their name and selects a font-based signature style.
- Draw: Signer draws their signature using a mouse or trackpad on a desktop.
- Image: Signer uploads a signature image file from the desktop.
- Mobile Draw: Signer draws their signature using touch on a mobile device.
- Mobile Image: Signer uploads or captures a signature image on a mobile device.

Available environments: Sandbox, Commercial, Government | Available tiers of service: Acrobat Standard, Acrobat Pro, Acrobat Sign Solutions | Configuration scope: Always enabled; no configuration

Saved Signatures for API Signing URLs – Allows use of saved profile signatures during API-based signing
Allow registered users to apply their saved profile signatures when signing agreements through API-generated signing URLs (GET /agreements/{agreementId}/signingUrls). Saved signatures appear for internal signers, and for external signers who authenticate using email OTP or Adobe ID. This capability streamlines signing workflows for backend integrations while maintaining account-level security controls.
Enabled by Adobe on a per-account basis following security review.

Available environments: Sandbox, Commercial, Government | Available tiers of service: Acrobat Sign Solutions | Configuration scope: Disabled; Contact Support

Personal address book management in the modern experience – Users can delete saved email addresses directly from their personal address book in the modern Request Signature experience, making it easier to keep personal recipient lists accurate and up to date.

Available environments: Sandbox, Commercial, Government | Available tiers of service: Acrobat Sign Solutions | Configuration scope: Enabled by default; not configurable.
Review the updated document for deleting an email from your address book >

Agreement Expiration Window – Extended default expiration period to 365 days
The maximum completion deadline for agreements has been extended from 180 days to 365 days. When document expiration is enabled, agreements are now automatically assigned a 365-day expiration date that cannot be removed. This change ensures all agreements have a defined lifecycle, improves long-term tracking and compliance, and reduces the risk of agreements remaining open indefinitely while still allowing users to set earlier deadlines when needed.

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

Revamped Home Page – Improves workflow access, surfaces critical actions
The Home page has been redesigned to make it easier to start agreements, monitor activity, and access key features, including the ability to copy recently sent agreements, view action tiles in a more intuitive order, quickly identify In Progress and Waiting for You items, and experience a streamlined What’s New banner that reduces visual clutter, helping users move faster, reduce missed agreements, and navigate a more focused Home experience.

The new Home page will be rolled out across 10 days after the release. Refer to the Technical Notice for the schedule >

Available environments: Sandbox, Commercial, Government | Available tiers of service: Acrobat Sign Solutions | Configuration scope: Enabled by default
Review the new Home page layout >

Trial Enhancements and Expanded Eligibility – The latest onboarding experience has been added for enterprise trials
Business trials now include the enhanced onboarding experience introduced in recent releases. Users with no Acrobat Sign entitlements receive full trial access.

Available environments: Commercial | Available tiers of service: Acrobat Sign Solutions for business Trial | Configuration scope: Trile entitlement

New Custom Workflow Designer becomes default – Promote modern designer, remove user switch controls, retain admin flexibility
The new Custom Workflow Designer experience is now the default for all accounts. Users no longer see switch links to revert to the classic designer, while administrators retain the ability to re-enable access to the previous experience if needed. This update advances the transition to the modern workflow design interface while preserving administrative control during the transition period.

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

REST API/Webhook Updates

The below updates are presented in the prerelease notes for disclosure purposes. Full documentation for API and Webhook updates can be found in the Acrobat Sign developer documentation when the version update is delivered to the production servers.

mTLS key management for webhooks – Add Acrobat Sign-generated key option, enable certificate signing workflow, improve security compliance
Developers can now choose how private keys are managed for webhook mTLS authentication in Acrobat Sign. In addition to the existing model where customers generate and upload their own private key and certificate, Acrobat Sign can now generate the private key and a certificate signing request (CSR). Customers can use the CSR to obtain a certificate from their certificate authority and upload it to complete the configuration. This option improves security by keeping private keys within Acrobat Sign while maintaining compatibility with existing webhook mTLS behavior.

Available environments: Sandbox, Commercial, Government | Available tiers of service: Acrobat Sign Solutions | Configuration scope: v6 REST API POST /webhooks endpoint; all scopes
Review the updated mTLS documentation >

Digital identity initialization via login_hint parameter – Allows API senders to initialize Digital identity authentication with a recipient-specific login identifier.
Several v6 REST API /agreements endpoints now support a loginHint parameter that allows API senders to initialize Digital Identity Gateway authentication using a known login identifier, such as an email address or user ID number. The identity provider controls the user experience, but the identifier typically pre-populates the login screen to strengthen high-trust authentication workflows and reduce impersonation risk. The identifier appears in masked format on the Digital Identity Gateway landing page and in the audit report to preserve traceability while protecting sensitive data.
The following endpoints have been updated to include the loginHint parameter:
- POST /agreements
- PUT /agreements/{agreementId}
- PUT /agreements/{agreementId}/participantSets/{participantSetId}/participants/{participantId}/securityOptions
- GET /agreements/{agreementId}
- GET /agreements/{agreementId}/members/participantSets/{participantSetId}
- GET /agreements/{agreementId}/participantSets/{participantSetId}/participants/{participantId}/securityOptions
- GET /agreements/{agreementId}/members

Available environments: Sandbox, Commercial, Government | Available tiers of service: Acrobat Sign Solutions | Configuration scope: v6 REST API

Release errata - Elements added

Below are items that have been added to this release since the initial publishing of the pre-release notes.

Phone Transaction Usage Reporting – Expanded reporting with group-level visibility and scheduled report access
Phone transaction reporting now provides visibility into purchased quantities, quota start dates, and detailed consumption across SMS and WhatsApp transactions. Customers can track usage at the group level and access scheduled CSV reports through a unified reporting experience, enabling more accurate budgeting, internal allocation, and proactive monitoring to prevent service disruption when transaction limits are reached.
Reporting is now generated through scheduled reports in the reporting interface, with API access available to retrieve the latest report output.

New endpoint: POST /api/rest/v6/reportDownload
This endpoint accepts a scheduleId and returns the download URL for the most recently generated CSV report associated with that schedule.

Available environments: Sandbox, Commercial, Government | Available tiers of service: Acrobat Sign Solutions | Configuration scope: v6 REST API

Agreement Expiration Window – Extended default expiration period to 365 days
The maximum completion deadline for agreements has been extended from 180 days to 365 days. When document expiration is enabled, agreements are now automatically assigned a 365-day expiration date that cannot be removed. This change ensures all agreements have a defined lifecycle, improves long-term tracking and compliance, and reduces the risk of agreements remaining open indefinitely while still allowing users to set earlier deadlines when needed.

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

Personal address book management in the modern experience – Users can delete saved email addresses directly from their personal address book in the modern Request Signature experience, making it easier to keep personal recipient lists accurate and up to date.

Available environments: Sandbox, Commercial, Government | Available tiers of service: Acrobat Sign Solutions | Configuration scope: Enabled by default; not configurable.

Release errata - Elements removed

Below are the line items that previously were announced as part of this release, but have since slipped to a later release date.

Enhanced Resource hub – Reorganizes learning and support links within Acrobat Sign
The updated Resource hub improves how users access learning and support materials directly within Acrobat Sign. Content is organized into structured sections with embedded video tutorials and direct access to webinars, release notes, customer stories, and support resources. These updates make educational content easier to locate within the product experience.

Available environments: Sandbox, Commercial, Government | Available tiers of service: Acrobat Sign Solutions | Configuration scope: This updated experience is enabled by default

Notification controls via Agreements API – Added multi-level controls to disable email notifications in the POST /agreements and POST /agreements/{agreementId}/reminders endpoints.
Developers can disable INITIAL, INTERMEDIATE, FINAL, CANCELLATION, and REMINDER email notifications when creating agreements through the v6 REST API. The solution introduces disabledNotificationTypes arrays at multiple levels in the request, allowing targeted control per role:
- participantSetsInfo[].disabledNotificationTypes — Disables email notifications for all members in a participant set
- ccs[].disabledNotificationTypes — Disables email notifications for individual CC recipients
- senderDisabledNotificationTypes — Disables email notifications for the agreement sender

The API-level senderDisabledNotificationTypes field takes absolute precedence over sender notification preferences as configured in Personal Preferences.

Available environments: Sandbox, Commercial, Government | Available tiers of service: Acrobat Sign Solutions | Configuration scope: v6 REST API

Recipient Filter in Reporting – Add recipient-based filtering to reports and data exports.
Add a Recipient filter to modern Reporting for Agreement and Transaction reports and Data Exports. Administrators can filter by recipient email to return all agreements that include the specified recipient, regardless of role or signing order. The filter supports autocomplete and multi-select behavior consistent with the existing Sender filter and applies to both visual reports and CSV exports.

Available environments: Sandbox, Commercial, Government | Available tiers of service: Acrobat Sign Solutions | Configuration scope: Enabled with Modern Reporting

Bio-Pharma (CFR) Support in Modern eSign – Adds signing reason capture and enforced sign-time reauthentication
Acrobat Sign completes Bio-Pharma support in the Modern eSign experience by adding signing reason capture and enforced reauthentication during signing. Organizations operating in regulated environments can require a signing reason, enforce reauthentication for each signature or at final click-to-sign, and maintain compliant audit reporting — all within the Modern interface.

Available environments: Sandbox, Commercial, Government | Available tiers of service: Acrobat Sign Solutions | Configuration scope: Support for Bio Pharma settings in Modern eSign is enabled by default.

Inline Document Editing During Authoring – Enable senders to edit document text directly within the authoring experience
Allows senders to edit document text directly within the authoring experience before sending an agreement for signature. An Edit Document option lets users modify text without downloading and re-uploading the file, while preserving existing fields and agreement configuration. This streamlines pre-send corrections and reduces disruption during agreement preparation.

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

Customer-Managed Keys – Enables encryption at rest using AWS KMS or Azure Key Vault keys
Customer-Managed Keys provide account-level encryption at rest using a customer-managed key in AWS Key Management Service (KMS) or Azure Key Vault. Account administrators can onboard a customer-managed key and re-encrypt supported content, rotate or revert key versions, suspend the key (causing encrypt and decrypt operations to fail), or destroy the key, which permanently prevents access to encrypted content.

Available environments: Sandbox, Commercial | Available tiers of service: Acrobat Sign Solutions on AWS environments | Configuration scope: Account only

SMS Usage Reporting API – Retrieve purchased quantities and track SMS consumption
The SMS Usage Reporting API provides visibility into SMS entitlements and consumption to support budgeting and service continuity planning. Organizations can retrieve total purchased SMS quantities, track overall usage to date, and query consumption by group and date range. This enables proactive monitoring and internal allocation to prevent disruption when credits approach exhaustion.
New endpoints:
- GET /api/rest/v6/smsUsage
- GET /api/rest/v6/smsUsage?groupId={groupId}
- GET /api/rest/v6/smsUsage?startDate=YYYY-MM-DD&endDate=YYYY-MM-DD
- GET /api/rest/v6/smsUsage?groupId={groupId}&startDate=YYYY-MM-DD&endDate=YYYY-MM-DD

Available environments: Sandbox, Commercial, Government | Available tiers of service: Acrobat Sign Solutions | Configuration scope: v6 REST API

Modern Request Signature becomes default – Retire Classic Compose, remove switch controls, standardize signing experience
All accounts are now transitioned to the modern Request Signature experience, replacing the classic Compose interface. Switch links and admin controls to revert to the classic experience are removed for commercial accounts, while GovCloud accounts are also transitioned with temporary retention of admin controls. This change standardizes the sending experience across environments and simplifies user onboarding ahead of full Classic retirement.

Available environments: Sandbox, Commercial, Government | Available tiers of service: Acrobat Sign Solutions | Configuration scope: Not configurable

Modern Create Template becomes default – Promote new authoring experience, expand rollout, maintain admin controls
The modern Create Template experience is now the default for all accounts, including those that share assets across multiple groups. This update expands the rollout of the new authoring interface, ensuring all users benefit from ongoing enhancements, while retaining admin controls to revert to the classic experience if needed.

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

Resolved Issues

4520028	Summary: The Group column on the Manage page displayed incorrect or inconsistent values when users belonged to multiple groups. Changing the user’s primary group caused agreements to show the wrong group, including the last selected primary group or multiple groups, instead of the group the agreement was originally sent from.
Issue	Description
4520028	Fix: Updated the Manage page logic to use the agreement’s sending group (agreement_group_id) instead of the user’s current primary group when rendering the Group column.
4532690	Summary: Users could not edit draft agreements created from custom workflows when both “Enable agreements to only be sent by using a workflow” and “Enable new Custom Workflow send experience” were enabled. The system incorrectly blocked access to the compose page when editing an existing draft, treating it as a new send action instead of a draft edit.
4532690	Fix: Updated the Compose page logic to detect draft editing scenarios and bypass the workflow restriction check, allowing users to edit existing draft agreements created from custom workflows.
4536764	Summary: Sending agreements through a custom workflow resulted in a server error due to a failure processing specific template PDFs. The error was caused by invalid or missing annotation appearance data in one or more source documents, which triggered a rendering exception during prefill. The issue was not consistently reproducible and could not be replicated outside the affected workflows.
4536764	Fix: Improved handling of rendering exceptions in the PDF processing layer.
4537197	Summary: When using the new Send in Bulk experience with manually entered recipient names, the second name field was removed during signing due to incorrect handling of required recipient name data across documents.
4537197	Fix: Updated document processing logic to correctly retain all recipient name fields when sending agreements in bulk.
4538172	Summary: Copying workflows that include recipient groups failed during Sandbox Sync with an “Error executing request” message due to invalid recipient group references. The workflow used environment-specific recipient group IDs, which are not portable across environments, causing validation to fail during sync.
4538172	Fix: Updated Sandbox Sync handling to correctly validate and process recipient group references during workflow copy operations, preventing failures when recipient groups exist in both environments.
4538251	Summary: In the new Send in Bulk experience, fullname and email signer info fields did not appear during signing or in the final document when the source file contained existing AcroForm fields. The issue was caused by incorrect handling of merge field data when combining signer info fields with pre-existing form fields, resulting in the fields not being rendered in child agreements
4538251	Fix: Updated merge and form field processing logic to correctly apply signer info fields in documents that include existing AcroForm fields.
4545485	Summary: Agreement creation intermittently failed when thumbnail generation encountered malformed PDF form fields. The failure was caused by source documents containing form fields without valid names and invalid nested field structures, which triggered processing errors during PDF generation.
4545485	Fix: Added validation and null checks during PDF processing to handle malformed form fields and prevent failures during thumbnail generation and agreement creation.
4545814	Summary: Fields are misaligned and text tags remain visible when processing landscape-oriented documents generated from XDP-based workflows. Incorrect coordinate calculations in landscape layouts cause improper field placement and prevent text tags from being properly parsed and removed.
4545814	Fix: Updated the field rendering logic to correctly calculate and place form fields in landscape-oriented documents, ensuring proper alignment and removal of text tags during processing.
4545978	Summary: Accented characters in signer names render incorrectly in the visible signature block when using local digital signing. The issue occurs because the default font embedded in the document lacks proper encoding for Western European characters, causing incorrect character substitution during signature appearance rendering.
4545978	Fix: Updated the embedded font configuration to include proper encoding for accented characters, ensuring correct rendering of signer names in the signature appearance
4547100	Summary: Cloned multiline text fields render inconsistently in the signed PDF. Multiline clone fields are missing the default appearance dictionary, which causes cloned fields to display fewer lines than the source field even when both fields use the same size and settings.
4547100	Fix: Added the default appearance dictionary to multiline cloned fields so cloned and source fields render consistently in signed documents.
4548305	Summary: The onboarding checklist shows “Request BAA for HIPAA readiness” as Pending even when HIPAA is enabled. The checklist evaluation logic incorrectly treats inherited HIPAA-related settings as incomplete, causing the task status to remain Pending despite the feature being enabled.
4548305	Fix: Updated checklist evaluation logic to correctly interpret HIPAA-related settings, including inherited values, so the onboarding task reflects the completed state when HIPAA is enabled.
4550731	Summary: A large gap appears between the signature underline and timestamp when signing documents using Fill & Sign. The issue occurs when the signature field is not wide enough to accommodate the rendered signature content, causing incorrect spacing in the signature appearance
4550731	Fix: Updated signature rendering to respect the defined field dimensions and adjust spacing appropriately, reducing the gap between the underline and timestamp.
4550906	Summary: The Change Password link points to an invalid URL for certain users, causing a browser error. The issue occurs when the application reads an outdated endpoint from configuration instead of the correct URL, leading to inconsistent behavior across environments.
4550906	Fix: Updated the configured password change endpoint to use the correct URL across affected environments.
4550992	Summary: Editing certain templates in the new experience redirects to the Create Template page instead of opening the template in edit mode. The issue occurs because the system determines the experience based on the template owner’s settings rather than the current user’s settings, causing incorrect routing when editing shared templates.
4550992	Fix: Updated template editing logic to use the current user’s experience settings instead of the template owner’s settings, ensuring templates open in the correct edit mode.
4551756	Summary: Approval request emails display unresolved template variables in the recipient field, causing incorrect email formatting. The issue occurs due to a failure in the email template rendering logic when generating entitlement conflict notifications.
4551756	Fix: Updated email template rendering to correctly resolve and populate recipient fields, ensuring valid email addresses are displayed in approval request emails.
4551768	Summary: Signers encounter an unhandled error when accessing or completing agreements due to a failure in form field appearance processing. A malformed appearance object causes a ClassCastException during document generation, leading to agreement rendering failure.
4551768	Fix: Updated form field processing logic to validate appearance object types before casting, preventing exceptions and ensuring agreements render correctly for signing.
4552272	Summary: Cancelled or abandoned agreements appear under Waiting for you on the Manage page. The issue occurs when a workflow restart event does not properly clean up participant status data, leaving stale visibility and indexing data that surfaces the agreement in incorrect views
4552272	Fix: Updated workflow restart handling and indexing logic to correctly clear prior participant status data and ensure agreements appear only in their correct state.
4553158	Summary: In RTL language environments on iOS, the signature panel does not respond correctly when drawing a signature. The panel scrolls instead of capturing input, requiring users to manually scroll to draw and apply the signature, which prevents normal signing behavior when the new recipient signature experience is enabled.
4553158	Fix: Updated signature panel interaction handling for RTL layouts on iOS to correctly capture drawing input without unintended scrolling, enabling normal signature creation and application.
4553583	Summary: Workflows allow email addresses with leading or trailing spaces, which causes agreements to fail silently when sending in the new experience. The system does not validate or normalize the input, and no error message is shown to indicate the issue.
4553583	Fix: Updated input handling to automatically trim whitespace from email addresses and prevent saving invalid values, and added handling for existing workflows so agreements can be sent successfully.
4553676	Summary: Hyperlinks display incorrectly in the Manage view, where the agreement title is appended to the URL, resulting in broken links. The issue occurs due to incorrect URL parsing when rendering hyperlinks in the Manage interface.
4553676	Fix: Updated hyperlink rendering to use proper URL parsing, ensuring links remain unchanged and function correctly across all views.
4555021	Summary: OTP validation fails with an “expired” error even when the code is entered immediately. The issue occurs due to a race condition in the authentication flow, where multiple submission events cause the OTP to be invalidated prematurely.
4555021	Fix: Updated OTP validation flow to handle duplicate or rapid submission events correctly, preventing premature expiration and allowing valid OTP entries to succeed.
4555028	Summary: Removing the next recipient to sign can fail with a system error and leave the agreement stuck in a pending revision state. The issue occurs when the recipient has an active reminder, which prevents the agreement update from completing successfully.
4555028	Fix: Updated recipient removal logic to handle cases where the next signer has active reminders, allowing the agreement update to complete without errors.
4555319	Summary: Web form creators see only Type and Draw signature options when previewing the form, while signers see all available options (Type, Draw, Image, Mobile). The issue occurs because the preview mode does not correctly apply enabled signature input settings when the creator is not acting as a signer.
4555319	Fix: Updated web form preview behavior to apply the full set of enabled signature input types, ensuring creators see the same signature options as signers.
4555345	Summary: Agreements with multiple Signer with Witness recipients fail to open in Preview from Draft with the error “ParticipantSetsInfo cannot be modified.” The issue occurs due to incorrect participant and witness ordering logic in custom workflows, which prevents the agreement from transitioning back to the authoring state
4555345	Fix: Updated participant and witness ordering logic in custom workflows to correctly calculate execution order, allowing agreements to return to the authoring state and proceed normally.
4555615	Summary: Webhook event payloads for delegated and replaced recipients do not include the privateMessage field. The issue occurs because the private message is not propagated to the recipient state used to generate webhook payloads, resulting in missing data for affected events.
4555615	Fix: Updated participant data handling to ensure private messages are included in webhook payloads for delegated and replaced recipients.
4555687	Summary: Agreements can be auto-cancelled and moved to a hidden state after signing due to a document visibility validation failure. When a participant is delegated or replaced, the document visibility mapping is not correctly transferred, causing a mismatch between assigned fields and visible documents, which can trigger an automatic cancellation.
4555687	Fix: Delegation and replacement logic now correctly clone document visibility mappings for new participants, preventing validation failures and unintended agreement cancellation.
4556516	Summary: Form fields can ignore configured font sizes and render inconsistently in generated agreements. The issue occurs in multiline fields when the document processing engine adjusts font size to prevent text clipping, overriding fixed font size settings.
4556516	Fix: Updated font rendering behavior so multiline fields respect fixed font size settings, aligning behavior with expected output and preventing unintended size adjustments.
4556967	Summary: Selected checkboxes can appear unselected in the finalized signed PDF for web forms. The issue occurs when certain hidden values (for example, “no”, “false”, “0”, “off”, “unchecked”) are used, which can cause checkbox states to be misinterpreted during document processing when Gibson is enabled.
4556967	Fix: Updated checkbox processing to correctly interpret hidden values and preserve selected states in the finalized document, ensuring consistency between signing and the signed PDF.
4557222	Summary: Link fields from field templates can disappear on the authoring page when used within a workflow. The issue occurs because link fields are not included in the agreement form field data returned during workflow-based authoring, resulting in missing fields.
4557222	Fix: Updated form field handling to include link fields from field templates during workflow processing, ensuring they are correctly merged and displayed on the authoring page.
4557272	Summary: The Date of Signing field can fail to appear in the finalized signed PDF. The issue occurs when text field rendering fails during document processing, preventing the date field from displaying in the output document.
4557272	Fix: Updated text field rendering to handle null or empty values correctly, ensuring the Date of Signing field is consistently displayed in signed documents.
4557282	Summary: Radio button fields in web forms can display an unexpected tooltip value (“object Object”) when created using the new template experience. The issue occurs due to incorrect handling of empty tooltip values, causing placeholder data to be rendered instead of being suppressed.
4557282	Fix: Updated tooltip handling logic to properly ignore empty values, preventing unintended placeholder text from appearing in web forms.
4557589	Summary: Prefilled checkbox fields can appear unchecked when the agreement is sent for signature. The issue occurs when duplicate or conflicting hidden values are defined for checkbox or radio inputs, which can cause incorrect interpretation of the selected state during document processing.
4557589	Fix: Updated field value handling to correctly process hidden values and preserve prefilled selections, ensuring checkbox states remain consistent when agreements are generated and sent.
4557672	Summary: The new request signature experience can display a generic error (“The request provided is invalid”) when sending an agreement, without identifying the specific field causing the failure. This can occur when recipient details (such as phone number format) fail validation, but the error is not surfaced clearly to the user.
4557672	Fix: Updated validation handling to provide specific, field-level error messages, helping users identify and correct invalid inputs before sending the agreement.
4557680	Summary: Checkbox or radio button mappings can fail in some agreements when combining multiple documents, resulting in expected values not being applied. The issue occurs when default values do not exactly match defined export values, which can cause fields to be treated as separate groups and break mapping behavior.
4557680	Fix: Updated field mapping logic to ignore mismatched default values and correctly associate fields across documents, improving consistency of checkbox and radio button behavior.
4557902	Summary: An extra gap can appear between the signature and the date and time stamp in Fill and Sign agreements. The issue occurs due to incorrect spacing calculation in well-formatted signatures, leading to inconsistent layout compared to other signing flows.
4557902	Fix: Updated signature layout calculation to correctly position the signature and timestamp, removing unintended spacing and ensuring consistent formatting.
4557947	Summary: Checkbox fields can appear unchecked in the finalized signed PDF when using library templates, even though the signer selected them. The issue can occur when checkbox fields are misconfigured or use certain hidden values, which leads to incorrect interpretation of the selected state during document processing.
4557947	Fix: Updated checkbox processing to correctly interpret hidden values and preserve selected states, ensuring checkbox selections are retained in the signed document.
4558295	Summary: Required radio button values can be missing in the finalized signed PDF. The issue can occur when field values contain special characters (for example, quotes or symbols) that are not properly processed, leading to the selected value not rendering in the document output.
4558295	Fix: Updated field value processing to correctly handle special characters, ensuring selected values are preserved and displayed in the signed PDF.
4558307	Summary: Form fields can ignore configured font sizes and render inconsistently in generated agreements. The issue can occur in multiline fields when the document processing engine adjusts font size to prevent text clipping, overriding fixed font size settings.
4558307	Fix: Updated font rendering behavior so multiline fields respect fixed font size settings, preventing unintended resizing and ensuring consistent output.
4558554	Summary: Signers can complete agreements without interacting with the Signature Block. The issue can occur in Gibson-enabled accounts when the Signature Block is not properly rendered or enforced during signing, allowing completion with only the Signature Field.
4558554	Fix: Updated signature rendering and validation logic to ensure Signature Blocks are correctly displayed and required before agreement completion.
4558725	Summary: Text tags can fail to render or convert into form fields during preview. The issue can occur when the uploaded PDF contains unsupported or invalid elements (for example, null annotations or existing fillable fields), which prevent text tag processing from completing successfully.
4558725	Fix: Updated text tag processing to handle PDFs with invalid or unsupported annotations more reliably, allowing fields to be generated as expected during preview.
4559285	Summary: Phone authentication can fail for certain regions when selecting a country code in the new request signature experience. The issue occurs when the UI displays an incomplete or incorrect country code (for example, “+1” instead of “+1246” for Barbados), which can cause validation errors when sending the agreement.
4559285	Fix: Updated country code handling to use the correct full dialing codes, ensuring phone numbers are validated and processed correctly in the new experience.
4560119	Summary: Text in form fields can appear misaligned or overlap in generated agreements. The issue can occur in multiline text fields when rendering differences are introduced by the document processing engine, leading to layout shifts compared to the authoring view.
4560119	Fix: Updated text rendering and layout handling for multiline fields to improve alignment and prevent overlapping, ensuring more consistent display between authoring and final documents
4562058	Summary: The recipient name can remain unchanged when selecting a different email from the address book on the Send page. The issue occurs because the name field does not refresh when a new contact is selected, causing a mismatch between the displayed name and selected email.
4562058	Fix: Updated recipient selection behavior so the name field always refreshes when a new contact is selected, ensuring the name and email remain synchronized.
4566339	Summary: Incorrect checkbox states can appear when processing static XFA PDFs with malformed field values. The issue can occur when unsupported or invalid XFA data (for example, string values in numeric fields) is handled inconsistently, particularly in Gibson-enabled environments where checkbox defaults can be misinterpreted.
4566339	Fix: Updated XFA handling in the document processing pipeline to normalize or ignore malformed values more consistently, preventing incorrect checkbox states and aligning behavior across environments.
4567278	Summary: Read-only text fields can fail to appear on the signing page when dynamic participants are enabled. The issue occurs due to field rendering inconsistencies during participant resolution, which can cause non-editable fields to be omitted from the signer view.
4567278	Fix: Updated field rendering logic for dynamic participants to ensure read-only fields are consistently included and displayed during signing.
4568023	Summary: Image and Mobile signature options can fail to appear in web forms during signing. The issue can occur due to inconsistent loading of signature options in the web form entry flow, where certain signing methods are not surfaced until the session is reloaded or accessed through an alternate path.
4568023	Fix: Updated web form signing initialization to consistently load all enabled signature options, ensuring Image and Mobile methods are available across all entry points.

June 16, 2026 (Minor release) v17.1.1

Adobe Acrobat Sign release v17.1.1

Sandbox deployment: May 12, 2025

Production deployment: June 16, 2026

GovCloud deployment: June 18, 2026

Improved Functionality

Recipient Filter in Reporting – Add recipient-based filtering to reports and data exports.
Add a Recipient filter to modern Reporting for Agreement and Transaction reports and Data Exports. Administrators can filter by recipient email to return all agreements that include the specified recipient, regardless of role or signing order. The filter supports autocomplete and multi-select behavior consistent with the existing Sender filter and applies to both visual reports and CSV exports.

Available environments: Sandbox, Commercial, Government | Available tiers of service: Acrobat Sign Solutions | Configuration scope: Enabled with Modern Reporting
Review the reporting overview >
Review the updated Create a Report document >
Review the updated documentation for Creating a Data Export >

Inline Document Editing During Authoring – Enable senders to edit document text directly within the authoring experience
Allows senders to edit document text directly within the authoring experience before sending an agreement for signature. An Edit Document option lets users modify text without downloading and re-uploading the file, while preserving existing fields and agreement configuration. This streamlines pre-send corrections and reduces disruption during agreement preparation.

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

Bio-Pharma (CFR) Support in Modern eSign – Adds signing reason capture and enforced sign-time reauthentication
Adobe Acrobat Sign completes Bio-Pharma support in the Modern eSign experience by adding signing reason capture and enforced reauthentication during signing. Organizations operating in regulated environments can require a signing reason, enforce reauthentication for each signature or at final click-to-sign, and maintain compliant audit reporting — all within the Modern interface.

Available environments: Sandbox, Commercial, Government | Available tiers of service: Acrobat Sign Solutions | Configuration scope: Support for Bio Pharma settings in Modern eSign is enabled by default.
Review the updated supported features list for Modern e-sign >

Experience Changes

REST API/Webhook Updates

Suppress agreement notifications via API – Add granular control over recipient messaging
Using the REST v6 POST /agreements API, control which notifications are sent when creating agreements by suppressing specific email types for participants, CCs, or the sender. This reduces unnecessary emails and supports cleaner, more controlled signing experiences in integrated workflows.

Available environments: Sandbox, Commercial, Government | Available tiers of service: Acrobat Sign Solutions | Configuration scope: REST v6 API

Release errata

There are no items that have slipped from this release as of this time.

Resolved Issues

Previous Releases

Get help faster and easier

New user?

Adobe Acrobat Sign Release Schedule and Prerelease Notes

Adobe Acrobat Sign release schedule and prerelease documentation

Sandbox availability

Releases

May 5, 2026 (Major release) v17.1

Adobe Acrobat Sign release v17.1

Sandbox deployment: April 7, 2026

Production deployment: May 5, 2026

GovCloud deployment: May 12, 2026

Improved Functionality

Experience Changes

REST API/Webhook Updates

Release errata - Elements added

Release errata - Elements removed

Resolved Issues

June 16, 2026 (Minor release) v17.1.1

Adobe Acrobat Sign release v17.1.1

Sandbox deployment: May 12, 2025

Production deployment: June 16, 2026

GovCloud deployment: June 18, 2026

Improved Functionality

Experience Changes

REST API/Webhook Updates

Release errata

Resolved Issues

Previous Releases

Get help faster and easier

Share this page

Ask the Community

Contact Us