Adobe Acrobat Sign Release Notes - 2022

Search

Adobe Acrobat Sign Release Notes: 2022

Adobe Acrobat Sign: January 2022

Improved Functionality

  •  Improvements to Manage Page Usability - The Manage page has been updated to improve "at a glance" data exposure:

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)

  • Improved Agreement URL Security - URLs sent via email and that point to agreements/PDFs now have a configurable lifetime that expires the link (Default is 7 days; Maximum value is 90 days). Recipients that attempt to access an expired link trigger a pop-up dialogue that allows them to request a new email (with a fresh link) to be delivered to the recipient's email address. Redirection of the new email/link is not possible through this action.
    • This setting only applies to expiring the URL and does not impact the lifespan and viability of the agreement itself.
    • Agreements sent prior to the introduction of this feature are not impacted by this setting.

Full details on document URL expiration can be found here >

Document link expiration controls

  • Improved Agreement Sharing Security - Agreement sharing has additional controls to limit sharing to and from parties external to the account:
    • Control the number of times that an agreement can be shared with an external party.
      • Free tier: 2
      • Trial tiers: 5
      • Individual tier: 10
      • Small business tier: 10
      • Business tier: 20
      • Enterprise tier: 20
    • Control the ability of an external party to share the agreement.

More information on sharing individual agreements can be found here >

Note:

Agreement shares committed prior to the introduction of this feature aren't counted.

  • New Trust Service Providers – SPID (Italy) and MitID (Denmark) are the new Trust Service Providers from the Cloud Signature Consortium providing certificates to apply secure digital signatures that meet the highest standards and compliance requirements.

Experience Changes

  • The New Home and Manage Page Become the Standard Interface - Adobe Sign has retired the classic experiences for the Home and Manage pages, and all accounts have been transitioned to the modern experience.

The option to revert to the classic interface has been removed, and only the new user interface is to be supported going forward.

  • Quick access action buttons on the Manage page have been updated - As part of the usability update to add the Notes and Reminder icons to the Manage page, the quick actions have been redesigned to have a similar look and feel.
Hover over icon update

  • HIPAA Agreement Security - Accounts that have HIPAA settings enabled will treat all recipients of agreements as if they are unregistered users with no account affiliation. In practice, this means that recipients with a registered Adobe Sign userID will not see these agreements on their Manage page.
    • Users within the same account as the sender are the exception to the rule. All agreements sent to recipients in the same account are implicitly trusted, and the agreements are displayed on the Manage page, where they can be viewed and shared.
  • Improved Contrast for the Signature Field - The blue font under the signature line is being darkened to comply with the Accessibility AA standard (4.5:1) for contrast.
Signature chrome compared - Pervious vs NEw

Resolved Issues

Issue
 Description
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.
4322749/4329156
 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.
4323749
 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.
4325294
 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.
4325826
 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.
4326335
 Summary: Transaction consumption reports were including non-billable agreements
Fix: The reporting query was improved to filter out the non-billable transactions.
4326406
 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.
4326725
 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.
4327494
 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.
4327780
 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.
4328045
 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.
4328110
 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.
4328313
 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. 
4328950
 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.
4329688
 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).
4329804
 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.
4329949 Summary: Fields that are hidden in authoring and that contain validation errors can trigger an error that cannot be viewed, preventing sending the agreement.
Fix: Validation is no longer applied to
4331649
 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.
4334224 Summary: Individual field downloaded from the Manage page would display a file name containing the original format of the file in addition to the final .pdf extension.
Fix: The file naming process when producing the final downloadable PDF document was updated to remove the previous file extension.

Improved Functionality

  • Improved reporting charts and data export - The Reports interface has been updated, allowing for:
    • Preconfigured graphical reporting for:
      • Agreements: Eleven reports tracking agreement activity by the sender, group, and workflow.
      • Transaction consumption (Expected in a future release): Four reports specifically tracking the volume of created agreements.
      • Users (Expected in a future release): Six reports illustrate user/group creation, login activity, and unique senders per day.
    • Data export reporting: Data exporting allows the user to define the output of a report CSV file by selecting the source report type, applying filters, and selecting the individual columns to be included.
Advanced reporting - Agreement volume

  • Improved Authoring environment available at the account and group level - The in-application authoring environment has an optional new experience with a new look and feel designed to enhance ad hoc agreement authoring (up to two recipients). The new environment is currently only for the Send for Signature workflow and does not support Web forms, Send in Bulk, or library templates. Enhancements include:
    • Field placement that allows the author to select a field type and then click to place the field one or more times, allowing for much quicker placement of multiple fields of the same kind.
    • More explicit indications of the field content (e.g., signature field elements, date field formats).
    • Properties for a selected field are listed in the left rail for better visibility and editing.
    • Field height for subsequently placed fields automatically adopts the height of the last field to have modified the field size (of the same field type).
    • The font color, size, and style for subsequently placed fields automatically adopt the font properties of the last field to have the font properties modified (spans field types that allow font modification).
    • Easier default value editing by simply clicking into the field and typing the default value.
    • A dedicated Date field for capturing date values other than the Date of signing
    • A dedicated Numbers field including all of the properties and validations for formatted numbers
    • Text searching using Ctrl/Cmd - F
v4 Authoring environment

