Adobe Acrobat Sign Release Notes - 2027

Last updated on Nov 16, 2026

Adobe Acrobat Sign release v18.0

Sandbox deployment
November 17, 2026

Production deployment
January 12, 2027

GovCloud deployment
January 19, 2027


Agreement preparation and sending

Sender email suggestions in recipient fields

What's changed

When adding recipients to an agreement, senders can now select their own email address from the autocomplete suggestions instead of entering it manually.

The updated experience displays the sender's email address directly, rather than using the "Myself" label from the classic experience. This change applies to both standard sending and custom workflows.

Environment

Commercial · Sandbox · Government 

Licensing

ETLA · VIP · VIPMP

Configuration

Core functionality; Enabled by default

Default value

Enabled

Admin action

None

Rollout

Available immediately after release


Formula Builder in modern authoring

What's new

Senders can now use the guided Formula Builder in the modern authoring experience to create calculated fields and custom formula-based validation rules. The builder provides a searchable list of fields, keywords, and functions, with syntax checking and error feedback to help senders create valid expressions without switching to Classic authoring.

The available functions match those supported in the Classic Formula Builder. Existing formula evaluation and the recipient signing experience remain unchanged.

Environment

Commercial · Sandbox

Licensing

ETLA · VIP · VIPMP

Configuration

Core functionality

Default value

Enabled

Admin action

None

Rollout

Available immediately after release


Inline Document Editing During Agreement Authoring

What's new

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 disabled by default for all users in supported accounts.  Account and group admins can enable 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.

Environment

Commercial · Sandbox 

Licensing

ETLA · VIP · VIPMP

Configuration

Account · Group

Default value

  • ETLA: Disabled
  • VIP: Enabled

Admin action

  • ETLA: Required to enable
  • VIP: Required to disable

Rollout

  • ETLA: Available immediately after release
  • VIP: Previously released in v17.2

New Review & Send experience

What's new

Senders can review agreements before sending them for signature. The new Review and Send step provides a read-only document preview and lets senders inspect fields assigned to individual recipients. Senders can return to document preparation to make corrections before sending.

  • Account and group administrators can configure the review step as Disabled, Optional, or Mandatory under Send Settings.
  • The preview does not simulate the complete signing experience. Conditional and calculated fields appear without evaluating signing-time behavior, and automatically added signature fields are not displayed.
  • The feature is not available for accounts that use Acrobat Sign's native user management system, in Acrobat Sign for Government, or when sending agreements through custom workflows or library templates.

Environment

Commercial · Sandbox

Licensing

ETLA · VIP · VIPMP

Configuration

Account · Group

Default value

  • ETLA: Optional
  • VIP: Mandatory

Admin action

  • Admins should evaluate the feature and explicitly configure it per their organization's requirements.

Rollout

Commercial availability begins January 12, 2027
Phased rollout schedule


Schedule Agreements to Send Later

What's new

Senders can prepare agreements in advance and schedule them to be sent automatically at a selected date and time, from 30 minutes to 30 days ahead. Scheduled agreements remain available under Drafts on the Manage page, where senders can edit, reschedule, or cancel them before delivery.

Scheduled Send is supported in the modern Request Signatures experience and through the REST API v6. It is not supported in classic Send, Send in Bulk, or Custom Workflows.

Scheduled Send is enabled by default, with no customer-facing administrator control to disable it. Administrators must contact Adobe Support to request account-level disablement. Disabling the feature does not prevent previously scheduled agreements from being sent.

Environment

Commercial · Sandbox · Government

Licensing

ETLA · VIP · VIPMP

Configuration

Contact Adobe Support

Default value

Enabled

Rollout

Available immediately after release


Automatic PDF accessibility tagging

What's new

Account and group administrators can enable automatic accessibility tagging for eligible untagged PDFs sent through Request Signature. The feature adds basic document structure, including headings and reading order, to improve navigation for recipients using assistive technologies. Automatic tagging supports agreements up to 25 pages and 10 MB.

Environment

Commercial · Sandbox · Government

Licensing

ETLA · VIP · VIPMP

Configuration

Account · Group

Default value

Disabled

Admin action

Must be explicitly enabled.

Rollout

Available immediately after release


Signing and recipient experience

Modern e-signing experience supports custom workflows

What's changed

