This document highlights the new features, experience changes, and resolved issues in the current release.
Not all features/changes are guaranteed to be enabled on the date of the release.
If you would like to be notified of release notes via email, please subscribe here >
Icons have been added to indicate when a Note or Reminder are attached to the transaction. Hover over the icon to get a quick view of important metadata associated with each agreement. Click on the icon to take action.
Advanced filtering has been added to the search feature to limit the returned data set by the searched object (e.g.: Notes)
The option to revert to the classic interface has been removed, and only the new user interface is to be supported going forward.
|4283949||Summary: PDFs created with ADA compliant fields do not translate to ADA compliant fields when processed through Adobe Sign.
|Fix: A new setting was introduced that preserves the Accessibility features of uploaded PDFs using a new tagging tree that includes a field appropriate type (e.g. span or link), a title derived from the field content, and an alternate text that matches the title. Tag strings are localized according to the agreement's locale. PDFs that do not have Accessibility features when uploaded will not be endowed with these features by the Adobe Sign process.|
|4295359/4323894||Summary: Some characters from the Lithuanian and German alphabet (č, ė, and ß) were not properly handled by one of the dependent libraries, causing the characters to be omitted in the printed signature string.
|Fix: The library was updated to properly handle the identified characters and render them appropriately in the signature string.|
|4304412||Summary: A private CSC provider experience was not properly inactivating the Authorize button after the OAuth authorization popup was closed, allowing users to click Authorize again, and creating a "Loading" loop that would not terminate despite the signature being captured.
|Fix: Updated the code to disable the Authorize action when the background screen becomes available and remains unavailable for a significant span of time while redirection takes place.|
|4308773||Summary: Signing on the iOS mobile application could result in an "AUTO_CANCELLED_CONVERSION_PROBLEM" after the recipient signature was completed due to offline sync events that cause queued requests to be sent multiple times.
|Fix: Server-side code has been added to evaluate if a successful conversion process has completed for the same participation ID when a conversion times out, allowing for graceful resolution of conflicts.
|4311477||Summary: Completed documents do not present field information to screen readers in a usable way.|
|Fix: A new setting was introduced that preserves the Accessibility features of uploaded PDFs using a new tagging tree that includes field annotations that are converted to readable XObjects in final processing.|
|4316462||Summary: Some agreements sent under the BioPharma settings were not being forced to reauthenticate when their authentication was managed by Active Directory Federation Service. This was dictated by how ADFS was configured, and if Forced Auth was configured to bypass the indication.|
|Fix: Code was added to require an ACR in combination with the ForceAuthn attribute, forcing the reauthentication process.|
|4317635||Summary: Documents with multiple signature/initial fields would experience a screen-roll back to the previous field when clicking into a subsequent signature/initial field.|
|Fix: Code updated to properly resolve the focus of the next field after applying content to any given field.|
|4319974||Summary: The Locale selector on the signing page was still visible when the signingurl is retrieved using GET /signingurl v6 REST API due to the API call falling back to the application value instead of the session value.
|Fix: The API call has been updated to retrieve the setting value from the session (API user) instead of the application|
|4320942||Summary: Agreements created with digital signatures and cloned fields could produce a signed document where the parent fields (of the cloned field array) could be editable.|
|Fix: Parent fields in cloned field arrays have been set to read-only.|
|4321067||Summary: Accounts with a configured Display_Email value were seeing the email of the originator in agreement emails (instead of the Display Email value).|
|Fix: The userID is now compared between the participant userID and the current userID to return the Display_Email value for the account in outbound emails (when the value is set to something other than the default value).|
|4321335||Summary: Some agreements would not permit CSC digital signatures when the agreement has been delegated multiple times.|
|Fix: Code has been added to the signature process to loop through the recipients and ensure that the signing phase is appropriate for delegated participation.|
||Summary: Transferred Web Forms do not trigger Webhooks for the new owner due to the ApiUserID failing to update.
|Fix: The code around transferring web forms has been updated to ensure the UserID of the web form is updated when the object is transferred.|
|4323013||Summary: Accounts with Limited document visibility enabled for web forms could trigger an error indicating "The document is not yet available" when creating a web form via API and then attempting to view it from the Manage page.|
|Fix: Code has been adjusted in a couple of settings involving web forms and limited document visibility to remove the conflict.|
||Summary: When modifying an agreement that has the sender as a signer that requires authentication, the system may not recognize the sender's session as being authenticated, prompting a server error.|
|Fix: Updated the Modify Agreement code to ensure the workflow checks the transaction properties to properly understand and enforce the sender's authentication requirements.|
|4324497||Summary: Users in accounts with UMG enabled may not see all pre-existing shared library templates from a (non-primary) group they have been added to when building custom workflows.
|Fix: The code involved with identifying all active groupIDs and their respective assets when building workflows has been improved.|
||Summary: Accounts that manage their users in the Adobe Admin Console were able to see the option to set a reminder on the Compose page when the default reminder was set by an admin.|
|Fix: The code has been updated to properly hide the reminder option when the default value is defined in the Admin UI.|
||Summary: Non-English languages did not properly filter returned data for Reports.
|Fix: The code was updated to leverage the environment locale as the filtering parameter instead of using the static English parameter.
||Summary: Transaction consumption reports were including non-billable agreements
|Fix: The reporting query was improved to filter out the non-billable transactions.|
||Summary: Authentication information was not persisting in reports for recipients in hybrid signing workflows.
|Fix: The code behind the hybrid workflows has been updated to ensure that authentication information is captured and persisted so that reporting returns the correct values.|
||Summary: The number of recipients reported (via the Reports tab) can change to one less when the Sender is one of the recipients and is replaced in the transaction due to the code misrepresenting the replaced signer as a "Replacee".
|Fix: The Replace signer code has been updated to properly identify replacing recipients as Signer roles.|
||Summary: Group-level admins can see the report data for users in the Default group when the "Only data from their own user group" setting is enabled.
|Fix: The reporting code for generating the report CSV has been updated to properly capture only the data pertaining to the requesting admin.|
||Summary: The Events and Event Summary were not including unverified (but signed) web forms as completed (signed) agreements
|Fix: The code that evaluates completed agreements has been updated to include signed and completed (but unverified) web forms.|
||Summary: When sending an agreement with the Sender as one of the recipients, and the Display Email setting set to a non-default value, the agreement can fail to send if the sender attempts to move back to the Compose page from the Authoring page.
|Fix: The workflow that governs navigating back to the Compose page has been updated to properly manage the Sender when their email value is masked by the Display Email value.|
||Summary: A duplicate Signed and Filed email can be sent to the same recipient if they are included multiple times in the signature cycle.
|Fix: The email distribution process has been improved to evaluate duplicate recipient email values and will only deliver one copy of the final email for any one transaction.|
||Summary: Adding a full HTML link to the Message field of an agreement could cause some email clients to convert that string into a clickable link. This functionality was not designed functionality, and subsequent code was added that prevented this effect, creating what appeared to be a bug in the agreement message field.
|Fix: A setting has been added to properly render a hyperlink in the email message. This setting is not accessible to customers and must be edited by support or the account success manager. The setting is enabled by default on enterprise and business tiers of service.|
||Summary: New code added last June caused some users which were in the CREATED state to be converted to an invalid email address, but the global email address directory maintained the correct email address link to the user. This caused agreements sent to the user to be affiliated with a user type that would prevent the agreements from being listed on their Manage page.
|Fix: Multiple code changes have been installed to prevent the issue from recurring, as well as to detect and warn about the conditions which can cause this type of problem. To include detecting the email address used for single-use pending users and automatically using the correct email address, preventing any new invalid users from being created when the other checks fail.
||Summary: Some document creation processes allowed for a file to be uploaded to Adobe Sign with multiple digital signature fields. These fields were rendered as blank fields on the final PDF.
|Fix: An internal library has been updated to better annotate converted documents, ensuring only one digital signature field is applied and throwing the appropriate error when multiple fields are found (the expected behavior).|
||Summary: As part of a user cleanup process, users in a Pending status that were in an account with a claimed domain could have been converted to a Created status, resulting in the consumption of user licenses.
|Fix: Users that were converted via the clean-up process have been returned to a Pending status. Code has been added to prevent Pending users in claimed domains from being converted to the Created status.|
||Summary: Signing a web form with only one name (one contiguous string) triggers a server error.
|Fix: Error handling has been applied to web forms that will manage the use case and supply a proper error message as appropriate.|