Adobe Acrobat Sign Release Schedule and Prerelease Notes

Cari

Terakhir dikemas kini pada 7 Jul 2026

Adobe Acrobat Sign release schedule and prerelease documentation

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.

Nota

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.

Nota

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

Isyarat

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

July 21, 2026 (Minor release) v17.1.2

Adobe Acrobat Sign release v17.1.2

Sandbox deployment: June 16, 2026

Production deployment: July 21, 2026

GovCloud deployment: July 23, 2026

Improved Functionality

Preserve Existing Digital Signatures in Uploaded PDFs – Admins can enable Acrobat Sign to preserve existing digital signatures in uploaded PDF files, allowing pre-signed documents to move through supported agreement workflows without flattening the original signature. This helps organizations use documents that were digitally signed before upload while protecting the document from changes that would invalidate the preserved signature.

Available environments: Sandbox, Commercial, Government | Available tiers of service: Acrobat Sign Solutions | Configuration scope: Account and Group
Review the configuration for preserving digital signatures >
Review the process for sending a PDF with an existing digital signature >

Inline Document Editing During Authoring – Edit document text directly in the authoring experience
Senders can edit document text directly in the authoring environment without downloading and re-uploading the file. The Edit Document option preserves existing fields and agreement configuration, reducing disruption during pre-send updates. Editing is available only while the agreement is in a draft state and is not available after the agreement is sent.

In-line document editing is to be released on a rolling schedule, as referenced in the technical notification.

This feature is enabled by default for all users in supported accounts, allowing senders to edit documents that are sent through Request Signature. Account and group admins can disable document editing through the Send Settings.

In-line document editing is not available in Acrobat Sign for Government or for accounts using the legacy user management system.

Available environments: Commercial | Available tiers of service: Acrobat Sign Solutions VIP and VIPMP customer accounts | Configuration scope: Account and Group; Enabled by default
Enable or disable in-line document editing >
How to edit text during field authoring >

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.

Customer-managed encryption keys for agreement files – Eligible Acrobat Sign customers can configure an AWS KMS customer-managed key to protect supported agreement files at rest. After the feature is enabled for an account, supported agreement files are encrypted using the customer-managed key, giving organizations more control over key management while preserving supported Acrobat Sign agreement workflows.

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

Resolved Issues