Agreements created using custom workflows can now open in the modern e-signing experience, providing recipients with a more accessible and streamlined signing interface. Supported workflows include sequential, parallel, hybrid, and recipient-group routing.

  • Eligible agreements automatically use the modern experience when it is enabled for the account.
  • Agreements that use other features not yet supported in the modern experience continue to open in the classic signing experience.

Environment

Commercial · Sandbox · Government

Licensing

ETLA · VIP · VIPMP

Configuration

Core functionality

Default value

Enabled

Admin action

None

Rollout

Available immediately after release


Saved signatures in the modern e-signing experience

What's changed

Recipients using eligible modern e-signing workflows can now use a previously saved signature instead of drawing or uploading it again. When permitted by the sending account, eligible recipients can also save a newly drawn or uploaded signature for future agreements.

Available environments: Commercial, Sandbox, Government | Available tiers of service: Acrobat Sign Solutions | Configuration scope: Existing Signature Preferences configuration

Environment

Commercial · Sandbox · Government

Licensing

ETLA · VIP · VIPMP

Configuration

Core functionality

Default value

Existing Signature Preferences configuration

Admin action

None

Rollout

Available immediately after release


Cloud Signatures are supported in the modern recipient experience

What's new

The updated experience supports the Cloud Signature provider selection, authentication, certificate selection, signature appearance, and signing process while providing the accessibility and usability improvements of the modern signing experience. 

Digital signatures configured for Download and Sign with Acrobat continue to use the classic recipient experience. 

Available environments: Sandbox, Commercial | Available tiers of service: Acrobat Sign Solutions | Configuration scope: Enabled by default

Environment

Commercial · Sandbox

Licensing

ETLA · VIP · VIPMP

Configuration

Core functionality

Default value

Available

Admin action

None

Rollout

Available immediately after release


Sign multiple agreements with electronic signatures

What's new

Signers can now select multiple agreements from the Manage page, review them together, and apply their saved electronic signature to eligible agreements in one session. This reduces repetitive signing steps for users who regularly process large numbers of agreements.

Signers must review each agreement before signing. Agreements requiring additional authentication or manual field completion are not eligible for bulk electronic signing.

Environment

Commercial · Sandbox · Government

Licensing

ETLA · VIP · VIPMP

Configuration

Account-level only (by Adobe Support)

Default value

Enabled

Admin action

Contact Support to disable

Rollout

Available immediately after release


Completion notifications for delegated recipients

What's new

Recipients who delegate their participation in an agreement now receive the completed agreement notification even when another participant completes the delegated action. This makes completion notifications consistent across single-recipient and multi-recipient agreements.

Environment

Commercial · Sandbox · Government

Licensing

ETLA · VIP · VIPMP

Configuration

Core functionality

Default value

Enabled

Admin action

None

Rollout

Available immediately after release


Agreement management and reporting

Recipient Delivery Status in Data Exports

 

What's new

Reports users can now include recipient email delivery status in CSV data exports. The new Recipient Delivery Status field identifies delivered, bounced, and not-yet-initiated initial invitation emails, helping administrators identify delivery failures across agreements without reviewing each agreement individually.

  • The field is available through the existing column chooser in modern Reporting.
  • Delivery status data isn't available for recipient records created before the 18.0 deployment (Jan 17, 2027).

Environment

Commercial · Sandbox 

Licensing

ETLA · VIP · VIPMP

Configuration

 Core function; Enabled by default

Default value

Available

Admin action

None

Rollout

Available immediately after release


Workflows and automation

Modern custom Compose experience becomes the default

What's changed

All Commercial and Government accounts are automatically switched to the modern Workflow Designer's custom Compose experience when using custom workflows. 
Admin controls remain available for customers who need to temporarily fall back to the classic experience. Full removal of classic fallback controls is planned for a later release.

Environment

Commercial · Sandbox · Government

Licensing

ETLA · VIP · VIPMP

Configuration

Account · Group

Default value

Enabled

Admin action

  • Required to revert to the classic experience

Workflow-level Reminders

What's new

Workflow creators can now configure reminder frequency directly in the Workflow Designer, allowing agreements sent through a workflow to use a predefined reminder schedule. This reduces manual setup and helps ensure participants receive consistent follow-up. Senders can adjust reminders for individual agreements when using the custom Compose page.

Workflow-level reminders are not supported through the classic Workflow Designer. Administrators must enable Global Settings > New custom workflow experience to use this feature.

Environment

Commercial · Sandbox · Government

