Last updated on
Mar 18, 2025
Adobe Acrobat Sign Release Notes: 2025
Production deployment: February 11, 2025
GovCloud deployment: February 18, 2025
Improved Functionality
- Improved user interface for Custom Send Workflows - The Custom Workflow Designer has been updated to provide a better sender experience that aligns with the Request Signature look and feel.
Available environments: Sandbox, Commercial, Government | Available tiers of service: Acrobat Sign Solutions | Configuration scope: Group, Account
Experience Changes
- Agreement expiration may be delayed up to 12 hours - Starting with this release, the automatic expiration of an agreement will take place during non-peak hours for the environment that is managing the agreement. In practice, any agreement that expires during the peak traffic times of any given Acrobat Sign environment will be queued to execute once the environment enters the non-peak time window.
- Workday: Digital Signature support for the Aadhaar Identity Provider - Customers using the Workday integration can now use the Aadhaar Identity Provider as a method to authenticate their recipients.
REST API/Webhook Updates
API and webhook updates for this release can be found in the Acrobat Sign API documentation.
- A new accountId attribute is being added to all event notification payloads.
- OEM Embed 2.0 partners will now be able to set up a webhook for their channel and listen in to all the asset notifications from each of their individual customer accounts.
- New Settings APIs
- POST /accounts/{accountId|me}/settings/search – Takes the identified account (accountId) and a list of setting names and returns the list of setting names with their values for the account specified. Only account-level values are returned.
- Available to non-admin users.
- PUT /accounts/{accountId|me}/settings - Applies a provided list of setting names and their values to the identified account (accountId).
- POST /accounts/{accountId|me}/settings/search – Takes the identified account (accountId) and a list of setting names and returns the list of setting names with their values for the account specified. Only account-level values are returned.
- New Logo APIs
- POST /accounts/{accountId|me}/logo - Uploads the CoBrandingLogo file.
- GET /accounts/{accountId|me}/logo - Returns the image data of the CoBrandingLogo image file in the same format that it was uploaded.
- Available to non-admin users
- DELETE /accounts/{accountId|me}/logo – Clears the CoBrandingLogo image for the account.
- Signing Reason APIs
- GET /accounts/{accountId|me}/signingReasons - Returns a list of signing reasons for the identified account (accountId).
- Available to non-admin users.
- POST /accounts/{accountId|me}/signingReasons - Creates a new signing reason for the identified account (accountId).
- GET /accounts/{accountId|me}/signingReasons/{signingReasonId} - Retrieves the text of the identified signing reason (signingReasonId) from the identified account (accountId). account's identified signing reason.
- Available to non-admin users
- PUT /accounts/{accountId|me}/signingReasons/{signingReasonId} - Updates the identified signing reason (signingReasonId) from the identified account (accountId).
- DELETE /accounts/{accountId|me}/signingReasons/{signingReasonId} - Removes the identified signing reason (signingReasonId) from the identified account (accountId).
- GET /accounts/{accountId|me}/signingReasons - Returns a list of signing reasons for the identified account (accountId).
- Updated swagger pages to indicate me as a shorthand for the accountId.
Resolved Issues
| Issue | Description |
|---|---|
| 4479949 | Summary: An OIDC API calls to an IDP contain the "charset=UTF-8" parameter in the "Content-type:application/x-www-form-urlencoded" header. This generates an error instead of a valid response. |
| Fix: The charset was removed as no charset should be specified. | |
| 4490523 | Summary: A button to print the PDF is not available on the Read Agreement view. |
| Fix: A print button has been added to the Read Agreement view. | |
| 4494248 | Summary: Incorrect Agreement Expiration Times in the agreement due to the client not passing timezone information. |
| Fix: The client has been updated to be timezone-aware. | |
| 4494297 | Summary: When a user delegates an agreement on behalf of another user (using advanced account sharing), the audit report may not show the event of the delegation based on configured settings that omit or include data. |
| Fix: The function that omits data has been improved to account for situations where events take place that suppress some content, but retain the event. | |
| 4495537 | Summary: Recipients get cancellation emails as CC'd participants when an agreement is sent via Workflow and subsequently canceled without the request to notify all parties when custom email templates are used. |
| Fix: The CSS for the CEMT templates has been updated to manage cancelation scenarios like non-custom templates do. | |
| 4495963 | Summary: If delegation is disallowed for users in the account, the options to enable signing or e-sealing for a user profile is locked. |
| Fix: Dependency of delegation is removed in the UI and the setting can be updated | |
| 4496084 / 4510358 | Summary: The correct selected radio button is not being set when the radio button is specified with an options list |
| Fix: When the option list is present in a radio button, we now get the selected radio button index from the list of options. | |
| 4497823 | Summary: User message (“Invalid agreement id”) for a non-participating user session in the browser for GET /SigningUrls for a valid agreement. |
| Fix: Rephrase the user notification (“Invalid agreement ID”) to a meaningful message. | |
| 4498914 / 4501065 | Summary: Users are not able to sign the document when the authentication type is Acrobat sign with bio pharma settings enabled due to an incorrect delimiter. |
| Fix: The delimited being used has been corrected. | |
| 4499847 | Summary: The Digital settings are not honoring the UI settings, showing more providers than have been selected due to duplicate entries in the providers' list. |
| Fix: Cleanup code has been added to ensure duplicates are cleared before fetching the setting value, and before updating the setting value. | |
| 4500637 | Summary: The creation data of a pdf is represented with a long value that is the milliseconds of Date, rather than using PDF date string format. |
| Fix: In the case that the Creation Date is represented by a CosNumeric, convert it to an ASDate by getting the CosNumeric as a String and then converting it to a long and then to Date object. | |
| 4500649 | Summary: Auto-adjustment for font size is not functioning due to a bug in an upstream library |
| Fix: The library has been updated. | |
| 4501939 | Summary: "Unexpected error" or "permission error" when the signer is making payment via Braintree due to unsupported configuration with AVS. |
| Fix: Some code has been added to ignore AVS where possible. Customers are cautioned that AVS configuration is incompatible with Acrobat Sign. | |
| 4502497 | Summary: Initial field not set to Required by default in New Authoring layout |
| Fix: The default has been edited to be required. | |
| 4502759 | Summary: Duplicated Japanese honorifics for Signers in Audit Report |
| Fix: We now use the user list string in all cases in createSignatureRequestedAuditEvent(). This will be accompanied by a string change where the honorific character is removed from all audit event strings used in the function. | |
| 4503010 | Summary: Action GET /agreements/ID fails with 500 - Miscellaneous server error for a few agreements after September 17 due to an origin check. |
| Fix: The origin check has been removed. | |
| 4503107 | Summary: When a sharee with SEND and SIGN permissions switches to the sharer's account and initiates a workflow where the sharer is the first signer, the user is redirected to the POST_SIGN page instead of the ESIGN page. |
| Fix: The in-place check has been updated to ensure that sharee has SIGN permissions for the group from which the agreement was sent are being used. | |
| 4503112 | Summary: Auto-Cancellation of agreement - error AUTO_AUTHOR_FAIL due to an iText error. |
| Fix: iText has been removed where unrequited, resolving the error. | |
| 4503640 | Summary: Form filler is unable to submit the document. Server error is seen after user clicks on 'Submit' on XFA documents |
| Fix: The library that evaluates PDFs for XFA has been improved to properly identify and remove XFA. | |
| 4504309 | Summary: Unable to send Draft folder agreements via Advanced Account Sharing due to missing endpoint in the filter. |
| Fix: Added the URL /account/requestSignatures/authoring in allowListedEndPointsBasedOnSendPermissions in filter.xml | |
| 4504567 | Summary: Radio button values are being changed when agreements are generated via bulk send |
| Fix: Replaced the hashmap with linkedhashmap to maintain order of insertion when creating SiB child agreements | |
| 4504631 | Summary: Processing workflow error Error message: Unhandled Error due to unsupported characters in an iText file |
| Fix: iText has been updated. | |
| 4504822 | Summary: User Search is cleared if User list is taking too large, and a search is requested before a previous search is completed (such as the initial loading of users when the page is opened) |
| Fix: When data is received, we check if the requestID matches the most recent request. If it does, we process the response, if it doesn’t, we ignore it. | |
| 4504831 / 4507199 | Summary: Signed agreement provides an invalid PDF 1kb in size due to a malformed PDFFont object that does not specify the required subtype of the font object. |
| Fix: The PDF-generating library has been updated to better manage malformed objects and provide a more graceful result. | |
| 4506230 | Summary: Automatic Field recognition not working in Sandbox due to the annotation either being wrong or absent where we are looking for it. |
| Fix: We now seaarch each page and each annotation on that page to find the annotation of the form field to ensure we get the correct page. | |
| 4506959 | Summary: Post-Sign Landing Page is showing HTML encoded characters |
| Fix: Fixed source template. | |
| 4508950 | Summary: Fields that have a name containing an apostrophe throw an error in the new experience. |
| Fix: The field parsing code has been improved to manage apostrophes. | |
| 4509503 | Summary: Users are unable to sign documents through the Acrobat Sign application iOS due to a datafield being empty and throwing a null pointer exception |
| Fix: A null pointer check has been added to gracefully manage the circumstance. | |
| 4509713 | Summary: Setting "Allow all users to share library documents with multiple groups" is being auto enabled when trying to enable "Allow administrator to share library documents with multiple groups" from Global settings due to an incorrect value being passed. |
| Fix: The correct value is now being used. | |
| 4510812 | Summary: Aadhaar authentication in Workday is preventing signatures. |
| Fix: Aadhaar authentication support has bene added to Workday. | |
| 4512044 | Summary: Modern esign throws error if the field name has a special character |
| Fix: Field name parsing has been improved to gracefully manage special characters in field names. | |
| 4516231 | Summary: The wording in the Audit Report regarding the signing link "E-Signature hosted by (Sender name)" is thought to be too vague. |
| Fix: The string in the Audit Report has been updated to read "Signing link is created by (Sender name)". |
Production deployment: March 17, 2025
GovCloud deployment: March 20, 2025
Experience Changes
- New e-sign environment for OEM Partners - The new e-signing environment has been enabled for the Acrobat Sign OEM partners. This environment provides a superior signing environment for the recipients and includes the option to define a field layer that mobile customers can switch to, significantly improving the field-filling process.
Resolved Issues
| Issue | Description |
|---|---|
| 4501733 | Summary: Setting a custom email display value for a group does not apply to reminder and cancelation emails. |
| Fix: Reminder and Cancellation email templates updated to properly reflect the Display Email value. | |
| 4502251 | Summary: Acrobat Sign authentication fails when the sending account is HIPAA enabled, and the sender and recipient have userIDs on different Acrobat Sign shards resulting in an Invalid access token error. |
| Fix: The Acrobat Sign authentication method has been improved to properly manage recipients with userIDs on different shards. | |
| 4504338 | Summary: An unprocessed error is triggered when the first person signs an agreement, but the second recipient is delegated twice. |
| Fix: The delegation code has been rebuilt to ensure proper authority to the agreement is passed when chain delegating. | |
| 4504648 | Summary: Checkboxes added through the API and that are enabled by default may retain their "checked" status on the final agreement even if unchecked during the signature process. |
| Fix: The inheritance of the checkbox value has been updated to ensure that the new values after a recipient is done are properly stored and reflected in the resulting PDF. | |
| 4506085 | Summary: Error when copying large templates from sandbox to Production. Template created without fields due to timeouts in the process. |
| Fix: The time threshold has been extended for synching actions. | |
| 4507500 | Summary: Acrobat (DC Web) users cannot upload attachments when applying a signature due to a missing path in the upload function. |
| Fix: The path to allow Acrobat users access to the upload functionality has been included. | |
| 4508102 | Summary: The process of deleting pages from a combined agreement document can fail because an internal service can throw an exception when deleting page related objects such as bookmarks, structure, destinations which causes the entire operation of deleting a page from a PDF to fail. |
| Fix: The internal service has been improved to better manage bookmarks, and the like to properly format the PDF to the Acrobat Sign expected standard. | |
| 4508673 | Summary: When a signing reason is required, and a signature field is assigned to a non-signer role (e.g., Approver), if modern eSign is enabled, the user is redirected to the modern eSign page and is not given the option to enter the signing reason. |
| Fix: A check has been added for a requirement for signing reasons, and if present, the recipient defaults to the classic esign page. | |
| 4508674 | Summary: Signed agreements with badly formatted destinations cannot be downloaded. |
| Fix: The internal library has been patched to better manage poorly formatted bookmarks and destinations. | |
| 4508934 | Summary: In the Salesforce integration, the File Name is trimmed after "." in the Signed Pdf Email Notification |
| Fix: The string trimming function has been improved to identify strings after a period that are not extensions. | |
| 4509274 | Summary: In the MS Teams environment, if the sender is the first (or only) signer, the agreement is not opened in a new tab after sending due to an empty value being passed in API redirection. |
| Fix: Improved the APi redirection by passing the correct values when triggering the signature process, and opening the new tab. | |
| 4509485 | Summary: Deleting pages from a combined agreement document can fail because an internal service can throw an exception when deleting page-related objects such as bookmarks, structure, and destinations, causing the entire operation to fail. Users can be unable to download their agreement PDF with an error message: "The document is not yet available or will have no pages to view." |
| Fix: The internal service has been updated to wrap the deleting process in testing to better manage malformed PDFs. | |
| 4509562 | Summary: Large agreements could present an issue where only the first several pages of the agreement would print to the PDF when opening the agreement on the Manage page due to an older sdk bundle. |
| Fix: The sdk bundle has been updated, resolving the issue. | |
| 4509684 | Summary: When calling GET /agreements/{agreementId}/documents/{documentId}) from the REST API, an error is triggered: "The server cannot send the response in a format requested in the Accept header" due to an incorrect content-type. |
| Fix: The content-type value has been corrected. | |
| 4509712 | Summary: Only 100 groups are shown when trying to share templates with multiple groups. |
| Fix: The number of groups fetched from the API has been increased to 1000 | |
| 4509989 | Summary: If we have a Name field beside the Signature field on the Web form eSign page, after applying the signature, the Name field does not have the signer's name and it's not visible. |
| Fix: An additional function was added to check the name value in the Name field and compare it to the existing value. If it has changed the field is populated with the new value. | |
| 4510498 | Summary: Suppressing email notifications to recipients fails for Written signature agreements due to a lack of configurable settings to control it. |
| Fix: A new setting has bene added to explicitly manage this type of email distribution. | |
| 4511386 | Summary: When a signer with a digital signature selects the option to download and sign, the participation counter increments before the signature is applied. |
| Fix: The logic that updates the system has been improved to better reflect the current status of the agreement. | |
| 4511390 | Summary: Group administrators don't have the authority to fully establish a share with their group users. |
| Fix: The sharing function for group admins has been updated to correct the issue. | |
| 4511902 | Summary: The custom date tag is not working with the New experience when the display format includes quote marks (due to encoding). |
| Fix: Acrobat now decodes the value before saving it. | |
| 4517094 | Summary: The link to the Terms of Use is failing due to the page being moved to a new source URL. |
| Fix: Updated the code to properly fetch the current URL. |
