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
- 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
- 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
- Recipient Agreement Access
- 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 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).
When the release is published, the new pages will also be 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.
- 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: October 28, 2024
Production deployment: November 12, 2024
GovCloud deployment: November 19, 2024
Improved Functionality
- Restart Agreement - Allow recipients to reset the agreement's signature cycle back to the first recipient. Any previously filled fields will remember the field values as the new default value but can be edited by the recipient they are assigned to.
Available environments: Sandbox, Commercial, Government | Available tiers of service: Acrobat Sign Solutions | Configuration scope: Group, Account
Review the document for the Restart agreement workflow option >
- Share templates with multiple groups—Create one template and share it with one or more groups. Updating the template will propagate across all groups with which it has been shared.
Available environments: Sandbox, Commercial, Government | Available tiers of service: Acrobat Sign Solutions | Configuration scope: Group, Account
Review the controls to allow sharing a template with multiple groups >
- Send in Bulk improvements:
- Government ID authentication - Send in Bulk now supports Government ID as a recipient authentication method.
- Delegator roles - The Delegator role has been added to the Send in Bulk list of roles when using a CSV file to add recipients.
- Government ID authentication - Send in Bulk now supports Government ID as a recipient authentication method.
Available environments: Sandbox, Commercial, Government | Available tiers of service: Acrobat Standard, Acrobat Pro, Acrobat Sign Solutions | Configuration scope: Group, Account
Review the new Send in Bulk documentation here >
- 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
Review the Manage page overview >
- eWitnessing is supported in parallel and hybrid signature workflows - Agreements that require parallel or hybrid signature flows can now utilize the eWitness recipient role.
Available environments: Sandbox, Commercial, Government | Available tiers of service: Acrobat Sign Solutions | Configuration scope: Group, Account
- Power Automate - Template selection from within the Manage page - Using the Power Automate Set-up Notification or Archive Agreement actions on the Manage page open a menu of templates in the right context panel, making it easier to create flows from existing agreements.
- This improvement is expected to be delivered after the November 12th launch date.
Available environments: Sandbox, Commercial | Available tiers of service: Acrobat Sign Solutions | Configuration scope: Group, Account
Review the new experience for the Power Automate actions on the Manage page >
- Identity Check improvements - The Identity Check policy has been improved to allow for name matching through the user interface (not just API) and to allow for partial name matching.
Available environments: Sandbox, Commercial, Government | Available tiers of service: Acrobat Sign Solutions | Configuration scope: Group, Account
Learn more about the Identity Check policy >
- Data Exports for Web form-based agreements - The Data Export option now has an additional data export for web form usage that includes new filters to help manage the signature process of web forms exclusivly.
Available environments: Sandbox, Commercial, Government | Available tiers of service: Acrobat Standard, Acrobat Pro, Acrobat Sign Solutions | Configuration scope: Available by default; Not configurable
Learn about the new Web Form Data Exports >
- Expanded options to notify CC'd parties - CC'd parties can be associated with specific recipients to ensure notification happens to the right CC'd party at each stage of the agreement signature process.
Available environments: Sandbox, Commercial | Available tiers of service: Acrobat Sign Solutions | Configuration scope: Group, Account
Learn more about recipient-related CC notifications >
- Add the agreement name and transaction ID to the footer of every page of an agreement - Enable an option to affix the agreement's Name and Transaction ID to the bottom right of every page of the transaction.
Available environments: Sandbox, Commercial, Government | Available tiers of service: Acrobat Sign Solutions | Configuration scope: Group, Account
Review the option to add the transactionID and doc name to the agreement pages >
- Authenticate the first signer of a web form using a digital identity - Configure web forms to authenticate the first signer using a digital identity when they initially access the web form's public link.
Available environments: Sandbox, Commercial, Government | Available tiers of service: Acrobat Sign Solutions | Configuration scope: Group, Account
Review the Create a Web Form documentation >
Experience Changes
- Improved signer experience for the mobile web interface—Users of the mobile applications will have a new experience that better highlights the recipients' elements within the agreement. This environment is enabled through the same admin control that enables the new recipient experience for the desktop
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.
- Updated API interface - The API Swagger documentation has been updated to a new version (OAS 3.1) that changes the overall appearance of the page. The content remains the same.
- New Webhook for when agreements are restarted - The Restart Agreement webhook AGREEMENT_RESTARTED has been added to support the event when a recipient restarts their agreement.
- The POST /agreements/{agreementId}/deliverableAccess endpoint has changed the API Category to PUBLIC instead of EXTERNAL_PARTNER.
Release errata - Elements added
Below are items that have been added to this release since the initial publishing of the pre-release notes.
- 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
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.
- Password protection for PDFs has been refined to only apply to PDFs that have been downloaded - As new interfaces have been developed, Acrobat Sign has started retrieving the actual PDF for the user to view or interact with (instead of an image, which was the legacy process). This has caused agreements with embedded password protection to challenge users to enter the password, even though the PDF remains within the Acrobat Sign system. With this release, password protection will be embedded when the PDF is downloaded, ensuring that PDFs within Acrobat Sign remain accessible and only PDFs that are removed from the system (downloaded) have the password embedded.
- Power Automate - Enhanced AI-driven assistant to build flows - A new AI assistant is available to help users create new flows in the Power Automate system. Using the AI assistant, users can easily identify what they want to automate and what systems (Sharepoint etc.) they want to use. The AI helps configure the objects under the hood and delivers useful automation quickly.
- Control the visibility of an agreement on a user's Manage page—Enable the option for senders to control if a recipient should have the agreement included in their Manage page. Given the rules around user/group content sharing, there are situations where having an agreement shared is undesireable (offer letters for example). Recipient Agreement Access allows the sender to identify one or more recipients to have the agreement excluded from their official body of agreements tracked on the Manage page, ensuring their privacy.
- Updates to the Custom Send Workflow Designer user interface - The Custom Send Workflow Designer has updated the user interface to align with the new Request Signature format and style, giving users a consistent environment to build their agreements.
Resolved Issues
Issue | Description |
---|---|
4469029 | Summary: Bad email settings error thrown in the Custom Workflow Designer |
Fix: The logic controlling the error has been improved. | |
4472759 | Summary: Inconsistent behavior between the new and classic send experience when using "Download and sign with Acrobat" and multiple digital signature fields. |
Fix: The classic send experience has been improved to match the new experience. | |
4474898 | Summary: Lag when loading Template data on the Manage page when group sharing is ON. |
Fix: Methods have been added to avoid repetitive database calls, improving load times. | |
4475508 | Summary: Unable to update user Group Via Rest Api V5 for users with an apostrophe in the name. |
Fix: Code improved to gracefully account for the character. | |
4476530 | Summary: Compose page shows incorrect reminder frequency when creating a draft agreement via the API and then navigating to the request signatures page. |
Fix: Logic was added to ensure that the proper object value is not unset, and if a null value is found, the inherited default value is used. | |
4478261 | Summary: Signer unable to complete digital signature using 'Intesi' Cloud Signature Provider on agreements consisting of multiple digital signature fields due to file size of signature images |
Fix: Unnecessary images have been removed from the request body. | |
4478970 | Summary: Agreements can be sent out using the wrong locale in the new Request Signature environment |
Fix: The logic that applies the localization value has been improved to ensure the right value is applied. | |
4479498 | Summary: Delegatees of an agreement could not have the nextToSign flag returned to False, if someone else signed the agreement |
Fix: The logic to update the flag has been improved. | |
4481738 | Summary: Recipients mentioned in parallel order at the end of the signature cycle are not getting encircled like other recipients who are also kept in parallel order |
Fix: The graphic is now applied to the last pairing. | |
4481761 | Summary: The custom workflow designer doesn't include the e-Witness role for recipients |
Fix: The role has been added. | |
4482080 | Summary: Users could see other users not in their group through account sharing menus. |
Fix: Content-sharing menus have been updated to observe the settings for user access levels. | |
4482094 | Summary: Viewing an agreement using OTP can cause an error after 5 views that the number of views has been exceeded. |
Fix: The code has been updated to use a new threshold value for the "views exceeded" error. | |
4483719 | Summary: When users who have their signing authority removed attempt to use Fill & Sign, an unexpected error is triggered. |
Fix: Code has been added to prevent users who don't have the authority to sign from accessing self-signing workflows. | |
4483914 | Summary: In a written signature flow, Signer 2 is unable to open the agreement when signer 1 uploads their document with 256-bit encryption. |
Fix: The digital certificates are now removed from the uploaded signed copy when signer 1 is uploading. | |
4483942/ 4488212 |
Summary: New Send in Bulk Authoring does not show all Shared Group Templates on the Send page due to an undersized fetch parameter. |
Fix: A larger pageSize query parameter has been added when fetching library documents. | |
4484039 | Summary: Text Fields with date validation formats are not saving for Acrobat form fields due to the None value being mishandled. |
Fix: Refactored the existing code that handles the "None" use case. | |
4484055 | Summary: Trying to change the TEXT FORMAT in authoring can produce an error message "An unexpected error has occurred. Would you like to reload the page to try again, or return home." |
Fix: New code has been added to manage the error condition and resume editing. | |
4485315 | Summary: Webform with calculated fields enters a repeating loading status due to too many recursive calls to the expression utility. |
Fix: Send resulted set of field names as a parameter except re-instantiating it each time when the method is called. | |
4485677 | Summary: Unable to sign a document from Adobe Sign iOS mobile application due to form fields with conditions not being returned in the GET API. |
Fix: The API was improved to properly manage the calculated values. | |
4486008 | Summary: Reminder emails were sent ignoring the backend setting SEND_REMINDER_EMAIL = false due to the inheritance ignoring the group setting. |
Fix: The code has been improved to reference the group-level setting. | |
4486155 | Summary: New Send in Bulk experience returns an error 'Column [Recipient_1:Auth_Type]: Invalid authorization type specified.' when using Acrobat Sign as the identity authentication method |
Fix: Updated documentation to clarify the CSV values. | |
4486276 | Summary: Required fields created from Acrobat are not required on Webforms because the logic between agreements and web forms is different, and their last participant values are different. |
Fix: Separated the logic to check if the agreement is based on a web form or not. | |
4486331 | Summary: The default text value In Web Form text fields is removed when the Signer is required to verify their email prior to viewing the form because the fields are cleared when the child copy is created. |
Fix: The field values will be fetched from the parent template's default values. | |
4486748 | Summary: The Template Filters are Not Filtering Properly because the group name in the agreement table is not updating properly. |
Fix: The agreement table is now updated with the latest info when details are changed. | |
4486767 | Summary: Download PDF Button is missing from Read Agreement View |
Fix: The graphic and functionality have been returned to the list of options | |
4486829 | Summary: The Account Administrator is listed as Group Admin on the Primary Group even when not explicitly set as Group Admin when Show Only Admins is selected. |
Fix: Improved the filtering to properly reflect the admin status. | |
4486863 | Summary: Emails are not getting triggered for shared notifications intermittently due to null pointer exceptions. |
Fix: Added null pointer checks to fix NullPointerExceptions that are causing emails not to be sent | |
4486893 | Summary: If an agreement is not exposed to the signer (due to backend settings being true), then the signer can sign the agreement but not decline it. |
Fix: Added a condition to check whether the signer should be allowed to decline the agreement or not | |
4486894 | Summary: Allowed IP Ranges can be blocked from adding new ranges due to incorrect property inheritance |
Fix: More granular arrays have been added to prevent data collisions from external parent objects. | |
4486919 | Summary: When group recipients are configured to notify, participant status is not updated to WAITING_FOR_OTHERS after signing. |
Fix: Code updated to ensure the whole participant set is updated when one recipient completes their action. | |
4486934/ 4496641 |
Summary: Calculated field loses formatting in final signed agreement/pdf, when signed in a locale using a comma as a decimal separator and one of the decimal digits is not zero |
Fix: The number formatting has been improved to manage the locale where the commas are used as a decimal separator. | |
4487113 | Summary: "Error marshaling data" occurs when applying a form field layer while editing a shared template due to an outdated null check . |
Fix: Removed the unused parameter and its null check from the method. Updated all calls to this method to reflect the new signature. | |
4487589 | Summary: AUTO_CANCELLED_CONVERSION_PROBLEM (COMMENT: PROJECT_TIMEOUT) due to stack overflow while combining PDF files. |
Fix: Improve code to detect XObject Form cycles and AcroForms without fields. | |
4488298 | Summary: Signature panel shows 'Edit' button even though no edit is allowed |
Fix: Conditions added to filter out the option when not available. | |
4488322 | Summary: The label is missing in a few agreements on GET /agreements/{agreementId}/documents API call due to it being set too early in the process |
Fix: The timing for applying the label has been updated. | |
4488449 | Summary: Any subject that includes a dot in the subject is treated as a link. |
Fix: The regex identification for the original template in the Subject line has been removed. | |
4488647 | Summary: GET /users is failing with "Some miscellaneous error has occurred" due to massive full table scans |
Fix: A condition to check for single-use users was removed. | |
4489025 | Summary: Sign then Send option not available in the new Request Signature experience. |
Fix: The functionality has been added. | |
4489028 | Summary: Web Forms section not visible under Account/Group settings for Developer accounts |
Fix: Web Forms have been added to the Developer Tier of service | |
4489132 | Summary: When EXPOSE_AGREEMENT_AFTER_SIGNING_ENABLED is TRUE, the signer is unable to delegate the agreement due to the API providing the wrong status. |
Fix: Updated the code to provide the correct response. | |
4489203/ 4489407 |
Summary: Unable to download form field data for library templates due to performance issues with templates and web forms. |
Fix: Refactored the fetching code to reduce the number of loops for the same object values. | |
4489539 | Summary: The Last Updated column shows a recent modified date but agreement has not been updated due to the column reflecting the last modified date value. |
Fix: LastUpdated column will now use Last Transaction Date instead. | |
4489666 | Summary: Repeatedly clicking the export user data button while the download operation is in progress can generate an excessive number of database queries. |
Fix: The export button is now disabled while the export is in progress, and re-enabled once the export is completed or if an error occurs. | |
4489708 | Summary: If an unverified signer's wet signature is uploaded by the sender, then an error is thrown, because Acrobat Sign is trying to verify the participant first |
Fix: Added a check for the sender's action to allow for this use case. | |
4489748 | Summary: The participant is unable to attach a file in the attachment field due to a conflict with the Content Security Policy. |
Fix: Added the documentcloud.adobe.com domain to the internal .jsp | |
4489806 | Summary: The SMS is getting sent to the recipient and the sender is receiving a false email for non-delivery of the SMS.when Custom Email Templates are used. |
Fix: Corrected the code that manages notifications to the email address when SMS is used. | |
4490094 | Summary: Exported form field data doesn't contain all data fields for agreements created via new Send in Bulk experience when the template was built in the previous version of Send in Bulk |
Fix: Improved the form export from the previous version template to the new environment. | |
4491200 | Summary: The Send in Bulk environment isn't displaying prefilled calculated date fields for recipients. |
Fix: The logic for how prefill fields are related to the child agreement(s) has been updated to ensure the prefill content is populated as expected. | |
4491429 | Summary: Unable to process payments if payment field is calculated field with a read-only field in the formula, but only when prefill fields are present in the agreement. |
Fix: Modify payment logic for prefill case to avoid setting default value for fields that are not present in prefill fields list (like read-only fields). | |
4491502 | Summary: Phone Authentication label text is not legible on smaller viewports |
Fix: The font size was increased to 13px. | |
4492386 | Summary: An increase in file size after Document Processing can cause issues with file size limitations. |
Fix: A new processing library has been put in place to improve the updated file size. | |
4493280 | Summary: Workflow "completed" emails were not delivered to some recipients due to conflicting roles (recipient and Cc'd party) |
Fix: New methods are provided to add logic to utilize the best participation role when multiple roles exist. | |
4493288 | Summary: Time zone does not show the legally correct text for some locales. |
Fix: Additional enum values have been added to the time zone selector to include the additional options. | |
4493570 | Summary: The option to limit access to agreements through the transaction number without login are not respecting group level settings. |
Fix: The setting has been redesigned to accept the groupId's value. | |
4493717 | Summary: Changing the field type for a field using the new authoring environment on the Edge browser causes flickering due to styling. |
Fix: The styling that causes the graphical flickering has been removed. | |
4494031 | Summary: Disabling the new authoring page in favor of the classic compose environment does not respect the configured settings. |
Fix: The authoring controller now uses the agreement originator's group membership and respects that group's settings accordingly. | |
4494284 | Summary: New authoring experience does not use the sending group setting for digital signature. It will use the setting from the primary group. |
Fix: The setting has been updated to respect the group configuration. | |
4496116 | Summary: Custom email display name from AGREEMENT_SEND_CUSTOM_FROM_EMAIL_DISPLAY_NAME setting is not shown |
Fix: Updated the macro that inserts the name value to use a more reliable source. | |
4496561 | Summary: The feature that enforces the setting to prevent users in a specific group from uploading documents from their computers isn't being respected at the group level. |
Fix: Code logic updated to respect group-level setting for local file upload when changing groups | |
4499981 | Summary: IP ranges UI display is not displaying the saved values nor any of the buttons is accessible due to the size of the div on the page. |
Fix: The size of the div has been increased to the height of the element. | |
4501353/ 4503262 |
Summary: Send in Bulk transactions intermittently send emails due to a null point exception. |
Fix: Logic added to help discover the sender's groupId and default to an empty string if unsuccessful. | |
4501414/ 4503383/ 4504559/ 4504619/ 4504658 |
Summary: The new Authoring environment displays fields for participants that aren't added to the agreement and may present error messages preventing authoring. |
Fix: Code has been added to ignore field placement for fields assigned to participants that aren't included in the agreement recipient list. | |
4501428/ 4503930 |
Summary: Signing is blocked when the recipient's name is not allowed to be edited during the signature process and:
|
Fix: Added a check to see if the name matches the saved user name in addition to existing checks. Bypass the check if the participation includes a digital signature field. Bypass the check for ADOBE_SIGN, KBA, and GOV_ID authentication types. | |
4501444 | Summary: Use "Next" instead of "Finish" for the mobile eSign view field navigation header button label when all required fields are completed. |
Fix: Button updated. | |
4501750 | Summary: Signing is prevented when a registered user changes their name and the setting allowing them to edit their name is disabled. |
Fix: Logic added to check the name against previous versions, if the signature includes a digital signature, and when using Acrobat Sign, GovID, and KBA authentication types | |
4502421 | Summary: The sender is being excluded from reminder recipients due to a change in the logic that filters recipients. |
Fix: The code has been reverted and the original logic has been restored. |
The February 2025 release is a minor release containing relatively minor feature updates and fixes for customer-reported issues.
- Sandbox release: January 14, 2025
- Production release: February 11, 2025
- GovCloud release: February 13, 2025
The March 2025 release is a minor release containing relatively minor feature updates and fixes for customer-reported issues.
- Sandbox release: February 19, 2025
- Production release: March 11, 2025
- GovCloud release: March 18, 2025
The April 2025 release is a major release containing features, updates, and fixes for customer-reported issues.
- Sandbox release: March 25, 2025
- Production release: April 15, 2025
- GovCloud release: April 22, 2025