Licensing

ETLA · VIP · VIPMP

Configuration

Account and Group

Default value

  • Unchanged for existing accounts
  • Enabled for new accounts after Jan 12, 2027

Admin action

  • Enable New custom workflow experience to gain access.

Rollout

Available immediately after release


Security, identity, and compliance


Expanded EU Digital Identity Wallet Support 

What's new

Adobe Acrobat Sign expands its support of EU Digital Identity Wallets issued by European countries by adding compatibility with supported European qualified trust service providers (QTSP).
This enhancement supports broader interoperability for qualified electronic signatures in the European Union, allowing organizations to use compatible wallets through the existing cloud signature workflow, without changing the existing signer experience.

Available environments: Commercial, Sandbox | Available tiers of service: Acrobat Sign Solutions | Configuration scope: Provider-level enablement

Environment

Commercial · Sandbox 

Licensing

ETLA · VIP · VIPMP

Configuration

Provider-level enablement

Default value

Available for providers that enable it

Admin action

None

Rollout

Available immediately after release


Additional cloud signature providers

What's new

Adobe Acrobat Sign adds support for additional cloud signature providers, giving organizations and signers more options for applying certificate-based digital signatures through supported regional trust services. New providers in Release 18.0:

  • Evrotrust (Bulgaria / EU)

  • Rubrix (Brazil) - Gateway service for Brazilian Remote Signature Providers 

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

Learn more

Environment

Commercial · Sandbox 

Licensing

ETLA · VIP · VIPMP

Configuration

Account and Group

Default value

Available

Admin action

Must be explicitly enabled

Rollout

Available immediately after release


Policy-based digital signatures

What's new

Administrators can enable predefined digital signature policies at the account or group level to meet specific regulatory requirements. Senders can then apply an approved policy to individual recipients, limiting them to cloud signature providers and certificates that meet the selected policy criteria.

Note: Signature policies apply only to Cloud Signatures. They do not apply to the Download and Sign with Acrobat workflow.

Environment

Commercial · Sandbox

Licensing

ETLA · VIP · VIPMP

Configuration

Account and Group

Default value

Disabled by default

Admin action

  • Must be enabled 

Rollout

Available immediately after release


Configurable password complexity

What's new

Administrators can now define custom password requirements for agreements, including minimum length, required character types, and a minimum number of character types. This provides greater flexibility to align password protection with organizational security policies.

The new Custom option under Security Settings > Document Password Strength supports passwords from 4 to 32 characters and applies to signer authentication, signed agreement PDF protection, and Signer Identity Reports.

  • Existing password-strength presets remain available and unchanged.
  • User login passwords are unaffected.

Environment

Commercial · Sandbox 

Licensing

ETLA · VIP · VIPMP

Configuration

Account and Group

Default value

Available; Not selected

Admin action

Must be explicitly selected

Rollout

Available immediately after release


User migration between accounts with customer-managed encryption 

What's changed

Customer-managed encryption (BYOK) is now generally available. Acrobat Sign customers can use fully owned encryption keys hosted in AWS Key Management Service to encrypt agreement files at rest.

User migration among accounts now fully supports accounts using customer-managed encryption. When a user is moved between accounts and either account uses Customer-managed encryption, Acrobat Sign re-encrypts affected agreements as needed so the migrated user retains secure access. 

Environment

Commercial · Sandbox 

Licensing

ETLA · VIP · VIPMP

Configuration

Account only

Default value

Core functionality; Available but not exposed

Admin action

Contact Support to enable

Rollout

Available immediately after release


Retention policy email reminders

What's new

Administrators can enable automated email reminders that notify senders before completed agreements are permanently deleted under their organization's retention policy. Reminders are sent 14 and 7 days before deletion and include a link to view, print, or download the agreement, giving senders an opportunity to preserve important records.

  • For retention periods shorter than seven days, a single reminder is sent immediately.
  • Extremely short retention periods may not generate reminders.
  • Notifications do not delay or prevent agreement deletion.

Environment

Commercial · Sandbox · Government

Licensing

ETLA · VIP · VIPMP

Configuration

Account · Group

Default value

Disabled

Admin action

  • Must be explicitly enabled.

Rollout

Available immediately after release 


Integrations and connected services

Improved integration discovery

What's changed

