Adobe Acrobat Sign Release Notes


This document highlights the new features,  experience changes, and resolved issues in the customer-facing application for the most recent release.

Developer-centric updates to the API and Webhooks are documented in the Acrobat Sign developer guide.

Not all features/changes are guaranteed to be enabled on the date of the release.

Production deployment: March 12, 2024

GovCloud deployment: March 19, 2024

Improved Functionality

  • The new Request Signature experience updated with additional feature support - The new Request Signature experience takes a big step towards parity with the classic experience by adding support for:
    • Seamless authoring experience (navigate back to the agreement configuration from the authoring environment)
    • Organizational contacts in the address book
    • Recipient groups, both ad-hoc and reusable
    • Modifying agreements in flight
    • OneDrive file upload

Available environments: Sandbox, Commercial | Available tiers of service: Individual, Teams, Enterprise | Configuration scope: Not configurable

  • Recipient identity check - Administrators can configure their account (or group) to require a check of the recipient's email address to match the expected value (as defined when the agreement is composed) when the recipient authenticates using the Digitial Identity Gateway.

Available environments: Sandbox, Commercial, Government | Available tiers of service: Individual, Teams, Enterprise | Configuration scope: Group, Account

  • Scope improved for the Block recipients by geolocation feature - The feature to block recipients by geolocation has had its scope improved to allow group-level configuration.

Available environments: Sandbox, Commercial | Available tiers of service: Enterprise | Configuration scope: Not configurable

  • User-led provisioning for Microsoft Power Automate within Acrobat Sign – Users who wish to create workflows within Acrobat Sign using the Power Automate integration can now provision access on behalf of their organization.
    When a user selects to create a new workflow, they will be presented with the Adobe Terms of Included Entitlement, Limits on Use Capacity, and the Microsoft terms and conditions, which they must agree to in order to enable the Power Automate integration.
    Administrators who would like to manage access to user-led provisioning can do so by navigating to Global Settings > Power Automate Workflows.

Available environments: Sandbox, Commercial | Available tiers of service: Enterprise | Configuration scope: Group, Account

  • Send agreement links via SMS to the recipient's phone number - Senders can optionally configure their agreement to send the agreement links directly to the recipient's phone number (in addition to the email address), allowing the recipient to review and sign the document directly on their smartphone without going through email first.

Available environments: Sandbox, Commercial | Available tiers of service: Enterprise | Configuration scope: Group, Account

Available environments: Sandbox, Commercial, Government | Available tiers of service: Enterprise | Configuration scope: Group, Account

  • Flatten uploaded files to embed default field values before authoring - Customers who build forms and templates that have fields containing default values can enable this feature to "flatten" the document after upload, embedding any default values into the source document before opening the authoring environment. This ensures that users cannot mistakenly alter the default values of the uploaded file during the authoring experience.

Available environments: Sandbox, Commercial, Government | Available tiers of service: Enterprise | Configuration scope: Group, Account

  • Private message support for CC'd parties on web forms - The CC'd participants on a web form can now have a private message configured that will be included in the email notification they receive when the agreement is completed.

Available environments: Sandbox, Commercial, Government | Available tiers of service: Enterprise | Configuration scope: Not configurable

  • Agreement metadata for Cloud Signatures - When creating digital signatures via third-party Trust Service Provider (TSP), Acrobat Sign can now optionally send additional metadata to the TSP. The included data is:
    • Account ID - For identifying the customer account and processing transactions enabled at the account level.
    • Group ID - For identifying the customer's group when a group has enabled a specific TSP for signature processing.
    • Transaction ID - To provide additional support in validating transaction processing per transaction. Useful in understanding the customer's consumption and billing with the vendor.

Available environments: Sandbox, Commercial | Available tiers of service: Individual, Teams, Enterprise | Configuration scope: Group, Account

Experience Changes

  • The classic Send page environment is changing the Email authentication type to None - In the list of authentication types on the classic Send page, the Email auth type has been changed to read None. The functionality has not changed. Agreements are still sent to the email address of the recipient provided Email is one of the types of delivery selected.
    The new Request Signature environment continues to use the term Email for now and will be updated to use None in a future release.
The classic Send page, highlighting the None authentication method

  • The format of email headers has changed to alter the From property for recipient emails, such as the initial "Please Sign" and Reminder templates. The previous format of "Adobe Acrobat Sign on behalf of <SomeUser>" has been changed to "<SomeUser> via Adobe Sign". The shorter format will ensure that the sender's name is not truncated.
Two email headers, one highlighting the legacy header, and the other highlighting the new header

  • The footer text that prefaces the Click to Sign banner has been updated from "By signing, I agree to this agreement, the Consumer Disclosure, and to do business with <Sender>" to "By signing, I agree to this document, the Consumer Disclosure and to utilize electronic signatures."
Both the legacy and new Click to Sign banners

  • VIP customer access to the new Chatbot experience has been suspended - The new Chatbot has been suspended until the next release in April 2024. 

