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
- Adding users
- Create function-focused users
- 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
- 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
- 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
- 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
- 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
- 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
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
- Authoring fields into documents
- In-app authoring environment
- Create forms with text tags
- Create forms using Acrobat (AcroForms)
- Fields
- 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
Support and Troubleshooting
Adobe Acrobat Sign release schedule and prerelease documentation
Adobe Acrobat Sign plans to deliver at least three releases each year, categorized as "major" or "minor" releases. Additional minor releases may be introduced to resolve customer-facing or system-processing issues as needed.
- Major releases contain large-scale updates, impactful new features, and a larger volume of minor updates and experience changes.
- Minor releases are added to the schedule as needed and when a launch date is established. Minor releases generally include smaller features and experience adjustments. Typically, there is one minor release between the major releases.
In the spirit of continuous improvement, Acrobat Sign will be releasing features not only in our major releases but also in minor releases (usually one minor release between each major release). To avoid disruption, we will continue to have these features behind enablement flags, meaning an account or group admin must explicitly turn them ON (check a checkbox).
Customers in the Health and Life Sciences field that require specific compliances should note that Acrobat Sign coordinates with a third-party vendor to provide a validation package for every release containing features to minimize your risk factor.
Documentation
Documentation for release notifications and new/updated content is typically published as follows:
- 6-8 weeks before the production release (typically four weeks before the Sandbox launch), a summary of the expected features and updates is published on this prerelease page.
- If features are added or removed from the release after this point, they are noted in the Errata section at the bottom of the page.
- Resolved issues are not published at this time.
- If features are added or removed from the release after this point, they are noted in the Errata section at the bottom of the page.
- 2-4 weeks before the production release (typically in alignment with the Sandbox launch), this prerelease page is updated with links to complete documentation of all new features and updated content.
- Links to the prerelease support documentation are provided on this page as needed. Prerelease documentation is in US English only.
- The first draft of the Resolved issues section is added. Resolved issues will likely change and be updated throughout the next four weeks.
- Links to the prerelease support documentation are provided on this page as needed. Prerelease documentation is in US English only.
- Launch day, the official release notes are updated to reflect the newly published features and updates with links to the production support documentation. This prerelease page is updated to remove the launched content and showcase the next release.
- The documentation is published after the release is complete, and functionality is verified in the live system. This takes a variable amount of time, depending on the amount and complexity of the new content. The official publication should not be expected before 7pm Pacific time and may be significantly later.
- The complete list of Resolved issues is updated in the US English version of the release notes. Localized versions may have out-of-sync data due to localization.
- Government Cloud updates typically happen one or more weeks after the production release. Due to the nature of the government environment, some features may need additional evaluation before enabling them.
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.
- The Sandbox is expected to have 99.9% availability and uses the same status page and outage procedures as the regular production environment.
- The Sandbox leverages the regular production SLA and support process to facilitate reporting issues.
This article contains prerelease information. Release dates, features, and other information are subject to change without notice.
Sandbox deployment: August 20, 2024
Production deployment: September 17, 2024
GovCloud deployment: October 8, 2024
Improved Functionality
- E-Witness an agreement - A new role has been added: Sign with Witness. Witnesses are identified by the signers at the time they open the agreement, before their signature is accepted.
Available environments: Sandbox, Commercial, Government | Available tiers of service: Acrobat Sign Solutions | Configuration scope: Group, Account
- New Recipient experience when interacting with an agreement - The recipient's signing environment has been updated to provide a better experience for all recipients.
Available environments: Sandbox, Commercial, Government | Available tiers of service: Acrobat Standard, Acrobat Pro, Acrobat Sign Solutions | Configuration scope: Account or Group
- Improvements to Identity Check - The recently added Identity Check policy has been updated to provide:
- API support for Identity Check configuration in /agreement endpoints.
- Name matching for Government ID and Cloud Signatures, with exact name matching only.
- Email matching for Cloud Signatures (to include Alternative Name matching).
Available environments: Sandbox, Commercial | Available tiers of service: Acrobat Sign Solutions | Configuration scope: Group, Account
- Improvements to the Signer Identity Report—The Signer Identity Report now includes more granular information to improve the understanding of the identifying document, such as differentiating a regular (full) driver's license from a provisional license.
Available environments: Sandbox, Commercial, Government | Available tiers of service: Acrobat Sign Solutions | Configuration scope: Group, Account
- Updated Audit Trail report—Accounts can update their Audit trail to include more information about the documents that the agreement recipients see and how they interact with them.
Available environments: Sandbox, Commercial, Government | Available tiers of service: Acrobat Sign Solutions | Configuration scope: Group, Account
- New filter and search functionality for the Reports environment - A new filter has been added to the reporting functionality, allowing Groups to be filtered through a multi-select interface.
Additionally, the search field capabilities have been improved to search for matches anywhere within a word string. Matches can be found at any word's beginning, middle, or end.
Available environments: Sandbox, Commercial | Available tiers of service: Acrobat Standard, Acrobat Pro, and Acrobat Sign Solutions | Configuration scope: Enabled as part of the base feature
- Custom email templates and Report Abuse links are now supported for Linkless notifications - The option to send Acrobat Sign agreement notifications without active links is now supported in Custom Email Templates. Additionally, the Report Abuse URLs are included in the notification.
Available environments: Sandbox, Commercial | Available tiers of service: Acrobat Sign Solutions | Configuration scope: Group, Account
- Clear indication of undelivered emails and SMS contacts - A new icon on the Manage page clearly indicates if there has been an issue when delivering a notification to a recipient, allowing the sender to understand and correct the bad email or phone number to get the agreement back on track.
Available environments: Sandbox, Commercial, Government | Available tiers of service: Acrobat Sign Solutions | Configuration scope: Not configurable
- Senders can view form field data as recipients fill them in—The sender of an agreement can view the field content of an agreement's fields as the recipient fills out the form. The view of the fields persists until the recipient completes their action.
Available environments: Sandbox, Commercial | Available tiers of service: Acrobat Sign Solutions | Configuration scope: Group, Account
- Allow recipients to download the individual files of an agreement - Recipients can be enabled to download their agreements in the form of the individual files that originally created the agreement.
Available environments: Sandbox, Commercial, Gov Cloud | Available tiers of service: Acrobat Sign Solutions | Configuration scope: Group, Account
- Improvements to the Request Signature page:
- Support for sending through Advanced Account Sharing - The Request Signature process now supports Advanced Account Sharing.
- SMS or email delivery - The option to send an agreement URL directly to a phone number has been added to the Request Signature experience.
- Calculated fields - The new cookieless authoring environment now supports calculated fields.
- The Authentication Method and Private Message configuration has been moved to their own interface - The Private Message and Authentication Method interface has been moved from being in-line with the recipient record and into a new subsection called Recipient Settings. Each recipient has their own explicitly configurable Recipient Settings section.
- Support for sending through Advanced Account Sharing - The Request Signature process now supports Advanced Account Sharing.
Available environments: Sandbox, Commercial | Available tiers of service: Acrobat Sign Solutions | Configuration scope: Enabled as part of the existing base feature
- Updates to the Send in Bulk experience:
- Send in Bulk has been updated to accommodate CC'd information for the CSV upload method of agreement creation - The CSV upload method for generating Send in Bulk child agreements now supports adding CC'd parties.
- Send in Bulk has been updated to include the Email via One-time Password authentication option through the CSV upload method. The One-time Password authentication method is available when creating Send in Bulk transactions using the CSV method.
- Send in Bulk is included in the Send permission for Advanced Account Sharing - Sharing accounts under advanced sharing rules, with Send authorization enabled now includes access to create and send agreements using the Send in Bulk feature as the sharing userID.
- Send in Bulk report for errors created when generating the child agreements - When errors are generated through the Send in Bulk process using a CSV upload as the source of recipients, a downloadable file is generated so the sender can correct inaccurate input.
Available environments: Sandbox, Commercial | Available tiers of service: Acrobat Pro, Acrobat Sign Solutions | Configuration scope: Enabled as part of the existing base feature
- The process of saving a web form has more granular controls - The control for validating a web form's first signer has been separated from the control to enable the recipient's access to save a web form.
Available environments: Sandbox, Commercial, Government | Available tiers of service: Acrobat Standard, Acrobat Pro, Acrobat Sign Solutions | Configuration scope: Enabled as part of the existing base feature
- Web forms support phone authentication for signer-added participants - Web forms that allow signer-defined participants can now include phone-based authentication for the added recipients.
Available environments: Sandbox, Commercial, Government | Available tiers of service: Acrobat Standard, Acrobat Pro, Acrobat Sign Solutions | Configuration scope: Enabled as part of the existing base feature
Experience Changes
- New support experience for accounts using the classic user interface - Long-time customers who haven't migrated their user management to the Adobe Admin Console have a new experience for contacting support and entering tickets.
Available environments: Commercial | Available tiers of service: Enterprise | Configuration scope: Enabled by default
- The new Request Signature environment is now the default experience for all accounts - The new and improved Request Signature environment has been promoted to the default experience with the September 2024 release. This is the first step in ending access to the classic environment, which is planned to be removed entirely from the user experience by March 2025.
- Administrators continue to have the option to reset the default environment to the classic experience through their admin menu.
- Links remain available for users to switch between the new and classic environments. Accounts that have previously disabled switch links will need to do so again.
- Administrators continue to have the option to reset the default environment to the classic experience through their admin menu.
Available environments: Sandbox, Commercial | Available tiers of service: Individual, Team, Enterprise | Configuration scope: Account, Group
- The Create Template experience for integrations that embed the user experience now employs the new Authoring functionality - Prior to this release, the Create Template experience in the embedded experience used the classic Authoring environment. As of this release, the newest Authoring environment is being used.
Available environments: Sandbox, Commercial | Available tiers of service: Enterprise | Configuration scope: API Application.
- Respect date format preferences in well-formatted signatures - The customer-defined preferred date format is now applied to the well-formatted signatures and signature blocks.
Available environments: Sandbox, Commercial, Government | Available tiers of service: Individual, Team, Enterprise | Configuration scope: Enabled by default
- Viewing/modifying an agreement set to be e-vaulted now opens on the Request Signature page - Customers using the eOriginal integration can now open agreements flagged to be vaulted in the Request Signature environment instead of the classic Send page environment.
Available environments: Sandbox, Commercial | Available tiers of service: Individual, Team, Enterprise | Configuration scope: Account, Group
- Send in Bulk has updated the interface to display the Message field when the CSV upload option is selected - The Message section is no longer hidden when a user selects the option to upload a CSV file to generate the child agreements through the Send in Bulk process.
Available environments: Sandbox, Commercial | Available tiers of service: Individual, Team, Enterprise | Configuration scope: Account, Group
- Improved expereience in the Request Signature environment for when a sender is the first signer or when prefill fields exist - When an agreement is sent, and the sender is the first signer, or prefill fields are present on the agreement, the signing environment opens immediately, allowing the sender to fill fields and sign without having to first access their email or Manage page.
Available environments: Sandbox, Commercial | Available tiers of service: Individual, Team, Enterprise | Configuration scope: Enabled by default
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.
- Webhook notification rate limiting - Concurrency-based rate limiting is being applied to webhook and callback notifications.
Feature Maximum Concurrent
RequestsDescription Webhook creation
10 At most 10 concurrent webhook creation requests are allowed per Account.
Requests exceeding this limit will result in a 429 TOO_MANY_REQUESTS response code.Webhook/callback notification
30 At most 30 concurrent webhook and callback notifications are allowed per Account.
Notifications exceeding this limit will retry according to exponential backoff until they are delivered.
- The agreementID is now available in GET /agreement API responses for web form agreements that are not yet verified - Web forms that are not yet signed or saved by the first signer now have an agreementID value that the API can retrieve through GET /agreement API calls.
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.
- Required recipient names support for custom send workflows - Organizations that use custom send workflows can now include required recipient names in the configuration of the workflow.
Available environments: Sandbox, Commercial | Available tiers of service: Acrobat Sign Solutions | Configuration scope: Group, Account
- Recipient Agreement Access setting to control if an agreement is displayed on a recipient's Manage page - A new option is available to control if an agreement is associated can be associated with an active userID, or if the recipient should be treated as an unknown recipient. This has the effect of not populating the agreement in the recipient's Manage page, making it safe from unintentional sharing through User or Group sharing.
Available environments: Sandbox, Commercial | Available tiers of service: Acrobat Sign Solutions | Configuration scope: Group, Account
- Updated User Sync Tool - The Acrobat Sign-specific version of the User Sync Tool has been updated to support Users in Multiple Groups.
Available environments: Sandbox, Commercial | Available tiers of service: Acrobat Sign Solutions | Configuration scope: Not Applicable
Resolved Issues
Issue | Description |
---|---|
4323027 |
Summary: Search in New Experience does not work correctly for charnum values or with underscores. |
Fix: The database was reindexed after the server migration, resolving the issue | |
4446870 |
Summary: Users are getting a blank screen when trying to login to Acrobat Sign intermittently |
Fix: Updated the JSP being served, resolving the eissue. | |
4456574 |
Summary: In the new experience if you author and send without adding a signature box, it doesn't try to add it to the last page due to a thumbnail not being created on the latest version. |
Fix: The classic behavior has been replicated with all new code to provide a consistent experience. | |
4459445 |
Summary: The document name field in the new experience for recent templates is too small to see the name |
Fix: The size of the field has been improved. | |
4465815 |
Summary: The "Well formatted" chrome is converted to English when the signature is processed. |
Fix: The locale of the user settings is now referenced when the signature appearance is created. | |
4467671 |
Summary: Emails sent in the Polish locale have unique formatting |
Fix: The localized template was reconfigured to be consistent with other locales | |
4468713 |
Summary: The agreement email body consists of incorrect and inaccurate messages/content. |
Fix: Multiple systems and templates updated to align the email templates | |
4468718 |
Summary: Typo in the Signature requested emails in Polish Language |
Fix: The typo has been corrected. | |
4469262 |
Summary: Blank White screen while selecting a template while using bulk send New Experience |
Fix: The Bulk Send processor has updated libraries, solving the issue. | |
4470664 |
Summary: Reminder events don't propagate automatically like other events in Salesforce |
Fix: The REMINDER_SENT event is now being pushed from the core application using the v6 REST methods | |
4471103 |
Summary: User email address with apostrophe twice is failing with the error message in workflow. |
Fix: The code managing the email formatting has been improved to accommodate this use case. | |
4471385 |
Summary: Content Protection feature not working as expected through re-authorization |
Fix: Improved code to ensure to fetch the correct Account details of the internal user are referenced when a Hostname is defined in the Account |
|
4471478 |
Summary: "AGREEMENT_WORKFLOW_COMPLETED" notification incorrectly shows SIGNER status as "WAITING_FOR_MY_SIGNATURE" |
Fix: Corrected the index that was being assigned to the status. | |
4472497 |
Summary: Documents with unparsable metadata are not properly handled |
Fix: XMP parse exceptions and now ignore |
|
4472908 |
Summary: The Password option cannot be suppressed in the new sending experience |
Fix: The component for adding the authentication options has been updated to properly reflect the authentication methods allowed for the group | |
4473086 |
Summary: Participation stamp and Transaction ID fields are not present on Notarized agreements due to being placed post signature on an earlier version of the agreement |
Fix: The processing has been improved to properly place the post-signing fields onto the agreement after notarization | |
4473112/ 4473556 |
Summary: Error thrown in new Send in BUlk if the sender is the first signer due to a check for this use case |
Fix: The check for the use case is now being ignored. |
|
4473248 |
Summary: Agreements may intermittently cancel due to streams with /Name attributes that are strings |
Fix: Now only /Type attributes that are Names will be checked | |
4473286 |
Summary: Delegation verbiage can be seen in the 'Signature Requested' email notification even after disabling delegation in account settings |
Fix: Added a condition which checks internal and external delegation setting values of Originator and display or hide the delegation link in email. |
|
4474071 |
Summary: Transfering ownership of a template is not updating the owning groupID |
Fix: Repaired the code to properly update the ownership table to reflect the new groupID | |
4474082 |
Summary: File attachments don't append to the signed pdf to a null pointer error |
Fix: Added a null check prior to the process where files are added to the final PDF | |
4475331 |
Summary: When CC sends a reminder to the originator, an error occurs the next time the Reminders button is clicked. |
Fix: Distinct logic has been added for this use case. | |
4475449 |
Summary: Documents with invalid Creation Dates will fail to process and become downloadable |
Fix: Code has been added to ensure that a valid creation date is available before saving. | |
4475603 |
Summary: The group is not selectable when in the Russian locale due to extra quotes in the locales script. |
Fix: The code for the Russian locale has been corrected so the script can run |
|
4475864 |
Summary: Upload signed copy is changing the signature type from written to design, preventing the agreement from being uploaded |
Fix: The code has been improved to properly retain the "written" signature type throughout the process. | |
4476004 |
Summary: Adobe Acrobat Sign events and alerts summary email is not getting triggered due to a legacy event alert. |
Fix: The legacy event alert has been removed. | |
4476583 |
Summary: Workflow's Completion Deadline not updated when set to 180 days due to the logic understanding the value must be less than 180, not less than or equal to. |
Fix: Fixed the parameter to properly accept less than or equal to | |
4477114 |
Summary: Unable to sync Custom Workflows from Sandbox to Production using Sandbox Sync feature |
Fix: Optimization has been added to improve sync times to prevent timeouts | |
4478119 |
Summary: Invalid negative number variable expression throws an exception when trying to edit a template |
Fix: Added a check to prevent the NumericFormatExceptions from being a string-based negative number |
|
4478127 |
Summary: The email footer shows the path to the image when linkless notifications are enabled. |
Fix: The code has been corrected to display the image instead of the path. | |
4478248 |
Summary: Written agreements fail when a signer uploads an esigned PDF because we modify the PDF for the next signer which invalidates the certificate and fails the validation of a signed document for the next signer. |
Fix: Logic has been added such that if the agreement is a written agreement, remove the esigned certificate when creating the pdf for the next signer. |
|
4478745 |
Summary: Unable to download signed document due to a null pointer error if the fontfile does not contain a valid cmap table. This aborts watermark generation and the document cannot be generated. |
Fix: New tests have been added for a valid cmap to preserve the page graphic state. |
|
4478901 |
Summary: When a signer attempts to decline signing an agreement that is hidden through the e-sign page, they encounter a server error due to a method that is intended to check if we are going to list a hidden agreement in any response |
Fix: A new method is being applied that checkz if the caller can edit the participation. |
|
4479209 |
Summary: The email address in the linkless notification instruction, when copy-pasted into the linkless access form page, has spaces in front, in-between and after the email address string and thus gives an error to users. |
Fix: The client-side Javascript now finds and removes all white spaces/line breaks before, after, and in between the email address string before submitting the form and passing the form data down to validation logic and access code read request. |
|
4479223 |
Summary: Date Field format not saving for form fields on AcroForm form fields |
Fix: The date format saved at the group level is not referenced and honored as expected. | |
4480119 |
Summary: Cannot delegate to users included in the CC when the signature was sent. |
Fix: Added a condition to not throw an exception for delegation to "Observe only" and CC participation | |
4480324 |
Summary: Unable to upload CSV in Send in bulk new experience if the Order column isn't completely filled in |
Fix: The code has been updated to allow for empty cells in the Order column | |
4480375 |
Summary: The redirect URI linked in the signup mail that the user receives after confirming their account is incorrect. |
Fix: The link has been updated to /adobeLogin which was incorrectly set to /adobeIDLogin |
|
4480399 |
Summary: There are form fields in some dialog fields that don't have visible, persistent labels, nor are they grouped in a fieldset to programmatically determine their relationship with each other. There are also no validation error messages. |
Fix: Added error messages, labels, and fieldsets with appropriate tags where applicable. Update placeholder text. |
|
4480403 |
Summary: Accessibility labels were missing in certain fields in the Custom Compose JS page, which prevented screen readers from reading the error message when that field was highlighted. |
Fix: Accessibility attributes have been added and the error message that was missing has been added to the modal at the top. |
|
4480407 |
Summary: Accessibility: The meaning of icons is not communicated to all users |
Fix: Added the ID to the recipient email input |
|
4480582 |
Summary: Signer Authentication not being set when sending the agreement to an alias email |
Fix: Added a check to set signer authentication for the recipient when an alias email is used | |
4480614 |
Summary: Agreements can get stuck when using a hybrid workflow and delegating recipients to an alias email. |
Fix: The order of processing for several modules were updated to account for all of the potential cases around delegating known users to aliased emails through a hybrid signature flow. | |
4480638 |
Summary: An interface conflict prevents users from disabling the PayPal option when using the payment interface |
Fix: Code has been improved to allow manipulation of the option to use PayPal. | |
4481121 |
Summary: Notifications aren't sent to agreement shares due to a check for notifications that removes the sharee |
Fix: The logic has been fixed to manage this use case | |
4481307 |
Summary: Written signature flow agreements with multiple signers can fail due to a miscalculation of the total number of participants being less than the total remaining participants, leading to an out-of-bounds index |
Fix: The calculations between the two sets of recipients is now calculated in the same manner to produce the correct results. | |
4481336 |
Summary: Sending in Bulk fails with an invalid CSV error if Senders aren't allowed to override the default authentication, internal auth is enabled, and the internal recipient's signer auth doesn't match the internal default. |
Fix: The CSV parsing code has been improved to manage this use case | |
4481340/ 4482600 |
Summary: "Powered by Adobe Acrobat Sign" image and horizontal rule overlapping KBA options for Web Forms due to the CSS width being too small |
Fix: Removed web form styling so it behaves the same as for regular agreement. |
|
4481902/ 4471416 |
Summary: Form fields are duplicated when using Templates through Send in Bulk due to the field template being applied from the team plate and the authoring stage |
Fix: The process for applying the field template has added logic to account for the template fields if available. | |
4481984 |
Summary: Timeout exceptions can lead to Send in Bulk transactions to create duplicate agreements |
Fix: A check has been added to identify if a child agreement already exists for the parent transaction. | |
4482743 |
Summary: Error " SEND_IN_BULK_WITH_ADV_ACCOUNT_SHARING_ROLLOUT" when using Send in Bulk on the Sandbox due to a setting not being enabled |
Fix: The setting was enabled, and the error was resolved. | |
4482746 |
Summary: Error: The request provided is invalid, while adding alternate recipient due to strings being passed as empty values instead of null values |
Fix: While equating names of participants, we are replacing empty String with null. | |
4483022/ 4484322 |
Summary: Send in Bulk may return a blank page when a horizontal scroll bar is visible on the Templates table |
Fix: The rendering processing of the template has been improved to account for this use case. | |
4483680 |
Summary: Update REST API documentation for Post Webhook api to add the feature resourceId and GROUP scope |
Fix: The API Swagger documentation has been updated | |
4484234 |
Summary: When using a custom workflow with more than 25 recipients, an error is triggered due to a hard-coded limit of 25. |
Fix: The hard-coded limit has been removed and replaced with the appropriate variable for the tier of service | |
4486809 |
Summary: When "well-formatted" signatures are disabled, the signature field can be reduced on the final document such that some of the signature is cut off |
Fix: Left padding points have been implemented for the signature field when "well-formatted" signatures are disabled. | |
4489678/ 4494301 |
Summary: When canBeDelegated is missing from the mail context, typically on a Custom Email Template, a Null Point Error is thrown |
Fix: A check to determine if there is a null value has been added before calling methods that will throw the error. |
|
4490021 |
Summary: Unable to download a signed copy of the agreement from the post-sign message page, if the post-sign redirect URL is specified during agreement creation |
Fix: The link to download the agreement has been added to the post-sign page | |
4490903 |
Summary: Unable to fill Web Form due to pop-ups in mobile devices |
Fix: Updated the code not to show terms of use popup on focus for mobile case |
The November 2024 release is a major release containing features, updates, and fixes for customer-reported issues.
- Sandbox release: October 15, 2024
- Production release: November 12, 2024
- GovCloud release: November 19, 2024
The December 2024 release is a minor release containing relatively minor feature updates and fixes for customer-reported issues.
- Sandbox release: November 11, 2024
- Production release: December 9, 2024
- GovCloud release: February 17, 2025
The February 2025 release is a minor release containing relatively minor feature updates and fixes for customer-reported issues.
- Sandbox release: January 13, 2025
- Production release: February 10, 2025
- GovCloud release: February 17, 2025