Acrobat Sign now surfaces integration options at more useful points in the workflow. Eligible users see a Microsoft 365 recommendation on the post-send page during their first three sends, while account administrators receive a one-time integration email and see clearer integration messaging on the Home page.
The Microsoft 365 recommendation opens the Microsoft AppSource listing. The administrator email links directly to the Integrations Hub.

Available environments: Commercial, Sandbox, Government | Available tiers of service: Acrobat Sign Solutions | Configuration scope: Enabled by Default

Environment

Commercial · Sandbox · Government

Licensing

ETLA<100K · VIP · VIPMP

Configuration

Enabled by Default

Default value

Enabled by Default

Admin action

None

Rollout

Available immediately after release


Acrobat Sign MCP in Adobe connectors 

What's new

Acrobat Sign MCP integration with Microsoft Copilot 
Users can access Adobe Acrobat Sign capabilities through Microsoft Copilot to create draft agreements, check agreement status, send reminders, and access library templates using natural-language requests.
Users can install the integration from the Microsoft Copilot App Store. Sending agreements remains under user control; Copilot creates drafts that users complete and send through Acrobat Sign.

Available environments: Commercial | Available tiers of service: Acrobat Sign Solutions | Configuration scope: Integration

Environment

Commercial 

Licensing

ETLA · VIP · VIPMP

Configuration

Available

Default value

Enabled

Admin action

None

Rollout

Available immediately after release


Developer and API changes

Webhook TLS 1.3 support

What's new

Adobe Acrobat Sign webhooks support TLS 1.3 for HTTPS callback endpoints, allowing integrations to register webhooks and receive notifications when the receiving endpoint requires TLS 1.3.

Learn more

Environment

Commercial · Sandbox · Government

Licensing

ETLA · VIP · VIPMP

Configuration

  • None; Core functionality

Default value

  • Available

Admin action

  • None required

Rollout

  • Available immediately after release

reminderFrequency=NEVER API behavior changes

What's new

Senders can prepare agreements in advance and schedule them to be sent automatically at a selected date and time, from 30 minutes to 30 days ahead. Scheduled agreements remain available under Drafts on the Manage page, where senders can edit, reschedule, or cancel them before delivery.

Scheduled Send is supported in the modern Request Signatures experience and through the REST API v6. It is not supported in Classic Request Signature, Send in Bulk, or Custom Workflows.

Implementation

Scheduled Send is enabled by default, with no customer-facing administrator control to disable it. Administrators must contact Adobe Support to request account-level disablement. Disabling the feature does not prevent previously scheduled agreements from being sent.

Learn more

Environment

Commercial · Sandbox · Government

Licensing

ETLA · VIP · VIPMP

Configuration

Disable through Support

Default value

  • Enabled

Admin action

  • Contact Support to disable

Rollout

Available immediately after release


Technical notifications

New release notes format

What's changing

The Adobe Acrobat Sign 18.0 release notes feature a new format designed to help you quickly discover updates relevant to your workflows and understand their benefits.

New and updated features are organized into categories, with direct links to detailed descriptions. Each description explains what’s new or changing, how it benefits you, and where to find supporting documentation.

A dedicated information panel provides at-a-glance details about feature availability, licensing, configuration requirements, default settings, and rollout schedules.

Environment

Public documentation

Licensing

Public

Configuration

Public to view

Default value

  • Published

Admin action

  • None

Rollout

Available immediately after release



Resolved Issues

Issue number Resolved issue details

4536757

Summary: After sending an agreement from Salesforce, users could see a blank Home page when opening Acrobat Sign in the same browser session.
Fix: Updated the Home page to load correctly in Salesforce-initiated browser sessions and restore the standard Acrobat Sign interface when opened outside Salesforce.

4545653

Summary: On iOS, signers could be offered the Sign with Acrobat option when local signing was the only permitted digital-signature method, even though local signing isn't supported on mobile devices.
Fix: Updated the mobile signing experience to direct affected signers to continue the local-signing process on a desktop device.

4553811

Summary: Saved profile signatures and initials could be deleted when an agreement that used them was destroyed, even though the saved signature belonged to the user rather than the agreement.
Fix: Updated agreement cleanup so destroying an agreement preserves the user’s saved profile signatures and initials.

4573860

Summary: In certain custom workflows, signature fields assigned through text tags could be presented to the wrong recipients because field assignments were not preserved consistently between authoring and signing.
Fix: Updated custom-workflow field processing so authored recipient assignments persist correctly into the signing experience.