Integration Updates

  • Support for secondary authentication methods in Microsoft integrations - Obtaining a signature through the Microsoft Teams, Outlook, and Word/PowerPoint integrations now supports using secondary authentication methods like Phone (SMS) authentication.

  • Acrobat Sign for Veeva Vault updated to v1.3.0 
    • Veeva Vault Library Upgrade - The application has been updated to a more modern and efficient Vault API library (VAPIL) for enhanced integration.
    • Veeva Vault API version Upgrade - The Veeva Vault API version has been upgraded to v23.1
    • The Integration deployment package has been enhanced to ensure no requirements are imposed on customers to use the latest document version.

Update your Veeva Vault integration >

REST API/Webhook Updates

API and webhook updates for this release can be found in the Acrobat Sign API documentation.

Resolved Issues

Issue Description
Summary: The user guide within the application is not opening localized user guide pages.
Fix: The localization code for how the user guide URL is mapped was corrected.
Summary: Accessing any agreement, template, or web form from the Manage tab is throwing an error on the console.
Fix: A deprecated library was removed to eliminate this error.
Summary: Obtaining a written signature on an iPad causes a reload cycle when popups are disabled on a mobile device.
Fix: Pop-up detection added and an error dialog has been added to allow the user to explicitly allow the pop-up.
Summary: The "Click to sign" button doesn't work when the Email is selected from autofill in MS Edge when signing a Webform.
Fix: Added a new "confirm email field" in the reset fields method.
Summary: Completed agreements sent using a workflow do not email the sharee.
Fix: The XML related to sharing agreements has been added to the workflow templates. New workflows updated or created after the March 2024 release will now include the share notification process.
Summary: When a singer has two or more initial fields that have a showIf condition applied to appear with the first initials field is filled, the second field is not exposed.
Fix: The field mapping values have been corrected to allow for the proper actions regarding showIf conditions.
Summary: When senders add an alternate participant, existing unexpired reminders do not have the new recipient added when the sender's choice option is enabled.
Fix: The code has been fixed to allow the new recipient to be added.
Summary: Navigation panels don't have the appropriate contrast ratio of 3:1 for a focus indicator
Fix: The identified side menus and body tables have been updated to have blue indicators with the appropriate contrast ratio.
Summary: When there is a recipient group or delegation. The 'on behalf' mail always shows the signer in the 'header' when the option to hide the recipient email is set to true.
Fix: Modified the header to set the right recipient address.
Summary: Recipient order in a data export CSV, "Number of Remaining Recipients" or "Number of Complete Recipients" is incorrect.
Fix: The impacted functions have been updated to produce the expected result.
Summary: Sandbox - Error seen while customizing the "Company" field using the new authoring experience and using a template created in the classic authoring environment.
Fix: The API has been updated to properly identify and make available the fields.
Summary: Inconsistent delegation for recipients that are already participants in an agreement depending on the recipient's status in the Acrobnat Sign system.
Fix: The impacted functions have all been corrected to provide a consistent experience (Participants already in the agreement cannot be delegated to)
Summary: The Phone authentication default is not working for group-level workflows.
Fix: Updates to the workflow designer have corrected this issue.
Summary: Sharing status - Deleted groups are visible when a group is deleted, and an existing share is still active. If a user creates a group with the same name again, then two groups with the same name are displayed.
Fix: Deleted groups have appended a [Deleted] string next to the group name.
Summary: When sending an agreement with a 'completion deadline' on the authoring page, a duplicate agreement expiration event is created for scheduling. This results in expiry events/emails getting triggered twice.
Fix: A status check was added to identify and prevent duplicate messaging.
Summary: Text fields don't appear on the signable document if the field name is only a special character as the name is then stored as a decoded character.
Fix: Encoding of special characters in form field names when saving the updated fields on the Authoring page has been added.
Summary:  Recipient fields are moving up in the document when sending from workflow and previewing before sending.
Fix: Fixed a function issue for a function TypeError exception which prevents proper text banner for default warning.
Summary: On Bulk Send, while selecting the group from the drop-down, the logo does not change.
Fix: Added the required attributes to the bulk send model.
Summary: Filter to show only Admins isn't working as expected. Returning an error of too many users.
Fix: The filter to show only admins has been corrected, resulting in only admins returning.
Summary: If externalId is passed when an agreement is created using the Workflow in 'Draft' state utilizing the POST agreements API endpoint, then the externalId is persisted in draft_resource table. When the Send button is pressed to send the agreement, then PUT agreements/{AgreementID} call is made. As part of this call externalId is not passed from UI.
Fix: Added call to load externalId from agreementInfo object to agreement object for custom compose flow.
Summary: HTML code is observable in an error message due to HTML not being supported in the error message object.
Fix: HTML removed from the error message.
Summary: The signature field is missing in an agreement when the signer opens the agreement in two different browsers at the same time and e-signs one while attempting to print, sign, and upload in the other.
Fix: An error is delivered indicating the user should reload the page to get the refreshed page with the signature field exposed.
Summary: When the KBA authentication mandates the inclusion of both first and last names, on the custom compose page, there is a possibility of submitting the agreement without entering the necessary data.
Fix: Validation has been implemented. If the setting requires name information, an error will be displayed when the KBA first name and last name are left unfulfilled.
Summary: Update users in bulk fails for the group containing special characters.
Fix: The group name is encoded when verifying if the group already exists to align with the database entry. Special characters are encoded in the database.
Summary: Vaulting does not apply to workflows. 'Vault this agreement' is unchecked if the vaulting setting is set to On.
Fix:  If we do not have the vaulting Info value set by the user, the VAULT_BY_AGREEMENT setting is checked.
Summary: Workflows may take 4-5 minutes on average to open for some accounts.
Fix: The database calls have been streamlined to reduce overall processing time.
Summary: The attached files are removed when switching the view on the Send page.
Fix: Code improved to preserve all parameters when switching between environments.
Summary: Agreement sharing with users is not functioning for agreements sent using a workflow and signed by the sender only..
Fix: The self-sign workflow code has been improved to accommodate sharing the agreement.
Summary: POST /webhooks sometimes take more than 15 seconds to respond (or times outs) when called immediately after creating a new account.
Fix: Syncing for new account creation has been streamlined to reduce processing time.
Summary: Government ID fails if the first name of the document is empty
Fix: A check has been implemented to manage the event when a first name is blank.
Summary: Regardless of the value of the "show link in email" setting, when sharing a completed agreement, the link to view the document online always appears in the email.
Fix: Created a new template that displays the link for viewing online, depending on the value of the show link in email setting. Modified the original template to include a check for whether the agreement is signed, and added logic to display the proper template based on settings.
Summary: Agreements will fail to send if there are text tags assigned to the sender and the sender isn't a participant in the agreement.
Fix: When the source document has text tag fields assigned to the "sender" role, they are deleted if the sender isn't participating in the agreement.
Summary: When changing the authentication method of a previously saved Draft agreement, the authentication method isn't updated.
Fix: When processing a recipient for the first time, the default auth method from their per-recipient settings is used.
Summary: The GET /agreement/id/formFields endpoint throws an NPE due to a PDFLink with an empty location.
Fix: Code has been added to manage the NPE issue. PDF links with no location are now omitted.
Summary: Acrobat Sign will continue to attempt to thumbnail an abandoned document if the document is large enough, resulting in a timeout error.
Fix: Code update to allow abandoned thumbnails to be completed, regardless of the abandoned status.
Summary: Web forms can fail in a way that prevents them from being able to be opened.
Fix: The logic around how web forms are processed has been updated to unblock a form that is failing to properly apply validation checks.
Summary: Workday - Documents with invalid annotations throw exceptions, causing the agreement to be canceled.
Fix: Annotations with no subtype are now ignored.
Summary: The Sender group column is missing on CSV export.
Fix: The column has been added to the export.
Summary: Web forms can be automatically canceled due to a null pointer error due to unknown participants.
Fix: Code has been added to properly manage the unknown participants.
4466885 / 4467126