Note:

The improved authoring environment currently supports only:

  • Placing fields when sending an agreement (ad hoc authoring). Send in Bulk, Web Forms, and Template authoring are not yet supported.
  • Up to two recipients.
  • A limited number of fields (the most common):
    • Signature
    • Initials
    • Name (the recipient's name imported from the signature)
    • Email (the recipient's email as defined during the agreement composition)
    • Date of Signing (inserted by the system when the signature is applied)
    • Text
      • Number
      • Date
    • Checkbox
    • Radio Buttons

Currently unsupported elements:

  • Agreements with more than two recipients
  • Self Signing
  • Web forms
  • Send in Bulk
  • Library templates
  • Text tags
  • Conditional fields
  • Calculated fields
  • Regular expression validation
  • Define a recipient name at Send - Administrators at the account and group level can require that the recipient name be included with the recipient's email address during the agreement configuration by the sender. The included name value is imported to the signature panel when the recipient opens a signature field.
    • The recipient may not edit the configured name value in any case.
    • The sender of the agreement can edit the name values prior to the first signature being applied.
    • Senders can replace the current recipient, providing a name-value for the new recipient.
  • Required name-values also enforced for web form counter-signers - When the feature is enabled, newly created web forms will also require a name-value for any configured counter-signers.
Note:

This feature only applies to agreements and web forms created through the Acrobat Sign web application.

More information on requiring a recipient name during the agreement/web form configuration process can be found here >

Require name on Compose page

  • Export agreement and web form data in JSON - When exporting data from agreements or webforms via REST v6 API, developers now have the option to select JSON as the export format in addition to CSV.
JSON export in the swagger documentation

  • Customize the contact information for signing password support - Customize the contact information provided to recipients when a signing password is used for signer identification. The default experience embeds the email address of the sender. However, it may be more practical to redirect this type of support request to a centralized support team or a security contact that manages passwords. Customization can be configured at the Account and Group levels.
Custom password message controls

  • REMINDER_SENT webhook event - A new webhook event has been added that executes on REMINDER_SENT events Either by explicitly subscribing to the AGREEMENT_REMINDER_SENT event or subscribing to AGREEMENT_ALL. 
Agreement_Reminder_Sent event

Experience Changes

  • Adobe Sign is being rebranded to Adobe Acrobat Sign Solutions - The Adobe Sign branded interfaces and document references have been updated to Adobe Acrobat Sign Solutions (or Acrobat Sign).
    • This rebranding does not impact any features or functionality of the service (e.g., not the domain URL nor the email address for the service).
    • Integration packages will update the branding with their next package update.
Acrobat Rebranding 2022

Caution:

The signing certificate will be updated to the new Acrobat Sign branding in the June release.

This will not happen in the April release.

Signing certificate

More details on the rebranding can be found here >

  • Updated text for the customer disclosure acceptance - The text for the recipient when accepting the consumer disclosure has been updated to: I agree to the consumer disclosure and agree to do business electronically with <Company Name>
    • If a Company Name is not available, the First/Last Name of the sender is used.
    • If neither a Company Name nor a First/Last Name is available, the sender's email address is used.
  • Signer authentication modernization - The signer authentication screens have been improved to no longer block recipients that have third-party cookies disabled when authenticating with password or SMS authentication methods. The experience has also been modernized to be responsive to different platforms.

Resolved Issues

Issue
 Description
4293949 Summary: The message popup for canceling an invite and revoking access tokens is misaligned with the text.
Fix: the messages have been updated to properly align the text.
4301564 Summary:  Calculated fields containing an "if" clause that also use a field containing the now() function in their own calculation disappear after the signature has been applied. The signature is visible during the signing process. The server-side date values converted from the now() function aren't rendering properly, where the client-side values are. This results in an invalid date, which hides the field.
Fix:  The server-side evaluation has been enhanced to correctly convert and manage the numerical value of the date as passed from the now() function.
4320113 Summary: When authoring a form in Acrobat, Text fields with formatting set to not show decimal places will display the field value with decimals once the agreement is uploaded and sent for signature.
Fix: A setting has been added to explicitly manage the formatting of number fields authored in Acrobat. This setting is disabled by default. Customers that have issues with number formatting when using forms created in Acrobat should contact the Support team and request to enable number field formatting for Acroforms.
4322775 Summary: IP addresses would not be collected and referenced on audit reports due to a setting being configured for the wrong scope.
Fix: The setting scope has been adjusted to the proper value.
4325183 Summary: Allowing the user session to time out when the new Reports page is loaded results in a general failure to refresh the page.
Fix: Interaction with the page after time out redirects to the login page.
4326123 Summary: When creating a new userID with APIs, some users would not be able to log in with the new credentials due to internal systems not communicating correctly.
Fix: A new setting has been added to manage user profiles between Adobe systems. The setting is enabled for all shards/accounts.
4326126 Summary: In the Korean locale, the name value on the signed document is broken in the participant stamp due to the encoding font for the Korean language returning incorrect glyphs.
Fix: The mapping library has been updated to include the encoding type to properly render the Korean glyphs.
4327886 Summary: When a user in an individual account is merged into a multi-license account, the user can retain admin rights.
Fix: Code has been added to strip admin rights from users that are migrated into a different account.
4328663 Summary: Customer accounts that have SAML set to Mandatory or SAML_ACTIVATE_PENDING_USERS = true can not Inactivate users using the bulk edit feature in the Acrobat Sign system as the userIDs reactivate immediately after the update.
Fix: Additional code has been added to ensure that only "Created" users can be immediately activated.
4329111 Summary: Custom formula validations do not work with Text Tags due to a task worker not loading properly.
Fix: The code has been updated to properly load the task worker.
4331101 Summary: Signers with a profile in the Acrobat Sign system cannot properly update their signature in a Stamp field when some other signature type field edits the signature string due to the Stamp signature field always pulling the name string from the user's profile.
Fix: Stamp signature strings are no longer tied to the user profile and update as all other fields do.
4331119/4331631/4334671 Summary:  Country codes missing from the phone authentication modal for Botswana, Bermuda, and Sudan.
Fix: The country codes for Botswana, Bermuda, and Sudan have been added.
4331146 Summary: REST v6 GET Agreements > displayUserSetMemberInfos is blank for some drafts when workflows are designed with more potential recipients than are utilized due to email values being required.
Fix: Code has been added to handle an empty email value.
4331149 Summary: Notarize transactions do not register when the transaction type is set to a default value of -1 in backend settings for an annual limit. However, annual limits do not apply if a transaction is Notarize managed.
Fix: We now ignore the annual limit for the Notarize managed transaction type and display it on Send settings page.
4332202 Summary: Privacy admins can be prompted with 'Some miscellaneous error as occurred when searching for agreements from recently migrated users.
Fix: Error checking has been added to capture and manage events where values are missing for migrated users.
4332303 Summary: User accounts can be made with uppercase characters in the email address that persist in the user database.
Fix: Values are now returned in lowercase characters in all cases.
4333575 Summary: Identity Verification Methods defined in Workflow (PHONE and ADOBE_SIGN) are not returned in REST v5 or v6 GET /workflows/{workflowId}
Fix: The missing Identity Verification Methods were added into JSON schemas
4333769 Summary: Users that created agreements or webforms in a group do not have access to edit that agreement/webform if they are removed from the group.
Fix: Code as been improved to ensure that userIDs that create an agreement/webform retain the edit ability while ensuring the original groupID is retained.
4333774 Summary: Multi-file agreements signed with a digital signature would not return a name-value when GET /agreements/{agreementID}/documents were called due to a null value in the document version reference.
Fix: Agreements containing a digital signature correctly contain a name property. For agreements created from multiple documents, the API will still return a single document for digitally signed agreements, and that document will now have the name listed as "multidoc.pdf".
4334814 Summary: Currency fields assigned to "Anyone" that completed the signature process without being updated would be removed from the final document due to a null value in the field causing the field to be removed.
Fix: A check has been added to manage a null value in a Currency field.
4335410/4335914 Summary: Some single-use pending users were adopting an accountId that caused them to appear as users in the account.
Fix: Database scripts were updated to exclude single-use pending users from these lists.
4335436 Summary: The SG1 shard cannot sync the production and sandbox environments due to an orchestrator failing to connect.
Fix: The orchestrator service was properly connected to the shard.
4335442 Summary: Error Code "MODIFYING_IMMUTABLE_FIELDS" is not listed in the swagger documentation for PUT /users/{userId} in REST v6
Fix: The swagger documentation has been updated and the error message improved.
4335782 Summary: when BioPharma settings are enabled, the user type signature update does not get synchronized with the other fields (such as the signer name field). this is caused by the "Signing Reason" component not catching the name change event that is broadcast when the signature panel is closed.
Fix: The "Signing Reason" component has been updated to track the before and after name changes properly.
4336003 Summary: Clicking the Create button when generating a WebForm with two or more participants and KBA enabled by default triggers an error. This is due to a null pointer exception occurring on form creation because the second participant is not defined on form creation
Fix: Added null pointer checks to resolve any exceptions in the java class.
4336018 Summary: When an agreement is implicitly delegated the API results are inconsistent with the experience of explicit delegations due to the implicit delegation event missing some information.
Fix: Implicit delegation flows have been improved to act the same as an explicit delegation.
4336037 Summary: Calling GET /signingUrls after retrieving the agreement ID can generate an "AGREEMENT_NOT_SIGNABLE" status that can be inferred to indicate the agreement is in a terminal state.
Fix: The conditions that trigger the status in these cases now trigger an "AGREEMENT_NOT_EXPOSED" status only.
4336076 Summary: In the signing experience, the "Next field required" text and button do not have sufficient contrast.
Fix: The button and text have been altered to provide a 4.5:1 contrast.
4336077 Summary: The participation stamp is not visible on the Signed PDF if the participant is marked as a recipient group. The indexing method finds the correct part for this stamp. But when there is a recipient group, this will give a random part from the group, which may not be the current signer. In such cases, the value is sometimes assigned as null and the signer part fails.
Fix: Modified the indexing method to return the correct signer part of the participation group.
4337254 Summary: Recipients are unable to complete the signing process when signing digitally via cloud service provider "BJCA" due to an invalid font being used to render some Chinese glyphs.
Fix: Updates to the rendering library now allow proper rendering of the glyphs, allowing the signing process to complete.
4337616 Summary: Sending agreement to an INACTIVE user creates a single-use pending user, who cannot sign with Adobe Sign authentication.
Fix: Inactive users in a claimed domain no longer generate a single-use pending user.
4337679 Summary: During the cleanup of users after they sign, biometric signatures with a user id are deleted. This resulted in a participation signature that was just a Hibernate proxy that if called would result in errors. This could happen during agreement event fetching since it looks at the scribble data.
Fix: Added code to check if there is really a scribble before reading any values from it.  Updated the clean-up code to null out the signature content.
4337734 Summary: Country ISO code for Curacao (CW) is rejected by the REST v6 API when used for phone authentication.
Fix: The code for Curacao has been added to the method and is now available.
4337948 Summary: Very localized data corruption cause the possibility for sending an agreement to an Active user yet created a single-use pending user.
Fix: The database was manually corrected.
4338735 Summary: The "コードを送信" (Send Code) button has a line break in the text in Japanese ​UI
Fix: The button has been reconfigured to only allow one line.
4340100 Summary: "Configured settings require that documents must be password protected" may trigger in UMG enabled accounts, even though "Signed Document Password Protection" is set to "Allow senders to password protect signed documents" for the active group on send page due to user settings overriding the group level settings.
Fix: For users in UMG enabled accounts the group level setting will be selected over the user-level settings.
4340558 Summary: When there is prefill drop-down field and digital signature present, the drop-down is still editable after sending the agreement.
Fix: Updated the dropdown field to read-only after filling the value
4340659 Summary: If the wrong email address for a participant is used, but it is very similar to the correct one (eg user@email.com is correct but customer enters user@email.com.us), and after that the sender tries to share agreement with the user, entering the correct email address will cause the error: "One or more sharees is already a participant and cannot be shared with" due to an inaccurate method for comparing email values.
Fix: A more accurate method is in place to better manage user identities in these cases.
4341111 Summary: The Send in Bulk function does not properly read the group settings when UMG is enabled, and instead defaults to the primary group settings in all cases.
Fix: The code has been updated to read the proper (selected) group settings for the Send in Bulk workflow.
4341187 Summary: Non-signer participants (eg: Approvers) that sign with only a stamp import the name value from their profile instead of using the name-value entered at the time of signing. this is reflected on the Manage page when reviewing the completed agreement.
Fix: The manage page will reflect the value entered at the time of signing.
4341807 Summary: The DISPLAY_EMAIL back-end value is being returned in response to /signingUrls.
Fix: The function to capture the email of a participant has been updated to take this context into account.
4341809 Summary: A "Click to change" popup is evident when a recipient hovers over their signature and the signer name value is applied via API
Fix: The signature code has been updated to remove this tooltip.
4341947 Summary: There is no retryAfter in the response body for some API calls when they trip the throttling threshold.
Fix: the managing method has been updated to include the retryAfter response.
4343205 Summary: Agreements sent with a custom email template and a link expiration set to 60 return a 500 error when the Send new Link button is used.
Fix: The link expiration function in conjunction with custom email templates has been modified to eliminate the error.
4343636 Summary: Agreements sent using a document containing the digital signature objects of other signature services can cause an unhandled error due to a null pointer exception.
Fix: The associated code has been updated to properly resolve the pointer issue.
4343696 Summary: After a participant uploads a document by clicking on Upload to Submit, an additional document version is created without a participation value. Since it doesn't have participation assigned this causes the agreement auto-cancellation (project timeout) approx. one hour after its creation.
Fix: We no longer create a document without participation.
4346378 Summary: Users cannot use the Library template they created after they are removed from that group.
Fix: Modified the library method to ensure we don't filter the group for library documents if the user is the originator of the library template.

Access to knowledge-based authentication for participant defined recipients on web forms

Customers that build web forms that allow for multiple external participants can now use the knowledge-based authentication method for the additional participants.

KBA access for additional recipients in web forms

Resolved Issues

Issue
 Description
4354725 Summary: Agreements can not be created via custom workflows when Required recipient name is enabled.
Fix: Name validation has been disabled for workflows, meaning that the required name value is not checked/enforced when the agreement is being composed.

Improved Functionality

  • Improved Digital Identity verification - Acrobat Sign's identity gateway connects to third-party authentication and identity verification services using the standard OpenID Connect (OIDC) authentication protocol. Customers can select from a wide array of authentication services and leverage the type of identity verification that best suits their demands.
    • Identity verification services include:
      • Video Identity Verification services
      • ID document identification
      • Knowledge-based authentication services
    • Identity information is optionally stored on the Signer Identity Report.
    • Identity verification is priced separately and consumed per the vendor policy.
    • Authentication transactions are procured and billed directly from the IDP.

Review the digital identity documentation >

Digital Identity Gateway

  • New webhooks
    • AGREEMENT_EXPIRATION_UPDATED (API only) - The AGREEMENT_EXPIRATION_UPDATED has been created for the event when an agreement’s expiration time is updated. AGREEMENT_EXPIRATION_UPDATED can only be subscribed to via the POST /webhooks API call.
    • AGREEMENT_SIGNER_NAME_CHANGED_BY_SIGNER - The AGREEMENT_SIGNER_NAME_CHANGED_BY_SIGNER webhook triggers when a recipient changes the pre-populated name value when they are signing their agreement. Name values can be prepopulated through the API or through the Require recipient name when sending feature.

Review the webhook documentation >

  • Updates to the custom workflow designer  - Updates to the custom workflow designer include:
    •  Users in Multiple Group awareness. Accounts that have UMG enabled allow:
      • Group administrators can assign workflows to any group that they are an administrator of (not only their primary group).
      • Group administrators can edit any workflow assigned to any group they are an administrator of.
    • An update to the workflow scope control interface that defines which users can access the workflow.
      • The text label indicating which group/users the workflow is enabled for has been changed from Activate for to Who can use this workflow.
      • The text label for the option to include all groups/users in the account has been updated from All groups to Any user in my organization.
      • The array of radio buttons used to select an individual group has been changed to a single-select drop-down menu with the text label Selected Group.

Review the custom workflow designer documentation >

Custom workflow designer group selector

  • Improvements to the new authoring environment - The new authoring environment introduced in April 2022 has been updated to include:
    • Support for up to 25 recipients.
    • New fields:
      • Dropdown (single-select)
      • Hyperlinks
    • New Acrobat web accounts and free Acrobat users enable these features automatically.
    • Enterprise accounts in the Acrobat Sign solution can enable the new authoring experience in Account Settings > Global Settings

Review the documentation for the new authoring environment >

  • Option to disable the email tracking pixel - Enterprise tier accounts can request the support team to disable the tracking pixel embedded in the recipient "Review and Sign" email templates.
    • Disabling the email pixel changes the trigger for the "Viewed" event:
      • When the pixel is enabled, the "Viewed" event triggers when the email is opened.
      • When the pixel is disabled, the "Viewed" event triggers when the agreement is opened (via the signing link).
    • New accounts of all service levels created after the June 2022 date will have the pixel disabled by default.

Review the tracking pixel documentation >

  • Disable hyperlinks embedded in signatures and initials - Enterprise tier accounts can request the support team to disable the embedded hyperlinks in signature and initial field objects (which open the transaction verification page).
    • All accounts created after the June 2022 release have this linking disabled automatically.
      • Accounts that exist before the June 2022 release will continue to see the legacy functionality.
    • Disabling the hyperlinks is not retroactive to agreements completed before adjusting the setting.
    • Once disabled, the embedded links can not be reenabled.

Review the transaction verification documentation >

Signature and initial hyperlinks to verification page

  • Expanded the Audit Report events - The audit report has been improved to include several events that were previously only reflected on the activity log or embedded in report files. Improvements include:

The option to allow the audit report to adopt the timezone offset from the account/group/user setting can be enabled at the account (and group) level by navigating to Account Settings > Global Settings > Set a default time zone to use for agreements created by users in this account

Configure the audit report to adopt the configured timezone offset

Time zone values can be set at the account, group, and user level, and the "lowest" level object takes precedence.

  • User settings override group settings.
  • Group settings override account settings.

If the setting is enabled and an individual user adjusts their timezone to be different from the account level setting, the user's audit reports will reflect the timezone offset as defined by the user profile, not the account.

Review the default time zone documentation >

When sending an agreement to a user with a known name value in the Acrobat Sign system (typically someone in your own account), the name value in the user's profile is automatically inserted in the signature process.

If the account allows users of this nature to change their name value when signing, that change is logged to the audit report, providing the initial name value and the updated value.  All subsequent iterations of the recipient's name in the audit report will reflect the adjusted value.

Log name changes

Standard electronic signatures now include the reason provided by recipients when signing, declining, or canceling an agreement.

Display reasons

Sharing an individual agreement produces a record in the audit report. This record now contains the participant the agreement was shared by, in addition to the party the agreement was shared with.

Log sharing events

Sharing an agreement after it has entered a terminal state will not update the audit report with new records, but the agreement Activity log does continue to track sharing activity.

Activity log of a share after agreement completion

Audit records are now presented for each time a recipient requests a new document after a link has expired.

Review the link expiration documentation >

New link request for expired link

Note:

Keep in mind that audit reports become immutable after the agreement reaches a terminal status. Reminder and share events executed after the agreement is terminal will not be reflected in the audit report.

  • Allow or disallow the sharing of individual agreements with internal/external parties - The ability for users to share an individual agreement with another party can be limited to allow/disallow sharing based on the internal/external status of the party being shared to.
    • Internal users are defined as users within the same Acrobat Sign account as the sender of the agreement.
    • External users are defined as all users that are not members of the same Acrobat Sign account as the agreement sender.

Review the agreement sharing documentation >

Agreement sharing controls

  • Access to knowledge-based authentication for participant-defined recipients on web forms - Customers that build web forms that allow for multiple external participants can now use the knowledge-based authentication method for the additional participants.

Review the web form documentation >

KBA access for additional recipients in web forms

Experience Changes

  • Web Forms no longer require third-party cookies to be enabled for signers -  Accounts that use web forms no longer need to be concerned if their signers have third-party cookies enabled before applying their signature. Web forms now support cookieless signature activity.
  • Expired signing links are limited to ten requests per hour - When a signing URL expires, the recipient can request a new URL up to ten times in a 60-minute time window.
    • A new URL will not be sent after the tenth request in the same 60-minute window.
    • The ten signature requests exist in a rolling time window, meaning that each request has a 60-minute timer.

Review the link expiration documentation >

  • Updated External Archive interface - The external archive interface has been updated to challenge the administrator to enter the email address twice (to ensure the correct email is configured) and store the email as a clickable address object instead of a text string. All interfaces for the automatic archive feature are being updated (Global Settings at the account/group level and the External Archive tab).

Review the external archive documentation >

Updated external archive interface

  • Update to the Required Recipient Name feature - The feature to require a recipient name when composing a new agreement now preserves that setting at the agreement level, ensuring that the setting value is enforced, even if the account/group level setting is changed.

Review the documentation for requiring a recipient name when sending agreements >  

  • Updates to the Notarize integration - Improvements continue for the Notarize integration:
    • The agreement expiration time is being shared with Notarize and will be honored by Notarize as part of their scheduling feature.
    • The Notarize API key is now validated before the agreement is sent for notarization. Send/update is blocked and an error is thrown if:
      • the account is an expired trial.
      • the Notarize account mapping to the API key is deactivated
      • the Notarize API key is invalid
      • the Notarize API key has been disabled

Review the Notarize documentation >

  • Update to the expiration date label in emails - The text identifying the expiration date in recipient emails has been updated to clarify that agreements can be signed until the expiration date. Due on {DATE} has been updated to Due by {DATE} :
Update to the expiration date label

  • Improved automatic form field detection (limited deployment) - Automatic form field detection has been improved to more accurately identify the type, size, number, and location of form fields to be placed.
    • Only deployed on the NA4 environment after the June 2022 release. To be deployed on other environments in future releases.

Review the documentation of automatic form field detection >

Registration page

Resolved Issues

Issue
 Description
4326356  Summary:   PDF forms created in InDesign specify a value of "Off" for unchecked checkbox fields, which caused issues when the fields are editable by recipients.
Fix: Ignore the default value of "Off" for unchecked checkbox fields when importing PDF forms.
4329479 Summary:   Government ID Selfie capture fails on iOS15 with a "Face not detected" error.
Fix: The GovernmentID package has been updated with improved code to address this error.
4330744 Summary:  Account administrators are unable to disable Bio-Pharma settings due to a mismatch of the settingID and the home shard for the account.
Fix: Database updated to correct the settings mismatch.
4332322 Summary: The number of consumed KBA transactions could be incorrectly inflated due to poor logic controls when assessing KBA usage
Fix: The logic has been corrected to reflect the correct usage.
4333689 Summary:  Web form creators are unable to delegate countersignature for web forms from the modern manage page due to the API not providing a signable reply when the signature is attempted.
Fix: Updates to the API to provide the correct reply to the signer when invoked from the Manage page.
4333769 Summary:  Users are unable to edit web forms (and agreements) once their Group is changed.
Fix: Edited the permissions to get and edit agreements for the originator when they have an inactive membership to the web form/agreement ID.
4336080 Summary:  Signatures using two-byte characters could result in part of the signing date being truncated in the final signature stamp.
Fix: Updated the field parameters to allow the space for the full signature stamp.
4338126 Summary:  The Cancel Reminder option is not visible on the modern Manage page for reminders created on the legacy Manage page due to a required parameter not being part of the legacy object definition.
Fix: Code has been added to bridge the gap between the legacy object and the modern functionality.
4338227 Summary:  Dropdown fields defined with a default value containing a single quote character do not register as a valid option and are not selectable.
Fix: Code has been added to properly manage a default value containing a single quote.
4339667 Summary:  Creators are unable to modify an in-flight webform created from a template containing prefill fields.
Fix: Code has been updated to not check for prefill fields when modifying an active web form.
4341476 Summary:   The expiration date is missing when Agreement creation is completed through the JASON payload due to the rendering code pulling the incorrect value from the agreement properties table.
Fix: Corrected the code to retrieve the correct value and publish that as the expiration date.
4343048 Summary: Cookie consent selections are not saved for the Sandbox and Government environments. Users must consent each time they authenticate
Fix: Cookie consent selections and updates are being saved for the user.
4343954 Summary:  Uploading a document with a Unicode title that was subsequently imported into the agreement name caused the name to be added twice, which could make the string too long for the PDF conversion function to properly create the PDF., resulting in a PDF that would not convert.
Fix: The code has been updated to use the original title string instead of creating a new one during the conversion
4344568 Summary:  Some of the Group level Email Settings do not save when updated to override the account-level settings due to a failure to check the override value for those parameters.
Fix: Code has been updated to properly check the override value when group level settings are updated.
4345297 Summary:  Cloud Signatures can fail with an "Error occurred while completing the digital signature" error due to the signature field being placed with a negative coordinate.
Fix: Code has been added to ensure the field location is calculated properly with corrected coordinates.
4345380 Summary: Recipients still have the UI option to decline to sign even when the "decline to sign" option is disabled.
Fix: the code has been updated to properly suppress the Decline to sign options in the UI when recipients first load the agreement page.
4346217 Summary:  Exports could fail with an exception reported due to executor threads not updating the tenantIDs from previous use, causing attempts to execute tasks on the improper tenants.
Fix: The tenantIDs are now properly updated in the executor threads when they are inherited from the scheduler.
4346736 Summary:  Calculated fields involving the now() function are not working when copied using the API because copied field calculated expressions retain escape characters all the way to the document data XML.
Fix: Calculated expressions are cleaned before saving to document data XML.
4347673 Summary:  Group administrators could retain visibility of users in groups where they have previously created reports, and subsequently moved out of that group as a result of the group filter not updating properly.
Fix: Group filtering has been updated to ensure that filters update when the user admin changes group authority.
4348040 Summary:  Customers adding some image files via attachment fields would not report the proper mime type
Fix: Code has been improved to accommodate the full range of options in the appropriate class.
4349061 Summary:  Library documents are not always sorted in alphabetical order due to combined lists not sorting after combination.
Fix: The combined lists are now sorted alphabetically (numbers before alpha characters and case insensitive).
4349494 Summary:  Fields manually placed over the location where an automatically detected field would have been placed retain the properties of the automatically detected field.
Fix: Field properties for automatically detected fields are not stored if they are not placed.
4349978 Summary: Government ID authentication could fail with a "No face detected" error when capturing a selfie..
Fix: The package for the Government ID function has been updated to resolve the root cause.
4350723 Summary:  TransactionID fields are not available for customized email templates
Fix: TransactionID fields have been added to the customizable email templates.
4351205 Summary: Signers could receive a ‘This agreement cannot be e-signed’  error while signing an agreement due to an internal ID being overwritten in select situations.
Fix: Newly created agreements commit the ID to the DB with the initial save of the agreement removing the need to update the ID at any time.
4351322 Summary:  Duplicate versions of a workflow can be saved due to the "Save" button not being disabled immediatly after saving a workflow.
Fix: The Save button is immediatly disabled upon saving a workflow, preventing the duplicate entry.
4352684 Summary:   The API call "PUT /widgets/{widgetId}/formFields" is not working for the SIGNATURE field
Fix: Repaired the code and verified it works as expected.
4353289 Summary:  Hungarian translation for 'Transaction Number XYZ is valid' is incorrect.
Fix: Translation as been corrected.
4353564/4361472 Summary: The ability to create new accounts via POST/account was broken due to upstream settings updates.
Fix: The POST/account API has been adjusted to account for the upstream setting.
4354088 Summary:  Unable to delete a field in the new Authoring experience using the "Delete" key.
Fix: Improved the code to allow for deleting with the delete key.
4354730 Summary:  Prefill fields used as conditionals in the show/hide values of fields for subsequent recipients may not be visible when the recipient receives the agreement.
Fix: Code for the field value tables has been improved to better include the properties of prefill fields.
4355002 Summary: The new authoring environment was not allowing Notary and Electronic Seal roles.
Fix: The roles have been added to the roles options.
4355003 Summary: Written workflows can break the New Link delivery when a link expires between downloading the signable document and the subsequent upload of the signed document.
Fix: The code has been improved to manage this situation.
4357224 Summary:  Custom Format on Date field doesn't import from PDF
Fix: Field import code updated to ensure correct format validation transfers from uploaded PDF.
4357710 Summary:  Radio buttons with conditional visibility can fail to display.
Fix: Conditional visibility code has been tightened to ensure accurate display when conditions are met.
4357908 Summary:  Transactions that use one premium authentication method when originally sent and later transfer that authentication method to a different premium method can have both authentication methods deducted even though only one is actually used
Fix:  Code has been improved to account for authentication method transfer to not count the original method when the agreement is updated.
4358003 Summary:  User migration can lock when classic migration is triggered, and then advanced migration is also triggered.
Fix: Code has been added to manage a migration in progress when a new migration is executed.
4358968 Summary:  New reporting does not properly report all legacy workflows if they are deactivated.
Fix: Reporting scopes have been improved to account for disabled and hidden workflows.
4361469 Summary:  Using the Switch Account option to send an agreement on behalf of another does not allow authoring, instead users are routed to the Manage page due to the new authoring environment not being part of the filter table for shared access.
Fix: Added new authoring to the filter for shared access.

Improved Functionality

  • Require recipient name at delegation  -  The feature to require the recipient name when sending a new agreement (released in April 2022) has been improved to allow entering a recipient name at the time of delegation as well. Users can enter the recipient name when they click Delegate signing to another option on the signing page or using the delegate link in the email.

Review the Require recipient name documentation >

Delegation with required name values

Note:

The improvement of the delegation process is achieved by updating the delegation API to use the v6 REST endpoint /delegatedParticipantSets.

Customers should see no impact beyond enforcing the required name values configuration during delegation. If any delegation issues are noticed, contact Support.

  • Form field tooltips support up to 4096 characters - The customizable tooltip option for all form fields has increased the number of characters allowed from 256 to 4096.
Improved capacity for tooltip values

  • Improved searching for Team/Small Business service packages - The search functionality used to find agreements has been improved to support more complex string queries using special syntax. The upgraded search feature is scheduled to be deployed by tier of service over the second half of 2022.
    • This release updates only the Team/Small business tier of service.
    • The documentation for the improved search functionality is available in the online help documentation. A link to the documentation is provided in the application by clicking the information icon next to the search field:
Information icon next to search field

Experience Changes

  • Legal notices consolidated into one menu item on the e-sign page - The legal notifications on the recipient e-signing page have been collected into one Legal Notices menu item in the Options menu. The collected notices are:
    • Terms of Use
    • Privacy Policy
    • Cookie preferences
    • Copyright and Trademark notices
    • Third-party notices
Legal notices

  • Clickable message links on the e-sign and Manage page  - Enterprise tier accounts that enable clickable links in their email templates will now see those links as clickable on the recipient's e-sign page as well as in the  Manage page view of the agreement.

Review the clickable links documentation >

Clickable links in the message field on the Manage page view of an agreement

  • +383 (Kosovo) country code added to SMS authentication - Kosovo (+383) has been added to the list of country codes for phone authentication.
Kosovo country code

  • Signature fields have updated their tooltips for better accessibility - Each of the signature field types has improved the tooltip to better identify the signature content required by the recipient.
Signature field tooltips

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.

  • Include Reminders in Audit Report events - Administrators now have the option to include Reminders in their audit reports. The option can be enabled at the account (and group) level by navigating to Account Settings > Global Settings > Audit Report
Configure reminders to be reported in the audit report.

When enabled, a record of every reminder sent is logged on the audit report (up to a maximum of 250 reminder events).

Reminders reported in the audit report.

Resolved Issues

Issue
 Description
4331709 Summary:  A MISC_SERVER_ERROR is generated when replacing a recipient with a userID that is auto-delegating their agreements to a user that is not an active userID in the system.
Fix: Code has been improved to successfully identify and create the auto-delegate userID as a single-use user for the purpose of the transaction.
4345707 Summary:   Ambiguous tooltip information for signature/initial/stamp fields is causing confusion when agreements are consumed using screen readers.
Fix: The tooltips have been updated to better indicate the type of content required (initials/signature stamp). The localization of those tooltips has been updated and verified on common screen readers.
4346795 Summary:  An uninformative error message is delivered to the user when authentication is denied based on IP address restrictions.
Fix: The error message has been improved to indicate the failure to authentication is predicated on the account security policy.
4348930 Summary: Dynamic values used in Payment fields do not include Prefill values in their calculations.
Fix: The code supporting calculating field values for payment fields has been corrected to properly access and import values from prefilled fields.
4353603 Summary: Images fields disabled by conditional logic based on other fields still allow an image to be uploaded.
Fix: The code that disabled field access under field condition logic has been corrected to ensure the image field cannot be accessed
4354667 Summary: When two attachment fields are available on the same page, the application focus does not shift to the next field after completing the first attachment, and enters a loop.
Fix: The field navigation and setFocus code has been corrected to properly navigate the focus to the next field.
4354854 Summary: Pasted email addresses when verifying a web form signature do not properly activate the Click to Sign button.
Fix: The OnPaste function has been improved to better accommodate this action in a web form submission.
4354992 Summary: Reminder and Delegation emails could trigger a bounce from anti-spam filters based on a mismatch of the envelope and header values for the sender due to name-value management being inconsistent.
Fix: The From header in email is now consistently formatted as "firstname lastname <adobesign@adobesign.com>" when the first and last name are available.
4355581 Summary: Account scoped report charts could list the reports showing their reportID if there were null values in the report properties.
Fix: The reporting API for the new report system has been updated to better manage reports with null values
4359189 Summary: Email templates can display &amp; instead of & when applying the company name.
Fix: The code to properly format the company name has been corrected.
4359920 Summary: The country code for Kosova (+383) is not available when configuring SMS authentication
Fix: Added (+383) to the SMS list of available country codes.
4360266 Summary: When a user is changed to Inactive status, and then moved to another group, the CSV generated when exporting a user list does not show the current group name for the inactive user.
Fix: A new method for retrieving user data to export without checking user status has been implemented.
4360311 Summary: Email templates can display &amp; instead of & when the sender's name includes an &.
Fix: The code to properly format the sender's name has been corrected.
4361282 Summary: Requesting a new link (after the previous link has expired) on a Reminder email template would cause all participants to be sent a reminder email.
Fix: Corrected the reminder code to only send the reminder to the recipient that requested it.
4361868 Summary: Calculated date values in non-English locales can report "Server error. There was a field which had an invalid value"
Fix: Improved the translation of date formats for localized dates with regards to calculated fields and conditional statements.
4365756 Summary: Due to a conflict in how settings are inherited through legacy settings, user profile pages were presented as blank to administrators when editing.
Fix: Understanding and accessing the proper inherited settings has been updated to eliminate the conflict and provide the correct values.
4366715 Summary: Agreements built from two files can create broken records in the structure tree that result in a failed creation process (due to the process used to combine the structure trees).
Fix: The library used to combine documents has been updated to better manage the structured tree when multiple files are included in one agreement.

Previous Releases

RELEASE NOTES: 2022

RELEASE NOTES: 2021

RELEASE NOTES: 2020

RELEASE NOTES: 2019

RELEASE NOTES: 2018

RELEASE NOTES: 2017

RELEASE NOTES: 2016

RELEASE NOTES: 2015

RELEASE NOTES: 2014

Adobe logo

Sign in to your account

Quick links

View all your plans Manage your plans

Legal Notices    |    Online Privacy Policy