4576058,
4578623,
4579255

Summary: Some PDFs containing existing AcroForm fields could display duplicate form fields after upload because document repair incorrectly treated existing fields as orphaned.
Fix: Corrected PDF form-field processing so existing fields are recognized properly and are not duplicated during authoring or signing.

4576609

Summary: Repeatedly using Preview & Add Fields in a custom workflow with group-shared templates could fail with an invalid-template error or lose an added document when returning to the send page.
Fix: Updated shared-template access and document-state handling so eligible templates remain available and selected documents persist through the workflow.

4577224,
4586033

Summary: With Limited Document Visibility, internal document links could be handled incorrectly when the recipient did not have access to the destination page.
Fix: Updated internal-link handling so links to inaccessible pages are disabled appropriately and required inaccessible links do not prevent recipients from completing the agreement.

4579304

Summary: Updating agreements through the API could take an excessive amount of time when requests contained large dynamic-participant payloads.
Fix: Updated agreement-update processing to remove the performance bottleneck affecting large dynamic-participant requests.

4579560

Summary: Currency-formatted PDF fields could lose their currency symbol and number formatting in the modern signing experience and completed PDF.
Fix: Updated field processing to preserve currency formatting during signing and in the completed agreement.

4580193

Summary: Some Safari signers could successfully authenticate but be returned to the authentication prompt instead of continuing to the agreement because their authenticated session was not retained through the redirect flow.
Fix: Updated authentication-session handling so the successful sign-in state is carried consistently into the signing session.

4581589,
4582429

Summary: On iPhone and iPad browsers, signers could enter an authentication loop after successfully signing in because the authentication session was not consistently recognized by the signing experience.
Fix: Updated authentication-session handling for browser privacy controls so successful authentication carries through to the agreement.

4582851,
4589257

Summary: Modifying an in-progress agreement again shortly after a previous modification could fail because the second request reused an outdated document reference.
Fix: Updated the modify-agreement workflow to use the agreement’s current document state instead of a superseded document reference.

4583756

Summary: The POST /search/agreementAssetEvents API could omit recent completed-agreement events when callers paged through results using onlyShowLatestEvent, preventing integrations from reliably detecting status changes.
Fix: Corrected event-query and pagination processing so matching latest events are returned consistently across result pages.

4585898

Summary: When an agreement combined templates containing same-named radio groups with numeric option values, the completed PDF could show the selection on only one instance of the group.
Fix: Updated radio-group processing so a selected numeric option is retained consistently across all matching instances in the completed PDF.

4587315

Summary: A radio-button group assigned to Any Recipient could disappear for later recipients when an earlier recipient left it unselected because the PDF’s unselected value was treated as an actual selection.
Fix: Updated radio-button processing to treat the PDF’s unselected state as empty, keeping the field available to subsequent recipients.

4588396

Summary: Radio-button text tags sharing a field name could create separate fields instead of one radio-button group when one option included a default value.
Fix: Updated text-tag parsing so the default-value modifier does not change the radio-group identity while still applying the configured default selection.

4588621

Summary: Users moved between accounts could lose access to existing agreements when either account used customer-managed encryption keys (BYOK) because the agreements remained encrypted with the source account’s key.
Fix: Improved the migration process to re-encrypt affected agreements as needed so migrated users retain access to their existing agreements.

4589289,
4591561

Summary: AGREEMENT_ACTION_REQUESTED webhook notifications could be sent without ParticipantSetsInfo when participant details could not be retrieved, resulting in an incomplete webhook payload.
Fix: Updated webhook processing to retry the notification instead of sending an incomplete payload when participant-detail retrieval fails, so the required participant information is included after the request succeeds.

4589692

Summary: Some bounced-recipient emails could fail to generate the expected bounce event when an already-processed bounce occurred earlier in the same processing batch.
Fix: Updated bounce processing to skip an already-handled message without abandoning the remaining messages in the batch.

4589893,
4593255

Summary: Cross-shard user provisioning could time out and roll back when migration processing included an unusually large amount of related user data, leaving the user unprovisioned in the destination account.
Fix: Updated cross-shard migration processing to prevent large volumes of related data from causing the provisioning operation to time out and roll back.

4590142

Summary: When Group administrators can edit user permissions was disabled, a group administrator could still grant Group Admin access while adding a new group membership because the restriction was not applied to new memberships.
Fix: Updated new-group membership handling so the Group Admin control follows the account-level permission restriction consistently.