Summary: UMG-enabled accounts send all of their groupIds in the header when sending a Bulk Send, which can be more than the max header size the microservice accepts.
Fix: The max header size has been increased.
Summary: Unable to sync Custom Workflows from Sandbox to Production due to faulty user encoding.
Fix: User encoding has been corrected for the syncing process.
Summary: The KBA verification will validate only the first member of the group of recipients and let you send the agreement even if the other members have a KBA auth and name info left empty.
Fix: The compose page now loads with a null recipient order, forcing a name check.
Summary: In the sandbox environment, the e-sign page has an extra space between the header and the sandbox blue bar
Fix: The header has been modified to allow a full view of the text.
Summary: In the e-Sign page's Option and Help menu, keyboard users are unable to navigate away from the expanded dropdown menu using the Tab key.
Fix: The Tab key can now close the menu. The focus shifts back to the dropdown trigger button after the menu is closed.
Summary: Even when set to 'Not Allowed' in the new experience, the agreement name can still be changed.
Fix: Editing has been restricted based on the workflow configuration.
Summary: CC info is not seen on the Manage page, the CC recipient does not receive the final signed filed email, and CC info does not appear in the Email body if the sender does not press "Enter" after entering the information.
Fix:  The information for the CC'd parties has been added to the agreement when the field loses focus.
Summary:  Required hyperlinks from library templates are duplicated on the e-Sign page resulting in unsignable agreements.
Fix:  How fields are transferred to child agreements form templates have been updated to ensure only one field is present.
4472895 Summary: If a sender uses the same email address as a Sealer recipient, but the case used in the email is different, an error will be triggered due to case sensitivity.
Fix: Case sensitivity has been removed when assessing the strings in this use case.
4472954 Summary: Sync speed for workflows between the Sandbox and Production environments is very slow.
Fix: Improvements to the query and code have improved sync time.
4474353 Summary: Connecting a Salesforce application to the Acrobat Sign Sandbox fails to redirect the user to the correct page due to the target URL not being set properly.
Fix: The code has been improved to set the target URL correctly and facilitate the user redirection.
4474581 Summary: The Sandbox stopped pushing webhook notifications after a rebuild of the Sandbox environment.
Fix: The Sandbox was redeployed, and the problem was resolved.


קבל עזרה במהירות ובקלות

משתמש חדש?