What's New
Get Started
- Quick start guide for administrators
- Quick start guide for users
- For Developers
- Video tutorial library
- FAQ
Administer
- Admin Console Overview
- User Management
- Add, edit, and review active users
- Create function-focused users
- Review users who haven't completed verification
- Check for users with provisioning errors
- Change Name/Email Address
- Edit a user's group membership
- Edit a user's group membership through the group interface
- Promote a user to an admin role
- User Identity Types and SSO
- Switch User Identity
- Authenticate Users with MS Azure
- Authenticate Users with Google Federation
- Product Profiles
- Login Experience
- Account/Group Settings
- Settings Overview
- Global Settings
- Account tier and ID
- New Recipient Experience
- Self Signing Workflows
- Send in Bulk
- Web Forms
- Custom Send Workflows
- Power Automate Workflows
- Library Documents
- Collect form data with agreements
- Limited Document Visibility
- Attach a PDF copy of the signed agreement
- Include a link in the email
- Include an image in the email
- Files attached to email will be named as
- Attach audit reports to documents
- Merge multiple documents into one
- Download individual documents
- Upload a signed document
- Delegation for users in my account
- Allow external recipients to delegate
- Authority to sign
- Authority to send
- Power to add Electronic Seals
- Set a default time zone
- Set a default date format
- Users in Multiple Groups (UMG)
- Group Administrator Permissions
- Replace recipient
- Audit Report
- Transaction Footer
- In Product Messaging and Guidance
- Accessible PDFs
- New authoring experience
- Healthcare customer
- Account Setup
- Add logo
- Customize company Hostname/URL
- Add company name
- Post agreement URL redirect
- Signature Preferences
- Well formatted signatures
- Allow recipients to sign by
- Signers can change their name
- Allow recipients to use their saved signature
- Custom Terms of Use and Consumer Disclosure
- Navigate recipients through form fields
- Restart agreement workflow
- Decline to sign
- Allow Stamps workflows
- Require signers to provide their Title or Company
- Allow signers to print and place a written signature
- Show messages when e-signing
- Require signers to use a mobile device to create their signature
- Request IP address from signers
- Exclude company name and title from participation stamps
- Apply Adaptive Signature Draw scaling
- Digital Signatures
- Electronic Seals
- Digital Identity
- Report Settings
- New report experience
- Classic report settings
- Security Settings
- Single Sign-on settings
- Remember-me settings
- Login password policy
- Login password strength
- Web session duration
- PDF encryption type
- API
- User and group info access
- Allowed IP Ranges
- Account Sharing
- Account sharing permissions
- Agreement sharing controls
- Signer identity verification
- Agreement signing password
- Document password strength
- Block signers by Geolocation
- Phone Authentication
- Knowledge-Based Authentication (KBA)
- Allow page extraction
- Document link expiration
- Upload a client certificate for webhooks/callbacks
- Timestamp
- Send Settings
- Show Send page after login
- Require recipient name when sending
- Lock name values for known users
- Allowed recipient roles
- Allow e-Witnesses
- Recipient groups
- CCs
- Required fields
- Attaching documents
- Field flattening
- Modify Agreements
- Agreement name
- Languages
- Private messages
- Allowed signature types
- Reminders
- Signed document password protection
- Send Agreement Notification through
- Signer identification options
- Content Protection
- Enable Notarize transactions
- Document Expiration
- Preview, position signatures, and add fields
- Signing order
- Liquid mode
- Custom workflow controls
- Upload options for the e-sign page
- Post-sign confirmation URL redirect
- Restrict access to shared agreemets
- Message Templates
- Bio-Pharma Settings
- Workflow Integration
- Notarization Settings
- Payments Integration
- Signer Messaging
- SAML Settings
- SAML Configuration
- Install Microsoft Active Directory Federation Service
- Install Okta
- Install OneLogin
- Install Oracle Identity Federation
- SAML Configuration
- Data Governance
- Time Stamp Settings
- External Archive
- Account Languages
- Email Settings
- Migrating from echosign.com to adobesign.com
- Configure Options for Recipients
- Guidance for regulatory requirements
- Accessibility
- HIPAA
- GDPR
- 21 CFR part 11 and EudraLex Annex 11
- Healthcare customers
- IVES support
- "Vaulting" agreements
- EU/UK considerations
- Download Agreements in Bulk
- Claim your domain
- Report Abuse links
- System Requirements and Limitations
Send, Sign, and Manage Agreements
- Recipient Options
- Cancel an email reminder
- Options on the e-signing page
- Overview of the e-sign page
- Open to read the agreement without fields
- Decline to sign an agreement
- Delegate signing authority
- Restart the agreement
- Download a PDF of the agreement
- View the agreement history
- View the agreement messages
- Convert from an electronic to a written signature
- Convert from a written to an electronic signature
- Navigate the form fields
- Clear the data from the form fields
- E-sign page magnification and navigation
- Change the language used in the agreement tools and information
- Review the Legal Notices
- Adjust Acrobat Sign Cookie Preferences
- Send Agreements
- Send (Compose) page
- Overview of landmarks and features
- Group selector
- Adding files and templates
- Agreement name
- Global Message
- Completion Deadline
- Reminders
- Password protect the PDF
- Signature type
- Locale for the recipient
- Recipient signature order/flow
- Recipient roles
- Recipient authentication
- Private message for the recipient
- Recipient agreement access
- CC'd parties
- Identity check
- Send an agreement only to yourself
- Send an agreement to others
- Written Signatures
- Recipient signing order
- Send in Bulk
- Send (Compose) page
- Authoring fields into documents
- In-app authoring environment
- Create forms with text tags
- Create forms using Acrobat (AcroForms)
- Fields
- Field types
- Common field types
- E-signature fields
- Initials field
- Recipient name field
- Recipient email field
- Date of signing field
- Text field
- Date field
- Number field
- Checkbox
- Radio button
- Drop-down menu
- Link overlay
- Payment field
- Attachments
- Participation stamp
- Transaction number
- Image
- Company
- Title
- Stamp
- Field content appearance
- Field validations
- Masked fields values
- Setting show/hide conditions
- Calculated fields
- Field types
- Authoring FAQ
- Sign Agreements
- Manage Agreements
- Manage page overview
- Delegate agreements
- Replace Recipients
- Limit Document Visibility
- Cancel an Agreement
- Create new reminders
- Review reminders
- Cancel a reminder
- Access Power Automate flows
- More Actions...
- How search works
- View an agreement
- Create a template from an agreement
- Hide/Unhide agreements from view
- Upload a signed agreement
- Modify a sent agreement's files and fields
- Edit a recipient's authentication method
- Add or modify an expiration date
- Add a Note to the agreement
- Share an individual agreement
- Unshare an agreement
- Download an individual agreement
- Download the individual files of an agreement
- Download the Audit Report of an agreement
- Download the field content of an agreement
- Audit Report
- Reporting and Data exports
- Overview
- Grant users access to reporting
- Report charts
- Data Exports
- Rename a report/export
- Duplicate a report/export
- Schedule a report/export
- Delete a report/export
- Check Transaction Usage
Advanced Agreement Capabilities and Workflows
- Webforms
- Reusable Templates (Library templates)
- Transfer ownership of web forms and library templates
- Power Automate Workflows
- Overview of the Power Automate integration and included entitlements
- Enable the Power Automate integration
- In-Context Actions on the Manage page
- Track Power Automate usage
- Create a new flow (Examples)
- Triggers used for flows
- Importing flows from outside Acrobat Sign
- Manage flows
- Edit flows
- Share flows
- Disable or Enable flows
- Delete flows
- Useful Templates
- Administrator only
- Agreement archival
- Webform agreement archival
- Save completed web form documents to SharePoint Library
- Save completed web form documents to OneDrive for Business
- Save completed documents to Google Drive
- Save completed web form documents to Box
- Agreement data extraction
- Agreement notifications
- Send custom email notifications with your agreement contents and signed agreement
- Get your Adobe Acrobat Sign notifications in a Teams Channel
- Get your Adobe Acrobat Sign notifications in Slack
- Get your Adobe Acrobat Sign notifications in Webex
- Agreement generation
- Generate document from Power App form and Word template, send for signature
- Generate agreement from Word template in OneDrive, and get signature
- Generate agreement for selected Excel row, send for review and signature
- Custom Send workflows
- Share users and agreements
Integrate with other products
- Acrobat Sign integrations overview
- Acrobat Sign for Salesforce
- Acrobat Sign for Microsoft
- Other Integrations
- Partner managed integrations
- How to obtain an integration key
Acrobat Sign Developer
- REST APIs
- Webhooks
- Sandbox
Support and Troubleshooting
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.
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.
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.
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.
This article contains prerelease information. Release dates, features, and other information are subject to change without notice.
Adobe Acrobat Sign Release 16.1
Sandbox deployment: June 24, 2025
Production deployment: July 22, 2025
GovCloud deployment: July 24, 2025
Improved Functionality
- Improved control over group-based sharing - Organizations using advanced account sharing can now optionally restrict the shared view of their agreements to only those agreements sent from the user's group. Agreements sent to a user from an external group will be filtered out to protect potentially private user communications that would be inappropriate to share generally. This filter only applies to the group-level shares (sharing a group to another group or user), and does not apply to user-based shared (sharing a user to a group or another user).
Available environments: Sandbox, Commercial, Government | Available tiers of service: Acrobat Sign Solutions | Configuration scope: Account or Group
Review the updated Account Sharing Permissions >
- Acrobat Sign for Government gets updated to the modern experience:
- Acrobat Sign for Government: Access to the modern Request Signature interface - GovernmentCloud administrators can now enable their account or groups to use the modern Request Signature interface.
- Acrobat Sign for Government: Mobile-first upgrade for recipients - Government users can now access the modern interface, designed to simplify signing on mobile devices through an easy-to-configure, form field-only interface.
- Acrobat Sign for Government: New Create Template interface available - Government users now have access to the modern Create Template interface, which streamlines the template design process and improves usability.
Available environments: Government | Available tiers of service: Acrobat Sign for Government | Configuration scope: Account or Group
- Updates for VIP-licensed customers:
- Streamlined admin setup from the Home Page - Acrobat Sign introduces a new Account management section to help account admins quickly access key configuration tools. Add users, organize groups, connect integrations, and migrate templates directly from the Home Page—no digging required.
- Add users to the Admin Console from Acrobat Sign – Admins can now add users directly from the Users page in Acrobat Sign, automatically updating the Adobe Admin Console.
- Admin Console Role assignment now available through Acrobat Sign - To streamline setup, Acrobat Sign now allows account admins to assign key Admin Console roles—Product and Support Admin—without leaving the product interface.
- Easier access to the suite of third-party integrations - A new Integrations page has been added to the admin menu, providing direct intuitive links to the setup files for the individual integrations.
- Easier HIPAA onboarding through in-product guidance - Organizations subject to HIPAA can now begin the enablement process within Acrobat Sign via a new self-service workflow. The system sends an automated request to Support and tracks progress based on the BAA signature and system configuration.
- Fast-track your template migration to Acrobat Sign with automated template conversion - The new template migration feature helps account admins quickly bring their templates into Acrobat Sign. Upload a template ZIP file, convert it automatically, and review results in the authoring environment—no technical expertise needed.
- Acrobat Sign Smart Assistant Chatbot - The new Smart Assistant gives you in-app answers to common questions like how to add users, check usage, or update settings. Ask your question in plain language and get step-by-step guidance, relevant HelpX articles, or links to support pages.
Available environments: Sandbox, Commercial | Available tiers of service: Acrobat Sign Solutions | Configuration scope: Not Configurable
- Use WhatsApp to send agreement links directly to a recipient's mobile device - The WhatsApp integration in Acrobat Sign has been expanded to include the option to send agreement notification and reminder links directly to a recipient's WhatsApp enabled device.
Available environments: Sandbox, Commercial | Available tiers of service: Acrobat Sign Solutions | Configuration scope: Account or Group
Review the updated documentation >
- Native PDF/A support for long-term document preservation - Acrobat Sign now supports validation and export of documents in PDF/A-2b format (ISO 19005), helping organizations meet stringent archiving standards and regulatory requirements. Documents retain their PDF/A conformity across the full agreement lifecycle—upload, signing, and storage.
Available environments: Sandbox, Commercial, Government | Available tiers of service: Acrobat Sign Solutions | Configuration scope: Account or Group
Review the new feature >
- Prevent Adobe Acrobat Sign from being embedded in third-party websites - Clickjacking Defense adds iframe protection to Acrobat Sign pages accessed through REST API v5+. Framing is only allowed when using auto login with a declared parent domain, helping prevent deceptive or unauthorized embedding.
Available environments: Sandbox, Commercial, Government | Available tiers of service: Acrobat Sign Solutions | Configuration scope: Account or Group
Review the clickjacking defense configuration documentation >
- New Trust Service Provider (TSP) - Acrobat Sign is expanding its list of supported Trust Service Providers (TSPs) to enhance the recipient's authentication options. The following new TSP is now available:
- eID Easy
This addition expands Acrobat Sign's compatibility with global standards, supporting seamless and secure digital signatures across multiple industries.
Available environments: Sandbox, Commercial | Available tiers of service: Acrobat Standard, Acrobat Pro, Acrobat Sign Solutions | Configuration scope: Account and Group
Experience Changes
- Improved digital signature experience - The process for applying a cloud-based digital signature has been refined to reduce the number of interactions the signer must complete when applying a digital signature.
Available environments: Sandbox, Commercial | Available tiers of service: Acrobat Standard, Acrobat Pro, Acrobat Sign Solutions | Configuration scope: The new process is enabled by default, not configurable.
- The character limit for labels in the Workflow Designer has been increased to 500 characters - When creating or editing a custom workflow in the Workflow Designer, the labels used to describe fields can now accept up to 500 characters (improved from 100 characters).
Available environments: Sandbox, Commercial, Government | Available tiers of service: Acrobat Sign Solutions | Configuration scope: Enabled by default; not configurable
Review the updated documentation >
- The New custom workflow experience control has moved to the Global Settings menu - The configurable option to Set the new custom workflow as the default experience has moved from the Send Settings page to the Global Settings page.
A new control has been added to expose "switch links" for users to switch between the new experience and the classic version.
Available environments: Sandbox, Commercial, Government | Available tiers of service: Acrobat Sign Solutions | Configuration scope: Account or Group
Integration Updates
- New Zapier Integration Now Available: You can now connect Acrobat Sign with thousands of applications using Zapier, enabling seamless automation of agreement workflows, with no coding or installation required.
Easily create “Zaps” to automate tasks such as sending emails or saving signed documents, helping you streamline and simplify repetitive processes.
Available environments: Sandbox, Commercial | Available tiers of service: Acrobat Sign Solutions | Configuration scope: Account
Review the overview documentation >
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.
- OAuth 2.0 capabilities have been extended to group-level administrators - Group-level admins now have the authority to use OAuth 2.0 tokens.
Available environments: Sandbox, Commercial, Government | Available tiers of service: Acrobat Sign Solutions | Configuration scope: Account or Group
- The webhookNotificationApplicableUsers parameter is to be removed from the Webhook payload - The Webhook 2.0 infrastructure has been rolled out to all customers, and with that completed, signer notifications have been deprecated. As a result, the webhookNotificationApplicableUsers parameter of the webhook payload no longer provides any useful data and will be removed from all webhook payloads.
Available environments: Sandbox, Commercial, Government | Available tiers of service: Acrobat Sign Solutions | Configuration scope: Not configurable
Release errata - Elements added
Below are items that have been added to this release since the initial publishing of the pre-release notes.
- Prevent Adobe Acrobat Sign from being embedded in third-party websites - Clickjacking Defense adds iframe protection to Acrobat Sign pages accessed through REST API v5+. Framing is only allowed when using auto login with a declared parent domain, helping prevent deceptive or unauthorized embedding.
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.
- The modern Request Signature environment has become the only experience when creating a new agreement. All existing Commercial accounts have been switched to the modern environment -
- Administrators no longer have the option to enable the classic experience through the admin menu.
- Customers using the Notarize integration will not be affected by this change.
Available environments: Sandbox, Commercial | Available tiers of service: Acrobat Sign Solutions | Configuration scope: Enabled by default; Not configurable
- Auto-tagging support for PDF accessibility compliance - Acrobat Sign now identifies untagged and scanned PDFs and applies accessibility tagging automatically, preserving the tag tree from sending through signing. This reduces manual burden and supports compliance with WCAG and Section 508 standards.
Available environments: Sandbox, Commercial, Government | Available tiers of service: Acrobat Standard, Acrobat Pro, Acrobat Sign Solutions | Configuration scope: Account or Group
- Custom Email Templates available for Acrobat Sign for Government - Customers on the GovCloud platform can now create custom email templates for their agreement notifications and reminders.
Available environments: Government | Available tiers of service: Acrobat Sign for Government | Configuration scope: Account or Group
Resolved Issues
Issue | Description |
---|---|
4501772 | Summary: For the modern request signature experience, the recipient message does not update when the language is changed in the Agreement settings. |
Fix: The code to accept the new language preference has been updated to address the change for messages when a new language is selected. | |
4503504 | Summary: In rare cases, retries during agreement creation can result in multiple copies of the same child agreement being generated using Send in Bulk |
Fix: Multiple updates to how child agreements are generated and listed internally with checks to ensure no duplicates can be created. | |
4511072 | Summary: Transaction Consumption Report emails are not received after using the "Send it now" option. |
Fix: The mailing system was updated to resolve a delivery issue. | |
4511224 | Summary: PDF files set to "Inherited" zoom before sending the default to "Fit to page" after signing, |
Fix: Annotation handling has been improved to ensure properties are correctly confirmed to the resulting PDF. | |
4512546 / 4522458 |
Summary: Shared workflows do not display field templates as expected for accounts sharing through Advanced Account Sharing. |
Fix: The GET /libraryDocuments/id/formFields request has been updated for the x-on-behalf-of-user header that is required for the advanced account sharing use case. | |
4515020 | Summary: The PUT /users/{id}/groups API call returns a 403 error when attempting to move a user who is not in the Default Group by a group level admin |
Fix: Aurthority has been extended to Group admins, who are now able to add users to their group, even if the assigned user is currently in another non-default group. | |
4516121 | Summary: When a group of radio buttons has individual tooltips, only the first tooltip displays for all options during signing. |
Fix: The radio button code strictly employed one tooltip for the array of buttons. It has been updated to allow individual representation. | |
4516129 | Summary: Agreements expire based on the UTC equivalent of the sender’s local time, not the intended local time. |
Fix: The logic that checks expiration time is no longer based on the browser time, instead allowing the core application to do the validation. | |
4518192 | Summary: Signers are intermittently unable to complete the signing process when using Adobe Sign Authentication with Okta SSO. |
Fix: Remove the crossShardLoginPage attribute from the session after successful login. | |
4521018 | Summary: When using the modern signing experience, dropdown fields configured with export values return the visible label instead of the export value in the /formData API response. |
Fix: Hidden (export) values are now being sent instead of the visible values. | |
4521111 | Summary: In the new authoring experience, users are unable to scroll through and view all available field templates from the Field Templates dropdown. |
Fix: The modern authoring experience has been updated to load more than just the first page of field templates. | |
4521311 | Summary: Due to a known 12-hour delay in the agreement expiration mechanism, reminders are being sent after the effective expiration time, resulting in failed signing attempts and user confusion. |
Fix: For recurring "Until Signed" reminders, the signing deadline is checked and will no longer send the reminder, but will leave it active so it can be picked up if the sender edits the signing deadline before it actually expires during the 12-hour grace period. | |
4522059 | Summary: When a signer uploads a file using an Attachment field and then completes a Digital Signature, the Download Document link results in a "Page Not Found" error. |
Fix: The checksum was eliminated from duplicate detection, as it's an optional property in the PDF spec. Acrobat Sign continues to use the file name and size to identify duplicates. | |
4522382 | Summary: Users are unable to complete transactions when using Click to Sign with authentication enabled. After signing in, the transaction does not complete and must be retried |
Fix: The crossShardLandingPage URL parameter was removed from the session post login. | |
4522384 / 4523594 / 4523900 |
Summary: When using the Bulk Send feature, no agreements are sent on the initial attempt, but a second attempt works as expected due to task queuing on the local shard. |
Fix: Task queuing has been refined to ensure tasks aren't delayed. | |
4522497 | Summary: The timestamp format on agreements changes from HH:MM:SS to HH:MM after the document is signed, resulting in loss of seconds in the final audit trail. |
Fix: Seconds have been added to the timePatern. | |
4522509 | Summary: CC recipients can not view the agreement context board when accessing LDV-enabled agreements via the email link. Instead, they receive a "Document not yet visible" error. |
Fix: Code amended to provide the needed access to view the context board. | |
4522547 | Summary: When using a template, the final PDF may display misaligned or missing form field data after signing due to page rotation being applied after every annotation. |
Fix: Page rotation has been corrected. | |
4522914 | Summary: When using the new Send in Bulk feature, customers may encounter an error during CSV upload if the values in the Agreement_Message or Private_Message columns exceed a certain character limit. |
Fix: The character limit was documented in customer-facing collateral. | |
4522945 | Summary: When trying to edit the reusable document as an account/group admin and trying to apply a field template NullPointerException occurs when checking origin participation |
Fix: Added method to find origin participation when editing library documents as account/group admin | |
4523043 | Summary: When editing a web form that includes a participant with the role set to Delegator, the Modify Web Form page fails to load. A console error is triggered, preventing any edits. |
Fix: Added a check which ensures that if the ROLE_MAP is undefined, the code does not read the className as undefined and throw an error. Instead, it returns undefined. | |
4523061 | Summary: Signed documents attached to emails retain their original file extensions in the filename, resulting in redundant naming |
Fix: No longer trim the filename substring if it starts with '.' and it is different from the extension. | |
4524122 | Summary: In the New Experience, attempting to start an agreement from a saved Workflow results in a system error due to an exceeded character limit. |
Fix: Label limits have been updated to allow 500 characters. | |
4524162 | Summary: Link validation prevents sending agreement on New Authoring Experience |
Fix: A parameter has been added to the new experience to check for the Errors hook, allowing for a more relaxed management of hyperlink validations. | |
4524356 | Summary: Users encounter a "Server Error: We encountered an error while processing your request" message when attempting to sign agreements due to the -1 border width not being interpreted correctly. |
Fix: Now interpreting -1 as a default 1pt border and only added a border if the border was greater than zero. | |
4524410 | Summary: In the New Send experience, when using a workflow and uploading a new file after deleting the preset agreement name, the Agreement Name field does not update automatically. |
Fix: Added a fix to remove the default value for the onBlur event and introduced logic to set the first uploaded document's name in the document name text field. | |
4524614 | Summary: The font used by text form fields in the PDF does not match the font chosen on the authoring page. The text field font is always SourceSansPro-Regular. |
Fix: Extended the ExternalFont.getFontReplacementMapping to include regular, bold, and italic fonts. | |
4525098 | Summary: The signature-requested email is not sent to signer2 when the sender is signer 2 and the sender replaces signer 1. |
Fix: Parallel recipient lists have been improved to manage the use case where an existing recipient is used to replace another recipient in the same recipient set. | |
4525377 | Summary: Electronic seals (eSeals) not working with the Modern Request Signature Experience |
Fix: Add a test case to verify electronic seal recipient in a non-UMG workflow, where the seal is restricted to group access. | |
4525491 | Summary: Agreement names containing non-Latin characters (e.g., Chinese, Japanese, Thai, Korean) appear as ?????? in the recipient's Manage tab and email notifications when sent via Send in Bulk. |
Fix: Documentation has been updated to indicate that the UTF-8 format is needed | |
4525653 | Summary: Agreements sent using the API with JPEG files are being automatically canceled due to a document processing error. The issue occurs after the files are uploaded successfully but before the agreement is sent. |
Fix: Added support for JPEG SOI app0-15 | |
4526153 | Summary: The scale of the stamp field behaves differently in the old and new authoring screens. |
Fix: The new authoring environment has been updated to scale the stamp field consistently with the classic version. | |
4527031 | Summary: When the "Allow senders to select signing order" is unchecked in New experience, the option "Recipients must Sign in order" remains visible |
Fix: The code regarding access to this control has been improved to properly suppress the option when the setting dictates. | |
4527284 | Summary: Agreements that include certain scanned or flattened PDF files are failing during authoring and are automatically cancelled with the error AUTO_AUTHOR_FAIL due to an internal library that is not managed. |
Fix: Implemented a method that catches any exception and logs it, but does not interrupt the generation of an agreement. | |
4527948 | Summary: When a calculated Acroform field is imported into Sign, the REST API returns a field containing { calculated: true, valueExpression: '' }, which causes the field to be displayed with a validation error. |
Fix: Fields identified in this use case are now updated to be manually entered, not calculated. | |
4528062 | Summary: Get /users API call failing for Salesforce users with very large user numbers |
Fix: A new version of the Salesforce integration improves the process for getting the list of users to be more efficient. | |
4528284 | Summary: Incorrect country code of the Cayman Islands for Phone Authentication under New Experience |
Fix: The country code has been updated. | |
4529259 / 4529319 |
Summary: Optional Signers' Names and 2FA Required Despite Workflow Configuration in New Custom Workflow Send Experience |
Fix: Provided a check for optional recipients so whenever no email ID is present, the auth verification (phone, password, kba) will not fail any validation. Similarly, the name will also not be mandatory for optional recipients unless the email ID field has some input. | |
4530084 | Summary: Some users are experiencing a blank screen when accessing Recipient Settings in the New Send Experience. The issue is caused by a missing translation for a specific country code label, and it affects all locales except en-US. |
Fix: The correct translations have been published and pinned to the appropriate functions. | |
4530537 | Summary: An NPE is produced when trying to convert a named destination into a location, preventing agreements from being sent. |
Fix: A new check is in place to determine if the destination is a named destination and skip it. |
The September 2025 release is a minor release containing updates, and fixes for customer-reported issues.
- Sandbox release: August 19, 2025
- Production release: September 16, 2025
- GovCloud release: September 18, 2025
The October 2025 release is a major release containing features, updates, and fixes for customer-reported issues.
- Sandbox release: September 15, 2025
- Production release: October 7, 2025
- GovCloud release: October 9, 2025