4590210

Summary: When an agreement was delegated back to a signer who had already participated in the agreement, form field values entered by that signer could be missing from reports and downloaded form-field data.
Fix: Updated delegation processing so the participation containing the signer’s form data is correctly marked as signed and included in reporting and data exports.

4590491

Summary: The help text for well-formatted signatures and initials could imply that initials receive the same date formatting as signatures, although initials are not timestamped.
Fix: Updated the product text to distinguish the formatting applied to signatures from the formatting applied to initials.

4592066

Summary: GET /users/{userId} could omit primaryGroupId even though the field is defined in the API response schema.
Fix: Updated user retrieval so the user’s primary group ID is populated and returned in the API response.

4592185

Summary: Admins could be unable to edit certain web forms built from templates containing matching checkbox or radio fields because repeated field-option data caused the update process to fail or time out.
Fix: Corrected field-option processing so affected web forms can be edited and updated normally.

4592401

Summary: Palau (+680) could be absent from Phone Authentication country selectors even after the country code was enabled for the account.
Fix: Updated the relevant phone-authentication country mappings so Palau (+680) is available consistently in supported recipient and delegation flows.

4592677

Summary: Text tags on a PDF page could fail to convert into Acrobat Sign fields when document text extraction encountered a character without a usable Unicode mapping.
Fix: Updated PDF text extraction to safely handle unextractable characters so processing continues and valid text tags are converted.

4593392

Summary: When an authenticated web form signer used Sign on Mobile, the agreement could complete while the captured signature was missing from the final PDF.
Fix: Updated the web form signing path to process mobile-captured signature data before generating the completed PDF.

4594180

Summary: Dutch agreement emails could use wording that described the signing deadline as an expected date rather than a required due date.
Fix: Corrected the Dutch email localization so the signing deadline is described accurately.

4594244

Summary: Hosts of API-created in-person signing agreements could receive an error when opening the signing link if no explicit recipient authentication method had been provided.
Fix: Updated authentication handling so inherited authentication configuration is resolved correctly rather than treated as an unsupported authentication method.

4594582

Summary: A Date of Signing field could appear during signing but be missing from the completed PDF for certain document structures.
Fix: Updated completed-PDF processing so Date of Signing fields remain present in the signed document.

4594805

Summary: When the API throttled a client for polling too frequently, the response could incorrectly describe the condition as high system load even though the error code identified excessive polling.
Fix: Updated the throttling response so the header and message identify the actual too-frequent-polling condition.

4594862

Summary: Applying an existing field template to another template could change radio-button option values when the options were placed on different pages, breaking conditional logic that depended on those values.
Fix: Updated field-template application so radio-button option values are preserved across pages.

4595222

Summary: The Learn More link in the Proof/Notary administration settings used an outdated HelpX destination.
Fix: Updated the in-product link to the current Proof/Notary settings documentation.

4595395

Summary: Account administrators could receive another BAA/HIPAA confirmation email after an unrelated account-setting change even though the HIPAA setting had already been enabled.
Fix: Updated notification handling so the confirmation email is sent only when the relevant HIPAA setting is actually enabled by the current change.

4595882

Summary: Canceled agreements could remain listed under Waiting for You on the Manage page and be selected for Bulk Sign, causing the Bulk Sign job to fail.
Fix: Corrected agreement-status handling so canceled agreements no longer appear as agreements awaiting the user’s action and are not included in affected Bulk Sign selections.

4596142

Summary: Replacing a recipient could incorrectly fail with an agreement-not-delegatable error even when the sender’s configuration allowed recipient replacement because validation also considered the original recipient’s delegation permissions
Fix: Updated recipient-replacement validation to use the sender’s applicable settings when determining whether a recipient can be replaced.

4598008

Summary: WhatsApp delivery consumption could fail to be recorded when the delivery method was changed to WhatsApp while editing an agreement before sending, causing usage counts in settings and reports to be inaccurate.
Fix: Updated agreement processing to record WhatsApp delivery consumption correctly when the delivery method is changed before sending.

4599010

Summary: On mobile devices, an image field displayed by conditional logic could appear available but not respond when the signer selected it, preventing the signer from uploading an image.
Fix: Updated conditional-field handling to refresh the image-upload control when the field becomes visible so it remains interactive on mobile devices.