Issue	Description
4487069	Summary: Undelivered notification on the Manage page could disappear while users scrolled through agreements because the agreement list reused row components and didn’t refresh the notification state for each agreement.
4487069	Fix: The Manage page now refreshes the undelivered notification state when agreement rows are reused, so the notification remains visible while users scroll.
4541319	Summary: Embedded hyperlinks in reusable template previews could become inactive because PDF processing removed the embedded link data during template conversion, while exposed URL links remained clickable.
4541319	Fix: PDF processing was updated to preserve embedded hyperlink data during reusable template conversion, so embedded and exposed URL links remain clickable in template preview.
4555107	Summary: Combined document API downloads could omit the audit report even when attachAuditReport=true was used because some requests were incorrectly handled as unauthenticated when API action ID generation failed.
4555107	Fix: The combined document API now preserves the requested audit report attachment when API action ID generation is unavailable, so downloads include the audit report when attachAuditReport=true is used.
4555473	Summary: Safari users could be returned to the login page after signing in because newer Safari privacy handling prevented Adobe Acrobat Sign session cookies from being retained correctly during the Adobe identity sign-in flow.
4555473	Fix: Session cookie compatibility handling was updated for newer Safari and macOS versions, so Acrobat Sign keeps users signed in after login.
4555620	Summary: Large file uploads could be rejected when sending from a group with a higher max upload size because transient document upload validation did not load the selected group’s upload-size setting.
4555620	Fix: Transient document uploads now pass the selected group ID so Acrobat Sign applies the group’s max upload size when validating uploaded files.
4560927	Summary: Completed agreement recipients could receive unexpected completion emails when the sender requested a new link from an expired agreement email because the URL renewal flow misclassified the sender confirmation email as a signer notification template.
4560927	Fix: The URL renewal flow now sends the requested access link only to the user who requested it and no longer sends completion emails to other agreement participants.
4561378	Summary: When users created a copy of an agreement and opened authoring, Acrobat Sign could send an incorrect deadline update email because the copied agreement’s automatically applied deadline was treated as a sender-updated expiration before the agreement was sent.
4561378	Fix: The copy workflow now blocks the initial deadline update email before the copied agreement is sent, while preserving deadline update notifications for later sender changes.
4562055	Summary: In the new sending experience, account-level custom workflows could revert the Send from group value to the sender’s primary group because the selected group wasn’t preserved when the workflow page refreshed and recreated the draft agreement.
4562055	Fix: The custom workflow send flow now preserves the selected group during page refresh and draft agreement creation, so users can send from a non-primary group in the new experience.
4562242	Summary: Prefill field values could disappear after an agreement was restarted by a later recipient because the restart workflow used the restarted document as the source instead of the prefilled document that retained the original field defaults.
4562242	Fix: The restart workflow now uses the prefilled document as the base for the restarted agreement, so original prefill values are preserved when the agreement is sent back for signing.
4562338	Summary: Swagger API authentication could stop on a blank redirect page and fail to generate a bearer token because the OAuth redirect page rejected valid Acrobat document-domain URLs during redirect validation.
4562338	Fix: Swagger OAuth redirect validation was updated to allow supported Acrobat document domains, so authentication returns users to Swagger and loads the generated bearer token.
4565965	Summary: Documents with multiple digital signatures could fail validation in strict PDF signature validators because Acrobat Sign temporarily wrote an internal signing workflow value into a signature field where the PDF specification requires a signature dictionary.
4565965	Fix: The PDF merge process now skips signature fields when applying form values, preventing internal workflow values from being written into signature fields and preserving valid multi-signature document structure.
4567496 / 4567841	Summary: Stamp signatures could render smaller than the configured size when signature reason settings were enabled because the signature reason layout logic incorrectly reserved space next to stamp fields.
4567496 / 4567841	Fix: Stamp rendering was updated so signature reason layout adjustments don’t resize stamp fields, preserving the configured stamp size.
4568666	Summary: Webhook notifications could be missed for some agreements with witness participants because participant lookup logic did not safely handle witness records during webhook payload generation.
4568666	Fix: Webhook payload generation now safely handles witness participants, so webhook notifications continue to generate and send for affected agreements.
4568798	Summary: Copied agreements could include recipients that had been removed through Modify Agreement because the copy workflow did not fully exclude deleted recipients when rebuilding the recipient list and routing groups.
4568798	Fix: The copy workflow now filters out recipients removed through Modify Agreement and rebuilds routing groups using only active recipients.
4569478	Summary: Checkbox selections could disappear in completed agreements when an interactive PDF contained an invisible checkbox field layered over a visible checkbox field, because the invisible field was still rendered during final PDF processing.
4569478	Fix: PDF processing now skips invisible checkbox fields when rendering the completed agreement, so visible checkbox selections remain displayed in the final signed document.
4569490	Summary: Some Adobe Acrobat Sign notification emails could be flagged as spam because the email preheader markup included hidden or low-contrast styling patterns that some mail filters treat as suspicious.
4569490	Fix: Notification email markup was updated to remove the hidden and low-contrast styling patterns, reducing false-positive spam detection while preserving normal email preview behavior.
4569491	Summary: The Assign Users to Group flow could fail with an unhandled error when user-status validation encountered an incomplete group membership record.
4569491	Fix: User-status validation now skips incomplete group membership records instead of stopping the assignment workflow, allowing Assign Users to Group to open successfully.
4569747	Summary: Agreements created through the REST API in authoring status could show all checkbox fields as selected because checkbox merge-field values were not correctly interpreted when loading the agreement for authoring.
4569747	Fix: Checkbox merge-field handling was updated so authoring correctly honors checked and unchecked values from the API payload, displaying only the intended checkbox selections.
4570171	Summary: Adobe Acrobat Sign could fail to process some otherwise valid PDFs when the document contained a malformed link destination, because document processing stopped instead of ignoring the broken link.
4570171	Fix: Document processing now validates link destinations before reading them and skips malformed links, so affected PDFs can be processed and sent successfully.
4571060	Summary: Conditional fields linked to dropdown selections could fail when the dropdown used export values that differed from the displayed option labels because Acrobat Sign compared the condition against the wrong dropdown value.
4571060	Fix: Dropdown condition handling was updated to map displayed option labels to their corresponding export values, so conditional fields appear and retain their values correctly when the signer selects the matching dropdown option.
4571362	Summary: Completion emails could fail to send when all SMS delivery attempts for an agreement had bounced because the exhausted SMS delivery event caused audit report generation to fail during completion processing.
4571362	Fix: Completion processing now handles exhausted SMS delivery events without interrupting audit report generation, so sender and signer completion emails are sent after the agreement is signed.
4571642	Summary: Signer names provided through the API could be missing from the agreement response and remain editable during signing when signer name editing was disabled, because the sender-provided name was not preserved for recipients without a profile name.
4571642	Fix: Recipient name handling now preserves sender-provided names when signer name editing is disabled, so the name is returned in the agreement response and appears prefilled and locked on the signing page.
4571797	Summary: Some failed or skipped bulk-signing agreements could not be previewed from Manage because the agreement preview used an intermediate portfolio document instead of reverting to the original agreement document.
4571797	Fix: Bulk-signing processing now reverts failed or skipped agreements to the previous document version, so the agreements can be opened and previewed from Manage.
4572223	Summary: Workflow-created agreements could be automatically canceled during document processing when thumbnail generation completed only partially, causing finalization to fail when the system tried to use a missing page thumbnail.
4572223	Fix: Document finalization was made more resilient so missing or incomplete thumbnail data is handled gracefully, preventing affected workflow agreements from being automatically canceled.
4572763	Summary: In-person signing agreements created through the API could fail to open when the host participant was missing the required authentication setting, and the API documentation did not clearly describe the required in-person signer and host configuration.
4572763	Fix: The API documentation was updated to describe the required IN_PERSON_SIGNER and HOST roles, matching participation set labels, and host authentication settings needed to create in-person signing agreements successfully through the API.
4575098	Summary: Checkbox fields populated through merge data could appear selected in Modern Authoring even when the provided value was "0" because Acrobat Sign interpreted both "0" and "1" string values as checked.
4575098	Fix: Checkbox merge-field handling was updated so Modern Authoring correctly treats "0" as unchecked and "1" as checked, matching Classic Authoring behavior.
4578199	Summary: Audit reports could fail to download for some agreements because an audit event was not handled correctly during audit report generation, causing Adobe Acrobat Sign to return a miscellaneous error.
4578199	Fix: Audit report generation now handles the affected audit event correctly, so audit reports can be generated and downloaded without the miscellaneous error.
4578567	Summary: Safari users in the Adobe Acrobat Sign Sandbox could be redirected back to the login page after signing in because the browser session was not retained correctly after authentication.
4578567	Fix: Session handling was updated so Acrobat Sign preserves the authenticated Safari session after login. Users may need to clear the existing browser session once after the release.