Adobe Acrobat Sign Release Notes: 2024
Production deployment: January 23, 2024
GovCloud deployment: January 25, 2024
Improved Functionality
- Error report for users provisioned through the Adobe Admin Console - Accounts that users through the Adobe Admin Console can review a report containing all users who have been provisioned but have not converted to an active status. Resolution statuses identify what the admin (or user) must do next to have the user activated in the Acrobat Sign service.
Experience Changes
- Disable social logins for Bio-Pharma signers - There is a recipient-facing change for agreements sent from a group that enables any of the Enforce Identity Authentication options and uses Acrobat Sign authentication. The updated experience automatically removes all options to use a socially linked authentication partner (e.g., Google, Facebook, and Apple). Recipients must authenticate directly through the Adobe identity management system.
- Data exports improved to return data based on recipient order - The contents of data exports now include and leverage the recipient order:
- Recipient order is a new selectable column when creating data exports.
- Recipients are ordered according to the recipient order on the export by default, even when the customer does not select that column to view.
- Adobe Acrobat Sign for Government improved Just in Time user provisioning - New users in a GovCloud organization can now use the account's vanity URL to authenticate to the Acrobat Sign for Government environment through their configured Identity Provider. Doing so triggers user creation in the Acrobat Sign system for new users and authenticates the user into the service for returning users. New user creation has been improved by implementing a built-in waiting mechanism that removed the requirement for the user to "Try again" if the system times out.
API and Webhooks
Resolved Issues
Issue | Description |
---|---|
4442628 |
Summary: Data exports don't reflect the same recipient order as the audit report in terms of the recipient order assigned on the agreement. |
Fix: The sorting order for Reports has been updated to always sort the data by recipient order as designed on the agreement | |
4452261 |
Summary: Apostrophes show as HTML the escape character ' in the Audit Report. |
Fix: The code that renders the Audit Report has been improved to properly display the apostrophe character. | |
4452559 |
Summary: When uploading an image containing orientation metadata to the Web Form image field, the metadata is lost during the image processing. |
Fix: The image metadata is now being extracted before the image is converted and then reapplied after conversion. |
|
4452592 |
Summary: Reminder events are not visible under the Agreement Events in Salesforce because the Reminder event isn't an enum in the events file. |
Fix: The Reminder enum has been added to the events file. |
|
4453260 |
Summary: If multiple documents are uploaded, and those documents have fonts that collide during processing, the resultant document is garbled. |
Fix: When multiple documents are uploaded, embedded fonts that collide are renamed. |
|
4453282 |
Summary: If a recipient is represented in an agreement in more than one role and is delegated into a participation set, it's possible that during signing the user value isn't selected from the set returning an error instead. |
Fix: Code has been updated to ensure delegated users in a participation set are properly understood and selected during the signature process. |
|
4454688 |
Summary: When all members in a recipient group are replaced, the list of recipients in that group is empty and triggers errors in signing. |
Fix: Checks have been put in place to identify and manage recipient groups to have a size of zero. |
|
4455110/ 4458255 |
Summary: Group names that have spaces in the name string may prevent the group from being selected when a user attempts the change the group in the UI due to a mismatch between the database name and the value stored in the group picker. |
Fix: Code has been added to ensure that the picker name is stored in the same format as the groupID name in the database. |
|
4456164 |
Summary: When a customer adds specific instructions for an additional participant while creating a web form, the text appears with line breaks in the middle of words when viewed by the signer. |
Fix: Word breaks have been removed. |
|
4456295 |
Summary: When users switch between groups, they sometimes end up seeing settings for the wrong group due to caching setting values. |
Fix: The navigation tree is fully cleared when changing groups. |
|
4456427 |
Summary: The tooltip for how attachments are named when attached to the final email is inaccurate. |
Fix: The tooltip has been updated to be more clear. |
|
4457210 |
Summary: Text overlapping with default text when Print, Sign, and Upload is used. |
Fix: The function to place the values in the dropdown has been improved to apply selected values of default values. |
|
4457539 |
Summary: Unable to add URL with '.art' domain extension in OAuth configuration. |
Fix: The top-level domain validator has been updated. |
|
4457813 |
Summary: Phone numbers are mixed up when initiating workflow via API when multiple recipients use the same email but different phone validations. |
Fix: Code has been improved to manage the use case of multiple recipients with he same email having different phone numbers. |
|
4458114 |
Summary: Signature fields subsequent to the first one have the text Tap to change instead of Tap to Sign when the value in the first field hasn't been applied. |
Fix: For the case where a value has not yet been applied, the text in the field will reflect Tap to sign. | |
4458141 |
Summary: When the email address is lowercase in the participant set but mixed-case in the senderEmail field, the user may be unable to see the Sign and Send option in new authoring. |
Fix: Changed comparison of the emails to be case insensitive. |
|
4458673 |
Summary: Recipients without an Acrobat Sign userID do not show all user values in data exports. |
Fix: Data exports have been updated to include the data from users not stored under userIDs in the database. |
|
4458731 |
Summary: Mozambique Country Code(+258) is not included in the list of supported country codes. |
Fix: +258 country code added. |
|
4458789 |
Summary: Impressively long API request logs will time out when loading. |
Fix: The SQL index has been updated. |
|
4459539 |
Summary: Private messages do not work when the sender is in a group where Private Messages are disabled, but the user sends from a different group with private messages enabled. |
Fix: Code has been added to ensure the group-level settings are honored. |
|
4461081 |
Summary: Drop down field value is not visible on the signed agreement when the agreement is digitally signed. |
Fix: several annotations have been removed, and the import function has been refactored to improve the field visibility. |
|
4461180 |
Summary: Unable to upload a signed document when the next recipient to sign the document is the agreement's originator. |
Fix: The function that checked the participation has been improved. |
|
4461726/ 4464466 |
Summary: Content protection is not inherited from a Workflow group. |
Fix: Code has been improved to ensure the group settings are applied. |
|
4461845 |
Summary: The "Next" button is unresponsive when the agreement contains a Digital Signature field. |
Fix: The library that drives the Next button has been updated. |
|
4464349 |
Summary: The new Send in Bulk can break synchronization with Acrobat Sign when used through API due to an incorrect field type. |
Fix: The field type has been corrected. |
|
4464621 |
Summary: Templates that contain fields for more recipients than the agreement contains can block the agreement process from loading the new authoring page. |
Fix: A redirect to the classic authoring page has been put in place when this issue is detected. |
|
4465906 |
Summary: Agreements created with a custom send workflow may not show the Upload Signed Document option on the Manage page. |
Fix: Updated the check that allows the upload signed document action to be available for custom workflows provided all conditions are met. |
|
4469350 | Summary: Agreements created via API with a parallel signature flow do not appear in the classic send environment in the correct order they were defined in the API call. |
Fix: The sorting of the recipients has been corrected for the classic environment. |
Production deployment: March 12, 2024
GovCloud deployment: March 19, 2024
Improved Functionality
- The new Request Signature experience updated with additional feature support - The new Request Signature experience takes a big step towards parity with the classic experience by adding support for:
- Seamless authoring experience (navigate back to the agreement configuration from the authoring environment)
- Organizational contacts in the address book
- Recipient groups, both ad-hoc and reusable
- Modifying agreements in flight
- OneDrive file upload
Available environments: Sandbox, Commercial | Available tiers of service: Individual, Teams, Enterprise | Configuration scope: Not configurable
- Recipient identity check - Administrators can configure their account (or group) to require a check of the recipient's email address to match the expected value (as defined when the agreement is composed) when the recipient authenticates using the Digitial Identity Gateway.
Available environments: Sandbox, Commercial, Government | Available tiers of service: Individual, Teams, Enterprise | Configuration scope: Group, Account
- User-led provisioning for Microsoft Power Automate within Acrobat Sign – Users who wish to create workflows within Acrobat Sign using the Power Automate integration can now provision access on behalf of their organization.
When a user selects to create a new workflow, they will be presented with the Adobe Terms of Included Entitlement, Limits on Use Capacity, and the Microsoft terms and conditions, which they must agree to in order to enable the Power Automate integration.
Administrators who would like to manage access to user-led provisioning can do so by navigating to Global Settings > Power Automate Workflows.
Available environments: Sandbox, Commercial | Available tiers of service: Enterprise | Configuration scope: Group, Account
- Send agreement links via SMS to the recipient's phone number - Senders can optionally configure their agreement to send the agreement links directly to the recipient's phone number (in addition to the email address), allowing the recipient to review and sign the document directly on their smartphone without going through email first.
Available environments: Sandbox, Commercial | Available tiers of service: Enterprise | Configuration scope: Group, Account
- OTP via Email authentication support for custom send workflows - Custom send workflows now support the option to use the One-time password via email authentication method.
Available environments: Sandbox, Commercial, Government | Available tiers of service: Enterprise | Configuration scope: Group, Account
- Flatten uploaded files to embed default field values before authoring - Customers who build forms and templates that have fields containing default values can enable this feature to "flatten" the document after upload, embedding any default values into the source document before opening the authoring environment. This ensures that users cannot mistakenly alter the default values of the uploaded file during the authoring experience.
Available environments: Sandbox, Commercial, Government | Available tiers of service: Enterprise | Configuration scope: Group, Account
- Private message support for CC'd parties on web forms - The CC'd participants on a web form can now have a private message configured that will be included in the email notification they receive when the agreement is completed.
Available environments: Sandbox, Commercial, Government | Available tiers of service: Enterprise | Configuration scope: Not configurable
- Agreement metadata for Cloud Signatures - When creating digital signatures via third-party Trust Service Provider (TSP), Acrobat Sign can now optionally send additional metadata to the TSP. The included data is:
- Account ID - For identifying the customer account and processing transactions enabled at the account level.
- Group ID - For identifying the customer's group when a group has enabled a specific TSP for signature processing.
- Transaction ID - To provide additional support in validating transaction processing per transaction. Useful in understanding the customer's consumption and billing with the vendor.
Available environments: Sandbox, Commercial | Available tiers of service: Individual, Teams, Enterprise | Configuration scope: Group, Account
Experience Changes
- The classic Send page environment is changing the Email authentication type to None - In the list of authentication types on the classic Send page, the Email auth type has been changed to read None. The functionality has not changed. Agreements are still sent to the email address of the recipient provided Email is one of the types of delivery selected.
The new Request Signature environment continues to use the term Email for now and will be updated to use None in a future release.
- The format of email headers has changed to alter the From property for recipient emails, such as the initial "Please Sign" and Reminder templates. The previous format of "Adobe Acrobat Sign on behalf of <SomeUser>" has been changed to "<SomeUser> via Adobe Sign". The shorter format will ensure that the sender's name is not truncated.
- The Restricted Cloud Signature Providers section on the Digital Signatures tab of the admin menu has been removed - The account and group IDs are listed at the top of the Global Settings and Group Settings, respectively. The Restricted Cloud Signature Providers section of the Digital Signatures tab has been removed as this information is best-sourced from the account or group as needed.
- The new Send in Bulk interface has been promoted to the default experience - All accounts have had their Send in Bulk experience upgraded to the new environment. Users have access to a link allowing them to switch back to the classic interface, and admins have access to the controls to set the default back to the classic experience if needed.
- VIP customers have access to a new Chatbot experience when using the in-application guidance - The new Chatbot has been developed to improve the response to customer questions by providing a better, interactive interface that delivers suggestions for top queries in the welcome message, recommendations based on previous selections from the user, direct query support, and complex query resolution. Users are asked to provide feedback on the returned information to help learn how to reply better in future instances, and an option to connect to a support agent via chat is presented if the information requested isn't found.
- VIP customer access to the new Chatbot experience has been suspended - The new Chatbot has been suspended until the next release in April 2024.
Integration Updates
- Support for secondary authentication methods in Microsoft integrations - Obtaining a signature through the Microsoft Teams, Outlook, and Word/PowerPoint integrations now supports using secondary authentication methods like Phone (SMS) authentication.
- Acrobat Sign for Veeva Vault updated to v1.3.0
- Veeva Vault Library Upgrade - The application has been updated to a more modern and efficient Vault API library (VAPIL) for enhanced integration.
- Veeva Vault API version Upgrade - The Veeva Vault API version has been upgraded to v23.1
- The Integration deployment package has been enhanced to ensure no requirements are imposed on customers to use the latest document version.
Resolved Issues
Issue | Description |
---|---|
4436411 |
Summary: The user guide within the application is not opening localized user guide pages. |
Fix: The localization code for how the user guide URL is mapped was corrected. | |
4441053 |
Summary: Accessing any agreement, template, or web form from the Manage tab is throwing an error on the console. |
Fix: A deprecated library was removed to eliminate this error. | |
4441309 |
Summary: Obtaining a written signature on an iPad causes a reload cycle when popups are disabled on a mobile device. |
Fix: Pop-up detection added and an error dialog has been added to allow the user to explicitly allow the pop-up. | |
4444676 |
Summary: The "Click to sign" button doesn't work when the Email is selected from autofill in MS Edge when signing a Webform. |
Fix: Added a new "confirm email field" in the reset fields method. |
|
4449161 |
Summary: Completed agreements sent using a workflow do not email the sharee. |
Fix: The XML related to sharing agreements has been added to the workflow templates. New workflows updated or created after the March 2024 release will now include the share notification process. | |
4454140 |
Summary: When a singer has two or more initial fields that have a showIf condition applied to appear with the first initials field is filled, the second field is not exposed. |
Fix: The field mapping values have been corrected to allow for the proper actions regarding showIf conditions. | |
4456726 |
Summary: When senders add an alternate participant, existing unexpired reminders do not have the new recipient added when the sender's choice option is enabled. |
Fix: The code has been fixed to allow the new recipient to be added. | |
4457764 |
Summary: Navigation panels don't have the appropriate contrast ratio of 3:1 for a focus indicator |
Fix: The identified side menus and body tables have been updated to have blue indicators with the appropriate contrast ratio. | |
4458840 |
Summary: When there is a recipient group or delegation. The 'on behalf' mail always shows the signer in the 'header' when the option to hide the recipient email is set to true. |
Fix: Modified the header to set the right recipient address. |
|
4458887 |
Summary: Recipient order in a data export CSV, "Number of Remaining Recipients" or "Number of Complete Recipients" is incorrect. |
Fix: The impacted functions have been updated to produce the expected result. | |
4459061 |
Summary: Sandbox - Error seen while customizing the "Company" field using the new authoring experience and using a template created in the classic authoring environment. |
Fix: The API has been updated to properly identify and make available the fields. | |
4460178 |
Summary: Inconsistent delegation for recipients that are already participants in an agreement depending on the recipient's status in the Acrobnat Sign system. |
Fix: The impacted functions have all been corrected to provide a consistent experience (Participants already in the agreement cannot be delegated to) | |
4460284 |
Summary: The Phone authentication default is not working for group-level workflows. |
Fix: Updates to the workflow designer have corrected this issue. | |
4460685 |
Summary: Sharing status - Deleted groups are visible when a group is deleted, and an existing share is still active. If a user creates a group with the same name again, then two groups with the same name are displayed. |
Fix: Deleted groups have appended a [Deleted] string next to the group name. |
|
4461456 |
Summary: When sending an agreement with a 'completion deadline' on the authoring page, a duplicate agreement expiration event is created for scheduling. This results in expiry events/emails getting triggered twice. |
Fix: A status check was added to identify and prevent duplicate messaging. | |
4461634 |
Summary: Text fields don't appear on the signable document if the field name is only a special character as the name is then stored as a decoded character. |
Fix: Encoding of special characters in form field names when saving the updated fields on the Authoring page has been added. |
|
4461953 |
Summary: Recipient fields are moving up in the document when sending from workflow and previewing before sending. |
Fix: Fixed a function issue for a function TypeError exception which prevents proper text banner for default warning. |
|
4463091 |
Summary: On Bulk Send, while selecting the group from the drop-down, the logo does not change. |
Fix: Added the required attributes to the bulk send model. | |
4463209 |
Summary: Filter to show only Admins isn't working as expected. Returning an error of too many users. |
Fix: The filter to show only admins has been corrected, resulting in only admins returning. | |
4463384 |
Summary: If externalId is passed when an agreement is created using the Workflow in 'Draft' state utilizing the POST agreements API endpoint, then the externalId is persisted in draft_resource table. When the Send button is pressed to send the agreement, then PUT agreements/{AgreementID} call is made. As part of this call externalId is not passed from UI. |
Fix: Added call to load externalId from agreementInfo object to agreement object for custom compose flow. |
|
4463469 |
Summary: HTML code is observable in an error message due to HTML not being supported in the error message object. |
Fix: HTML removed from the error message. | |
4463485 |
Summary: The signature field is missing in an agreement when the signer opens the agreement in two different browsers at the same time and e-signs one while attempting to print, sign, and upload in the other. |
Fix: An error is delivered indicating the user should reload the page to get the refreshed page with the signature field exposed. | |
4463507 |
Summary: When the KBA authentication mandates the inclusion of both first and last names, on the custom compose page, there is a possibility of submitting the agreement without entering the necessary data. |
Fix: Validation has been implemented. If the setting requires name information, an error will be displayed when the KBA first name and last name are left unfulfilled. |
|
4463881 |
Summary: Update users in bulk fails for the group containing special characters. |
Fix: The group name is encoded when verifying if the group already exists to align with the database entry. Special characters are encoded in the database. |
|
4463888 |
Summary: Vaulting does not apply to workflows. 'Vault this agreement' is unchecked if the vaulting setting is set to On. |
Fix: If we do not have the vaulting Info value set by the user, the VAULT_BY_AGREEMENT setting is checked. |
|
4464230 |
Summary: Workflows may take 4-5 minutes on average to open for some accounts. |
Fix: The database calls have been streamlined to reduce overall processing time. | |
4464396 |
Summary: The attached files are removed when switching the view on the Send page. |
Fix: Code improved to preserve all parameters when switching between environments. | |
4464473 |
Summary: Agreement sharing with users is not functioning for agreements sent using a workflow and signed by the sender only.. |
Fix: The self-sign workflow code has been improved to accommodate sharing the agreement. | |
4464483 |
Summary: POST /webhooks sometimes take more than 15 seconds to respond (or times outs) when called immediately after creating a new account. |
Fix: Syncing for new account creation has been streamlined to reduce processing time. | |
4464620 |
Summary: Government ID fails if the first name of the document is empty |
Fix: A check has been implemented to manage the event when a first name is blank. | |
4464792 |
Summary: Regardless of the value of the "show link in email" setting, when sharing a completed agreement, the link to view the document online always appears in the email. |
Fix: Created a new template that displays the link for viewing online, depending on the value of the show link in email setting. Modified the original template to include a check for whether the agreement is signed, and added logic to display the proper template based on settings. |
|
4464844 |
Summary: Agreements will fail to send if there are text tags assigned to the sender and the sender isn't a participant in the agreement. |
Fix: When the source document has text tag fields assigned to the "sender" role, they are deleted if the sender isn't participating in the agreement. |
|
4464907 |
Summary: When changing the authentication method of a previously saved Draft agreement, the authentication method isn't updated. |
Fix: When processing a recipient for the first time, the default auth method from their per-recipient settings is used. |
|
4464978 |
Summary: The GET /agreement/id/formFields endpoint throws an NPE due to a PDFLink with an empty location. |
Fix: Code has been added to manage the NPE issue. PDF links with no location are now omitted. | |
4465801 |
Summary: Acrobat Sign will continue to attempt to thumbnail an abandoned document if the document is large enough, resulting in a timeout error. |
Fix: Code update to allow abandoned thumbnails to be completed, regardless of the abandoned status. | |
4465946 |
Summary: Web forms can fail in a way that prevents them from being able to be opened. |
Fix: The logic around how web forms are processed has been updated to unblock a form that is failing to properly apply validation checks. | |
4465952 |
Summary: Workday - Documents with invalid annotations throw exceptions, causing the agreement to be canceled. |
Fix: Annotations with no subtype are now ignored. | |
4466399 |
Summary: The Sender group column is missing on CSV export. |
Fix: The column has been added to the export. | |
4466560 |
Summary: Web forms can be automatically canceled due to a null pointer error due to unknown participants. |
Fix: Code has been added to properly manage the unknown participants. | |
4466885 / 4467126 |
Summary: UMG-enabled accounts send all of their groupIds in the header when sending a Bulk Send, which can be more than the max header size the microservice accepts. |
Fix: The max header size has been increased. | |
4467036 |
Summary: Unable to sync Custom Workflows from Sandbox to Production due to faulty user encoding. |
Fix: User encoding has been corrected for the syncing process. | |
4468762 |
Summary: The KBA verification will validate only the first member of the group of recipients and let you send the agreement even if the other members have a KBA auth and name info left empty. |
Fix: The compose page now loads with a null recipient order, forcing a name check. | |
4469069 |
Summary: In the sandbox environment, the e-sign page has an extra space between the header and the sandbox blue bar |
Fix: The header has been modified to allow a full view of the text. | |
4469416 |
Summary: In the e-Sign page's Option and Help menu, keyboard users are unable to navigate away from the expanded dropdown menu using the Tab key. |
Fix: The Tab key can now close the menu. The focus shifts back to the dropdown trigger button after the menu is closed. |
|
4469419 |
Summary: Even when set to 'Not Allowed' in the new experience, the agreement name can still be changed. |
Fix: Editing has been restricted based on the workflow configuration. | |
4469680 |
Summary: CC info is not seen on the Manage page, the CC recipient does not receive the final signed filed email, and CC info does not appear in the Email body if the sender does not press "Enter" after entering the information. |
Fix: The information for the CC'd parties has been added to the agreement when the field loses focus. | |
4470393 |
Summary: Required hyperlinks from library templates are duplicated on the e-Sign page resulting in unsignable agreements. |
Fix: How fields are transferred to child agreements form templates have been updated to ensure only one field is present. | |
4472895 | Summary: If a sender uses the same email address as a Sealer recipient, but the case used in the email is different, an error will be triggered due to case sensitivity. |
Fix: Case sensitivity has been removed when assessing the strings in this use case. | |
4472954 | Summary: Sync speed for workflows between the Sandbox and Production environments is very slow. |
Fix: Improvements to the query and code have improved sync time. | |
4474353 | Summary: Connecting a Salesforce application to the Acrobat Sign Sandbox fails to redirect the user to the correct page due to the target URL not being set properly. |
Fix: The code has been improved to set the target URL correctly and facilitate the user redirection. | |
4474581 | Summary: The Sandbox stopped pushing webhook notifications after a rebuild of the Sandbox environment. |
Fix: The Sandbox was redeployed, and the problem was resolved. |
Production deployment: April 09, 2024
GovCloud deployment: April 11, 2024
Improved Functionality
- Phone authentication support for web form signers - Enterprise customers who use web forms can now configure phone authentication for the first signer of the web form. The phone number is requested and verified immediately after accessing the web form (before the signer can interact with any fields).
Available environments: Sandbox, Commercial | Available tiers of service: Enterprise | Configuration scope: Enabled by default
- Enable the cookieless "Request Signature" experience for customer integrations - Customers who have created their own applications that invoke the Request Signature experience can enable the cookieless environment, providing a more seamless experience for their users.
Available environments: Sandbox, Commercial | Available tiers of service: Enterprise | Configuration scope: The UI for the option is exposed by default. Enabling is manual by Application.
Experience Changes
- The new Send in Bulk environment is now the default experience for all accounts - The new and improved Send in Bulk environment has been promoted to the default experience with the April 2024 release. This is the first step in ending access to the classic environment, which is planned to be removed entirely from the user experience by March 2025.
- Administrators continue to have the option to reset the default environment to the classic experience through their admin menu.
- Links remain available for users to switch between the new and classic environments.
- Administrators continue to have the option to reset the default environment to the classic experience through their admin menu.
- VIP customers have access to a new Chatbot experience when using the in-application guidance - The new Chatbot has been developed to improve the response to customer questions by providing a better, interactive interface that delivers suggestions for top queries in the welcome message, recommendations based on previous selections from the user, direct query support, and complex query resolution. Users are asked to provide feedback on the returned information to help learn how to reply better in future instances, and an option to connect to a support agent via chat is presented if the information requested isn't found.
- Removal of the mobile app banner - The banner advertisement for the Adobe Acrobat Sign mobile application has been removed from the Home page.
Resolved Issues
Issue | Description |
---|---|
4466859 | Summary: Date formatting in US English does not properly translate on the e-sign page. |
Fix: Code update to ensure the e-sign date matches the PDF date formatter. | |
4467995 | Summary: Limited Document Visibility can break a web form when multiple files are used and then edited/removed. |
Fix: Code has been improved to ensure the hidden files of an agreement are correctly preserved when updating a web form with LDV enabled. | |
4469175 |
Summary: When selecting the signing URL, some browsers do not open the iFrame citing an error that cookies are disabled. This is due to changes in browser requirements. |
Fix: The parameters for the cookie have been updated to comply with the requirements of the change. | |
4469178 | Summary: The download URL can be misaligned with the agreement resources based on the esigning environment |
Fix: The claim to the resources has been updated to align with the correct experiences used. | |
4469538 | Summary: Email notifications are being sent when the "emailOption" and "redirectOptions" options in v6 API are set to "none" |
Fix: The code to execute email notifications has been updated and reordered to ensure the correct settings for the agreement are applied. | |
4475491 |
Summary: The View and Delegate URLs generated by the API fail with an unauthorized error when Content Protection is enabled due to missing logic to create a temporary user session. |
Fix: The logic has been added to permit the creation of the user session that generates a viable URL. |
Production deployment: June 18, 2024
GovCloud deployment: July 9, 2024
Improved Functionality
- Updated Request Signature experience - The Request Signature interface adds several elements that bring the experience closer to parity with the classic Send page. Included in this release are:
- Drag and Drop files - Files can now be added to the agreement configuration by dragging them from your desktop or local folders and dropping them into the Files section.
- Add Me - The Add Me option adds the agreement creator to the agreement in the next recipient record.
- e-Vaulting - Customers who require e-vaulting can now use the Request Signature experience and be assured that the agreements are added to their vault.
- Hybrid Routing - Configuring agreements with hybrid signature workflows is now supported when enabled.
Available environments: Sandbox, Commercial | Available tiers of service: Individual, Team, Enterprise | Configuration scope: Enabled by default
Resolved Issues
Issue | Description |
---|---|
4459444 |
Summary: The Add Me link to insert the sender as a recipient in the agreement signature flow is missing in the new Request Signature environment. |
Fix: The Add Me link has been added and is functioning the same as it has previously on the Send page. | |
4477422 |
Summary: The payment field may not work properly through the new authoring environment, converting the Payment fields into Text fields. |
Fix: The code was updated to properly manage the payment field. |
Sandbox deployment: July 16, 2024
Production deployment: August 13, 2024
GovCloud deployment: August 15, 2024
Experience Changes
- A new post-signing page for unregistered recipients — Recipients who complete their action (sign, approve, etc.) are delivered to a new post-signing page that provides access to their agreement PDF, and offers an opportunity to try a few of the more popular Adobe Acrobat features.
Countries with stricter communication laws will not display the four "Try now" offers.
A secondary stripped-down experience is delivered to recipients whose agreements are subject to the following exemptions:
• Recipients signing an agreement through an embedded application.
• When the group from which the agreement is sent has a redirect URL.
Registered recipients are delivered a version of the post-signing page that provides a button to sign in to the Manage page of their Acrobat Sign account.
Available environments: Sandbox, Commercial | Available tiers of service: Enterprise | Configuration scope: Not configurable
- Change to the Send Code announcement for Phone Authentication - The panel that alerts a recipient to the requirement for phone authentication has been updated to include an additional acknowledgment:
"By clicking the 'Send Code' button, you acknowledge and agree that you will receive an automated phone call or text message at the number you provided to confirm your identity."
Available environments: Sandbox, Commercial | Available tiers of service: Individual, Teams, Enterprise | Configuration scope: Not configurable
Webhook update
Update to the Webhook notification payload for all AGREEMENT_* subscription event types – All Agreement webhook notification events have been updated to include three new fields:
- userId - The unique identifier of the participant
- Requires the Agreement Info parameter to be checked in the Notification Parameters for the value to be included in the payload.
- authenticaitonMethod - The authentication method used for the participants to have access to view and sign the agreement.
- createdGroupId – The ID of the group from which the webhook was created.
- Requires the Agreement Info parameter to be checked in the Notification Parameters for the value to be included in the payload.
Resolved Issues
Issue | Description |
---|---|
4465123 |
Summary: Using SSO authentication may result in "review and Sign" emails having faulty hyperlinks. |
Fix: The code has been improved to properly resolve SSO and SAML authentication processes. | |
4479831 |
Summary: An extra backslash '\' release character is added to the name in the ESeal. |
Fix: The code has been updated to properly manage the release character | |
4479994 |
Summary: The email template used to communicate user migrations uses internal name values instead of the customer-applied values. |
Fix: The template has been updated to use the correct customer provided values. | |
4483513 |
Summary: Email addresses with an apostrophe in the Display email fail to resolve their GET calls when the agreement involves an ESeal. |
Fix: The code has been updated to properly manage the use case of an apostrophe in the Display Email field. |
Production deployment: September 17, 2024
GovCloud deployment: October 8, 2024
Improved Functionality
- E-Witness an agreement - A new role has been added: Sign with Witness. Witnesses are identified by the signers at the time they open the agreement, before their signature is accepted.
Available environments: Sandbox, Commercial, Government | Available tiers of service: Acrobat Sign Solutions | Configuration scope: Group, Account
- New Recipient experience when interacting with an agreement - The recipient's signing environment has been updated to provide a better experience for all recipients.
Available environments: Sandbox, Commercial | Available tiers of service: Acrobat Standard, Acrobat Pro, Acrobat Sign Solutions | Configuration scope: Account or Group
- Updated Audit Trail report—Accounts can update their Audit trail to include more information about the documents that the agreement recipients see and how they interact with them.
Available environments: Sandbox, Commercial, Government | Available tiers of service: Acrobat Sign Solutions | Configuration scope: Group, Account
- New filter and search functionality for the Reports environment - The filter selector has been improved to allow for selecting multiple filters without the drop-down box closing after each selection. Additionally, the search field capabilities have been improved to search for matches anywhere within a word string. Matches can be found at any word's beginning, middle, or end.
Available environments: Sandbox, Commercial | Available tiers of service: Acrobat Standard, Acrobat Pro, and Acrobat Sign Solutions | Configuration scope: Enabled as part of the base feature
- Custom email templates and Report Abuse links are now supported for Linkless notifications - The option to send Acrobat Sign agreement notifications without active links is now supported in Custom Email Templates. Additionally, the Report Abuse URLs are included in the notification.
Available environments: Sandbox, Commercial | Available tiers of service: Acrobat Sign Solutions | Configuration scope: Group, Account
- Senders can view form field data as recipients fill them in—The sender of an agreement can view the field content of an agreement's fields as the recipient fills out the form. The view of the fields persists until the recipient completes their action.
Available environments: Sandbox, Commercial | Available tiers of service: Acrobat Sign Solutions | Configuration scope: Group, Account
- Allow recipients to download the individual files of an agreement - Recipients can be enabled to download their agreements in the form of the individual files that originally created the agreement.
Available environments: Sandbox, Commercial, Gov Cloud | Available tiers of service: Acrobat Sign Solutions | Configuration scope: Group, Account
- Improvements to the Request Signature page:
- Support for sending through Advanced Account Sharing - The Request Signature process now supports Advanced Account Sharing.
- SMS or email delivery - The option to send an agreement URL directly to a phone number has been added to the Request Signature experience.
- Calculated fields - The new cookieless authoring environment now supports calculated fields.
- The Authentication Method and Private Message configuration has been moved to their own interface - The Private Message and Authentication Method interface has been moved from being in-line with the recipient record and into a new subsection called Recipient Settings. Each recipient has their own explicitly configurable Recipient Settings section.
- Support for sending through Advanced Account Sharing - The Request Signature process now supports Advanced Account Sharing.
Available environments: Sandbox, Commercial | Available tiers of service: Acrobat Sign Solutions | Configuration scope: Enabled as part of the existing base feature
- Updates to the Send in Bulk experience:
- Send in Bulk has been updated to accommodate CC'd information for the CSV upload method of agreement creation - The CSV upload method for generating Send in Bulk child agreements now supports adding CC'd parties.
- Send in Bulk has been updated to include the Email via One-time Password authentication option through the CSV upload method. The One-time Password authentication method is available when creating Send in Bulk transactions using the CSV method.
- Send in Bulk is included in the Send permission for Advanced Account Sharing - Sharing accounts under advanced sharing rules, with Send authorization enabled now includes access to create and send agreements using the Send in Bulk feature as the sharing userID.
- Send in Bulk report for errors created when generating the child agreements - When errors are generated through the Send in Bulk process using a CSV upload as the source of recipients, a downloadable file is generated so the sender can correct inaccurate input.
Available environments: Sandbox, Commercial | Available tiers of service: Acrobat Pro, Acrobat Sign Solutions | Configuration scope: Enabled as part of the existing base feature
- The process of saving a web form has more granular controls - The control for validating a web form's first signer has been separated from the control to enable the recipient's access to save a web form.
Available environments: Sandbox, Commercial, Government | Available tiers of service: Acrobat Standard, Acrobat Pro, Acrobat Sign Solutions | Configuration scope: Enabled as part of the existing base feature
- Web forms support phone authentication for signer-added participants - Web forms that allow signer-defined participants can now include phone-based authentication for the added recipients.
Available environments: Sandbox, Commercial, Government | Available tiers of service: Acrobat Standard, Acrobat Pro, Acrobat Sign Solutions | Configuration scope: Enabled as part of the existing base feature
- Improvements to Identity Check - The recently added Identity Check policy has been updated to provide:
- API support for Identity Check configuration in /agreement endpoints.
- Name matching for Government ID and Cloud Signatures, with exact name matching only.
- Email matching for Cloud Signatures (to include Alternative Name matching).
Available environments: Sandbox, Commercial | Available tiers of service: Acrobat Sign Solutions | Configuration scope: Group, Account
- Improvements to the Signer Identity Report—The Signer Identity Report now includes more granular information to improve the understanding of the identifying document, such as differentiating a regular (full) driver's license from a provisional license.
Available environments: Sandbox, Commercial, Government | Available tiers of service: Acrobat Sign Solutions | Configuration scope: Group, Account
Experience Changes
- New support experience for accounts using the classic user interface - Long-time customers who haven't migrated their user management to the Adobe Admin Console have a new experience for contacting support and entering tickets.
Available environments: Commercial | Available tiers of service: Enterprise | Configuration scope: Enabled by default
- The new Request Signature environment is now the default experience for all accounts - The new and improved Request Signature environment has been promoted to the default experience with the September 2024 release. This is the first step in ending access to the classic environment, which is planned to be removed entirely from the user experience by March 2025.
- Administrators continue to have the option to reset the default environment to the classic experience through their admin menu.
- Links remain available for users to switch between the new and classic environments. Accounts that have previously disabled switch links will need to do so again.
- Administrators continue to have the option to reset the default environment to the classic experience through their admin menu.
Available environments: Sandbox, Commercial | Available tiers of service: Individual, Team, Enterprise | Configuration scope: Account, Group
- Improved expereience in the Request Signature environment for when a sender is the first signer or when prefill fields exist - When an agreement is sent, and the sender is the first signer, or prefill fields are present on the agreement, the signing environment opens immediately, allowing the sender to fill fields and sign without having to first access their email or Manage page.
Available environments: Sandbox, Commercial | Available tiers of service: Individual, Team, Enterprise | Configuration scope: Enabled by default
- Send in Bulk has updated the interface to display the Message field when the CSV upload option is selected - The Message section is no longer hidden when a user selects the option to upload a CSV file to generate the child agreements through the Send in Bulk process.
NOTE: This experience change was released to the production environment early.
Available environments: Sandbox, Commercial | Available tiers of service: Individual, Team, Enterprise | Configuration scope: Account, Group
- The Create Template experience for integrations that embed the user experience now employs the new Authoring functionality - Prior to this release, the Create Template experience in the embedded experience used the classic Authoring environment. As of this release, the newest Authoring environment is being used.
Available environments: Sandbox, Commercial | Available tiers of service: Enterprise | Configuration scope: API Application.
- Respect date format preferences in well-formatted signatures - The customer-defined preferred date format is now applied to the well-formatted signatures and signature blocks.
Available environments: Sandbox, Commercial, Government | Available tiers of service: Individual, Team, Enterprise | Configuration scope: Account, Group
- Viewing/modifying an agreement set to be e-vaulted now opens on the Request Signature page - Customers using the eOriginal integration can now open agreements flagged to be vaulted in the Request Signature environment instead of the classic Send page environment.
Available environments: Sandbox, Commercial | Available tiers of service: Individual, Team, Enterprise | Configuration scope: Account, Group
Resolved Issues
Issue | Description |
---|---|
4323027 |
Summary: Search in New Experience does not work correctly for charnum values or with underscores. |
Fix: The database was reindexed after the server migration, resolving the issue | |
4446870 |
Summary: Users are getting a blank screen when trying to login to Acrobat Sign intermittently |
Fix: Updated the JSP being served, resolving the eissue. | |
4456574 |
Summary: In the new experience if you author and send without adding a signature box, it doesn't try to add it to the last page due to a thumbnail not being created on the latest version. |
Fix: The classic behavior has been replicated with all new code to provide a consistent experience. | |
4459445 |
Summary: The document name field in the new experience for recent templates is too small to see the name |
Fix: The size of the field has been improved. | |
4465815 |
Summary: The "Well formatted" chrome is converted to English when the signature is processed. |
Fix: The locale of the user settings is now referenced when the signature appearance is created. | |
4467671 |
Summary: Emails sent in the Polish locale have unique formatting |
Fix: The localized template was reconfigured to be consistent with other locales | |
4468713 |
Summary: The agreement email body consists of incorrect and inaccurate messages/content. |
Fix: Multiple systems and templates updated to align the email templates | |
4468718 |
Summary: Typo in the Signature requested emails in Polish Language |
Fix: The typo has been corrected. | |
4469262 |
Summary: Blank White screen while selecting a template while using bulk send New Experience |
Fix: The Bulk Send processor has updated libraries, solving the issue. | |
4470664 |
Summary: Reminder events don't propagate automatically like other events in Salesforce |
Fix: The REMINDER_SENT event is now being pushed from the core application using the v6 REST methods | |
4471103 |
Summary: User email address with apostrophe twice is failing with the error message in workflow. |
Fix: The code managing the email formatting has been improved to accommodate this use case. | |
4471385 |
Summary: Content Protection feature not working as expected through re-authorization |
Fix: Improved code to ensure to fetch the correct Account details of the internal user are referenced when a Hostname is defined in the Account |
|
4471478 |
Summary: "AGREEMENT_WORKFLOW_COMPLETED" notification incorrectly shows SIGNER status as "WAITING_FOR_MY_SIGNATURE" |
Fix: Corrected the index that was being assigned to the status. | |
4472497 |
Summary: Documents with unparsable metadata are not properly handled |
Fix: XMP parse exceptions and now ignore |
|
4472908 |
Summary: The Password option cannot be suppressed in the new sending experience |
Fix: The component for adding the authentication options has been updated to properly reflect the authentication methods allowed for the group | |
4473086 |
Summary: Participation stamp and Transaction ID fields are not present on Notarized agreements due to being placed post signature on an earlier version of the agreement |
Fix: The processing has been improved to properly place the post-signing fields onto the agreement after notarization | |
4473112/ 4473556 |
Summary: Error thrown in new Send in BUlk if the sender is the first signer due to a check for this use case |
Fix: The check for the use case is now being ignored. |
|
4473248 |
Summary: Agreements may intermittently cancel due to streams with /Name attributes that are strings |
Fix: Now only /Type attributes that are Names will be checked | |
4473286 |
Summary: Delegation verbiage can be seen in the 'Signature Requested' email notification even after disabling delegation in account settings |
Fix: Added a condition which checks internal and external delegation setting values of Originator and display or hide the delegation link in email. |
|
4474071 |
Summary: Transfering ownership of a template is not updating the owning groupID |
Fix: Repaired the code to properly update the ownership table to reflect the new groupID | |
4474082 |
Summary: File attachments don't append to the signed pdf to a null pointer error |
Fix: Added a null check prior to the process where files are added to the final PDF | |
4475331 |
Summary: When CC sends a reminder to the originator, an error occurs the next time the Reminders button is clicked. |
Fix: Distinct logic has been added for this use case. | |
4475449 |
Summary: Documents with invalid Creation Dates will fail to process and become downloadable |
Fix: Code has been added to ensure that a valid creation date is available before saving. | |
4475603 |
Summary: The group is not selectable when in the Russian locale due to extra quotes in the locales script. |
Fix: The code for the Russian locale has been corrected so the script can run |
|
4475864 |
Summary: Upload signed copy is changing the signature type from written to design, preventing the agreement from being uploaded |
Fix: The code has been improved to properly retain the "written" signature type throughout the process. | |
4476004 |
Summary: Adobe Acrobat Sign events and alerts summary email is not getting triggered due to a legacy event alert. |
Fix: The legacy event alert has been removed. | |
4476583 |
Summary: Workflow's Completion Deadline not updated when set to 180 days due to the logic understanding the value must be less than 180, not less than or equal to. |
Fix: Fixed the parameter to properly accept less than or equal to | |
4477114 |
Summary: Unable to sync Custom Workflows from Sandbox to Production using Sandbox Sync feature |
Fix: Optimization has been added to improve sync times to prevent timeouts | |
4478119 |
Summary: Invalid negative number variable expression throws an exception when trying to edit a template |
Fix: Added a check to prevent the NumericFormatExceptions from being a string-based negative number |
|
4478127 |
Summary: The email footer shows the path to the image when linkless notifications are enabled. |
Fix: The code has been corrected to display the image instead of the path. | |
4478248 |
Summary: Written agreements fail when a signer uploads an esigned PDF because we modify the PDF for the next signer which invalidates the certificate and fails the validation of a signed document for the next signer. |
Fix: Logic has been added such that if the agreement is a written agreement, remove the esigned certificate when creating the pdf for the next signer. |
|
4478745 |
Summary: Unable to download signed document due to a null pointer error if the fontfile does not contain a valid cmap table. This aborts watermark generation and the document cannot be generated. |
Fix: New tests have been added for a valid cmap to preserve the page graphic state. |
|
4478901 |
Summary: When a signer attempts to decline signing an agreement that is hidden through the e-sign page, they encounter a server error due to a method that is intended to check if we are going to list a hidden agreement in any response |
Fix: A new method is being applied that checkz if the caller can edit the participation. |
|
4479209 |
Summary: The email address in the linkless notification instruction, when copy-pasted into the linkless access form page, has spaces in front, in-between and after the email address string and thus gives an error to users. |
Fix: The client-side Javascript now finds and removes all white spaces/line breaks before, after, and in between the email address string before submitting the form and passing the form data down to validation logic and access code read request. |
|
4479223 |
Summary: Date Field format not saving for form fields on AcroForm form fields |
Fix: The date format saved at the group level is not referenced and honored as expected. | |
4480119 |
Summary: Cannot delegate to users included in the CC when the signature was sent. |
Fix: Added a condition to not throw an exception for delegation to "Observe only" and CC participation | |
4480324 |
Summary: Unable to upload CSV in Send in bulk new experience if the Order column isn't completely filled in |
Fix: The code has been updated to allow for empty cells in the Order column | |
4480375 |
Summary: The redirect URI linked in the signup mail that the user receives after confirming their account is incorrect. |
Fix: The link has been updated to /adobeLogin which was incorrectly set to /adobeIDLogin |
|
4480399 |
Summary: There are form fields in some dialog fields that don't have visible, persistent labels, nor are they grouped in a fieldset to programmatically determine their relationship with each other. There are also no validation error messages. |
Fix: Added error messages, labels, and fieldsets with appropriate tags where applicable. Update placeholder text. |
|
4480403 |
Summary: Accessibility labels were missing in certain fields in the Custom Compose JS page, which prevented screen readers from reading the error message when that field was highlighted. |
Fix: Accessibility attributes have been added and the error message that was missing has been added to the modal at the top. |
|
4480407 |
Summary: Accessibility: The meaning of icons is not communicated to all users |
Fix: Added the ID to the recipient email input |
|
4480582 |
Summary: Signer Authentication not being set when sending the agreement to an alias email |
Fix: Added a check to set signer authentication for the recipient when an alias email is used | |
4480614 |
Summary: Agreements can get stuck when using a hybrid workflow and delegating recipients to an alias email. |
Fix: The order of processing for several modules were updated to account for all of the potential cases around delegating known users to aliased emails through a hybrid signature flow. | |
4480638 |
Summary: An interface conflict prevents users from disabling the PayPal option when using the payment interface |
Fix: Code has been improved to allow manipulation of the option to use PayPal. | |
4481121 |
Summary: Notifications aren't sent to agreement shares due to a check for notifications that removes the sharee |
Fix: The logic has been fixed to manage this use case | |
4481307 |
Summary: Written signature flow agreements with multiple signers can fail due to a miscalculation of the total number of participants being less than the total remaining participants, leading to an out-of-bounds index |
Fix: The calculations between the two sets of recipients is now calculated in the same manner to produce the correct results. | |
4481336 |
Summary: Sending in Bulk fails with an invalid CSV error if Senders aren't allowed to override the default authentication, internal auth is enabled, and the internal recipient's signer auth doesn't match the internal default. |
Fix: The CSV parsing code has been improved to manage this use case | |
4481340/ 4482600 |
Summary: "Powered by Adobe Acrobat Sign" image and horizontal rule overlapping KBA options for Web Forms due to the CSS width being too small |
Fix: Removed web form styling so it behaves the same as for regular agreement. |
|
4481902/ 4471416 |
Summary: Form fields are duplicated when using Templates through Send in Bulk due to the field template being applied from the team plate and the authoring stage |
Fix: The process for applying the field template has added logic to account for the template fields if available. | |
4481984 |
Summary: Timeout exceptions can lead to Send in Bulk transactions to create duplicate agreements |
Fix: A check has been added to identify if a child agreement already exists for the parent transaction. | |
4482743 |
Summary: Error " SEND_IN_BULK_WITH_ADV_ACCOUNT_SHARING_ROLLOUT" when using Send in Bulk on the Sandbox due to a setting not being enabled |
Fix: The setting was enabled, and the error was resolved. | |
4482746 |
Summary: Error: The request provided is invalid, while adding alternate recipient due to strings being passed as empty values instead of null values |
Fix: While equating names of participants, we are replacing empty String with null. | |
4483022/ 4484322 |
Summary: Send in Bulk may return a blank page when a horizontal scroll bar is visible on the Templates table |
Fix: The rendering processing of the template has been improved to account for this use case. | |
4483680 |
Summary: Update REST API documentation for Post Webhook api to add the feature resourceId and GROUP scope |
Fix: The API Swagger documentation has been updated | |
4484234 |
Summary: When using a custom workflow with more than 25 recipients, an error is triggered due to a hard-coded limit of 25. |
Fix: The hard-coded limit has been removed and replaced with the appropriate variable for the tier of service | |
4486809 |
Summary: When "well-formatted" signatures are disabled, the signature field can be reduced on the final document such that some of the signature is cut off |
Fix: Left padding points have been implemented for the signature field when "well-formatted" signatures are disabled. | |
4489678/ 4494301 |
Summary: When canBeDelegated is missing from the mail context, typically on a Custom Email Template, a Null Point Error is thrown |
Fix: A check to determine if there is a null value has been added before calling methods that will throw the error. |
|
4490021 |
Summary: Unable to download a signed copy of the agreement from the post-sign message page, if the post-sign redirect URL is specified during agreement creation |
Fix: The link to download the agreement has been added to the post-sign page | |
4490903 |
Summary: Unable to fill Web Form due to pop-ups in mobile devices |
Fix: Updated the code not to show terms of use popup on focus for mobile case |
Production deployment: November 12, 2024
GovCloud deployment: November 19, 2024
Improved Functionality
- Restart Agreement - Allow recipients to reset the agreement's signature cycle back to the first recipient. Any previously filled fields will remember the field values as the new default value but can be edited by the recipient they are assigned to.
Available environments: Sandbox, Commercial, Government | Available tiers of service: Acrobat Sign Solutions | Configuration scope: Group, Account
- Share templates with multiple groups—Create one template and share it with one or more groups. Updating the template will propagate across all groups with which it has been shared.
Available environments: Sandbox, Commercial, Government | Available tiers of service: Acrobat Sign Solutions | Configuration scope: Group, Account
- Send in Bulk improvements:
- Government ID authentication - Send in Bulk now supports Government ID as a recipient authentication method.
- Delegator roles - The Delegator role has been added to the Send in Bulk list of roles when using a CSV file to add recipients.
- Government ID authentication - Send in Bulk now supports Government ID as a recipient authentication method.
Available environments: Sandbox, Commercial, Government | Available tiers of service: Acrobat Standard, Acrobat Pro, Acrobat Sign Solutions | Configuration scope: Group, Account
Review the new Send in Bulk documentation here >
- Clear indication of undelivered emails and SMS contacts - A new icon on the Manage page clearly indicates if there has been an issue when delivering a notification to a recipient, allowing the sender to understand and correct the bad email or phone number to get the agreement back on track.
Available environments: Sandbox, Commercial, Government | Available tiers of service: Acrobat Sign Solutions | Configuration scope: Not configurable
- eWitnessing is supported in parallel and hybrid signature workflows - Agreements that require parallel or hybrid signature flows can now utilize the eWitness recipient role.
Available environments: Sandbox, Commercial, Government | Available tiers of service: Acrobat Sign Solutions | Configuration scope: Group, Account
- Power Automate - Template selection from within the Manage page - Using the Power Automate Set-up Notification or Archive Agreement actions on the Manage page open a menu of templates in the right context panel, making it easier to create flows from existing agreements.
- This improvement is expected to be delivered after the November 12th launch date.
Available environments: Sandbox, Commercial | Available tiers of service: Acrobat Sign Solutions | Configuration scope: Group, Account
- Identity Check improvements - The Identity Check policy has been improved to allow for name matching through the user interface (not just API) and to allow for partial name matching.
Available environments: Sandbox, Commercial, Government | Available tiers of service: Acrobat Sign Solutions | Configuration scope: Group, Account
- Data Exports for Web form-based agreements - The Data Export option now has an additional data export for web form usage that includes new filters to help manage the signature process of web forms exclusively.
Available environments: Sandbox, Commercial | Available tiers of service: Acrobat Sign Solutions | Configuration scope: Available by default; Not configurable
- Expanded options to notify CC'd parties - CC'd parties can be associated with specific recipients to ensure notification happens to the right CC'd party at each stage of the agreement signature process.
Available environments: Sandbox, Commercial | Available tiers of service: Acrobat Sign Solutions | Configuration scope: Group, Account
- Add the agreement name and transaction ID to the footer of every page of an agreement - Enable an option to affix the agreement's Name and Transaction ID to the bottom right of every page of the transaction.
Available environments: Sandbox, Commercial, Government | Available tiers of service: Acrobat Sign Solutions | Configuration scope: Group, Account
- Authenticate the first signer of a web form using a digital identity - Configure web forms to authenticate the first signer using a digital identity when they initially access the web form's public link.
Available environments: Sandbox, Commercial, Government | Available tiers of service: Acrobat Sign Solutions | Configuration scope: Group, Account
- Mobile-friendly forms and agreements - Provide an additional view of agreements for mobile recipients that lists only the field within the agreement available to the recipient. Senders can arrange the field list as they like, and group fields into logical sections to help the signers move through the field input with a minimum of scrolling. Recipients have the option to view the mobile-friendly fields list or the original PDF view with the fields placed within the document content.
Note: This feature is not deployed with this release, but will be scheduled a few weeks later.
Available environments: Sandbox, Commercial | Available tiers of service: Acrobat Standard, Acrobat Pro, Acrobat Sign Solutions | Configuration scope: Group, Account
Experience Changes
- The Custom Workflow Designer has a label limit of 100 characters - The customizable label values in the Custom Workflow Designer (CWD) are now limited to 100 characters maximum. Pre-existing workflows will be impacted, triggering an error when the workflow is updated with an explicit error message indicating the problem, and outlining the offending label in red. The Workflow template must be updated in the CWD to ensure that labels don't exceed 100 characters before the template can be successfully updated. All new workflows will constrain the labels to 100 characters before they can be saved.
Note that preexisting workflows that contain a label with more than 100 characters can still be sent without error.
Mobile application updates
- Improved signer experience for the mobile web interface—Users of the mobile applications will have a new experience that better highlights the recipients' elements within the agreement. This environment is enabled through the same admin control that enables the new recipient experience for the desktop
Integrations
REST API/Webhook Updates
API and webhook updates for this release can be found in the Acrobat Sign API documentation.
- Updated API interface - The API Swagger documentation has been updated to a new version (OAS 3.1) that changes the overall appearance of the page. The content remains the same.
- New Webhook for when agreements are restarted - The Restart Agreement webhook AGREEMENT_RESTARTED has been added to support the event when a recipient restarts their agreement.
- The POST /agreements/{agreementId}/deliverableAccess endpoint has changed the API Category to PUBLIC instead of EXTERNAL_PARTNER.
Resolved Issues
Issue | Description |
---|---|
4469029 | Summary: Bad email settings error thrown in the Custom Workflow Designer |
Fix: The logic controlling the error has been improved. | |
4472759 | Summary: Inconsistent behavior between the new and classic send experience when using "Download and sign with Acrobat" and multiple digital signature fields. |
Fix: The classic send experience has been improved to match the new experience. | |
4474898 | Summary: Lag when loading Template data on the Manage page when group sharing is ON. |
Fix: Methods have been added to avoid repetitive database calls, improving load times. | |
4475508 | Summary: Unable to update user Group Via Rest Api V5 for users with an apostrophe in the name. |
Fix: Code improved to gracefully account for the character. | |
4476530 | Summary: Compose page shows incorrect reminder frequency when creating a draft agreement via the API and then navigating to the request signatures page. |
Fix: Logic was added to ensure that the proper object value is not unset, and if a null value is found, the inherited default value is used. | |
4478261 | Summary: Signer unable to complete digital signature using 'Intesi' Cloud Signature Provider on agreements consisting of multiple digital signature fields due to file size of signature images |
Fix: Unnecessary images have been removed from the request body. | |
4478970 | Summary: Agreements can be sent out using the wrong locale in the new Request Signature environment |
Fix: The logic that applies the localization value has been improved to ensure the right value is applied. | |
4479498 | Summary: Delegatees of an agreement could not have the nextToSign flag returned to False, if someone else signed the agreement |
Fix: The logic to update the flag has been improved. | |
4481738 | Summary: Recipients mentioned in parallel order at the end of the signature cycle are not getting encircled like other recipients who are also kept in parallel order |
Fix: The graphic is now applied to the last pairing. | |
4481761 | Summary: The custom workflow designer doesn't include the e-Witness role for recipients |
Fix: The role has been added. | |
4482080 | Summary: Users could see other users not in their group through account sharing menus. |
Fix: Content-sharing menus have been updated to observe the settings for user access levels. | |
4482094 | Summary: Viewing an agreement using OTP can cause an error after 5 views that the number of views has been exceeded. |
Fix: The code has been updated to use a new threshold value for the "views exceeded" error. | |
4483719 | Summary: When users who have their signing authority removed attempt to use Fill & Sign, an unexpected error is triggered. |
Fix: Code has been added to prevent users who don't have the authority to sign from accessing self-signing workflows. | |
4483914 | Summary: In a written signature flow, Signer 2 is unable to open the agreement when signer 1 uploads their document with 256-bit encryption. |
Fix: The digital certificates are now removed from the uploaded signed copy when signer 1 is uploading. | |
4483942/ 4488212 |
Summary: New Send in Bulk Authoring does not show all Shared Group Templates on the Send page due to an undersized fetch parameter. |
Fix: A larger pageSize query parameter has been added when fetching library documents. | |
4484039 | Summary: Text Fields with date validation formats are not saving for Acrobat form fields due to the None value being mishandled. |
Fix: Refactored the existing code that handles the "None" use case. | |
4484055 | Summary: Trying to change the TEXT FORMAT in authoring can produce an error message "An unexpected error has occurred. Would you like to reload the page to try again, or return home." |
Fix: New code has been added to manage the error condition and resume editing. | |
4485315 | Summary: Webform with calculated fields enters a repeating loading status due to too many recursive calls to the expression utility. |
Fix: Send resulted set of field names as a parameter except re-instantiating it each time when the method is called. | |
4485677 | Summary: Unable to sign a document from Adobe Sign iOS mobile application due to form fields with conditions not being returned in the GET API. |
Fix: The API was improved to properly manage the calculated values. | |
4486008 | Summary: Reminder emails were sent ignoring the backend setting SEND_REMINDER_EMAIL = false due to the inheritance ignoring the group setting. |
Fix: The code has been improved to reference the group-level setting. | |
4486155 | Summary: New Send in Bulk experience returns an error 'Column [Recipient_1:Auth_Type]: Invalid authorization type specified.' when using Acrobat Sign as the identity authentication method |
Fix: Updated documentation to clarify the CSV values. | |
4486276 | Summary: Required fields created from Acrobat are not required on Webforms because the logic between agreements and web forms is different, and their last participant values are different. |
Fix: Separated the logic to check if the agreement is based on a web form or not. | |
4486331 | Summary: The default text value In Web Form text fields is removed when the Signer is required to verify their email prior to viewing the form because the fields are cleared when the child copy is created. |
Fix: The field values will be fetched from the parent template's default values. | |
4486748 | Summary: The Template Filters are Not Filtering Properly because the group name in the agreement table is not updating properly. |
Fix: The agreement table is now updated with the latest info when details are changed. | |
4486767 | Summary: Download PDF Button is missing from Read Agreement View |
Fix: The graphic and functionality have been returned to the list of options | |
4486829 | Summary: The Account Administrator is listed as Group Admin on the Primary Group even when not explicitly set as Group Admin when Show Only Admins is selected. |
Fix: Improved the filtering to properly reflect the admin status. | |
4486863 | Summary: Emails are not getting triggered for shared notifications intermittently due to null pointer exceptions. |
Fix: Added null pointer checks to fix NullPointerExceptions that are causing emails not to be sent | |
4486893 | Summary: If an agreement is not exposed to the signer (due to backend settings being true), then the signer can sign the agreement but not decline it. |
Fix: Added a condition to check whether the signer should be allowed to decline the agreement or not | |
4486894 | Summary: Allowed IP Ranges can be blocked from adding new ranges due to incorrect property inheritance |
Fix: More granular arrays have been added to prevent data collisions from external parent objects. | |
4486919 | Summary: When group recipients are configured to notify, participant status is not updated to WAITING_FOR_OTHERS after signing. |
Fix: Code updated to ensure the whole participant set is updated when one recipient completes their action. | |
4486934/ 4496641 |
Summary: Calculated field loses formatting in final signed agreement/pdf, when signed in a locale using a comma as a decimal separator and one of the decimal digits is not zero |
Fix: The number formatting has been improved to manage the locale where the commas are used as a decimal separator. | |
4487113 | Summary: "Error marshaling data" occurs when applying a form field layer while editing a shared template due to an outdated null check . |
Fix: Removed the unused parameter and its null check from the method. Updated all calls to this method to reflect the new signature. | |
4487589 | Summary: AUTO_CANCELLED_CONVERSION_PROBLEM (COMMENT: PROJECT_TIMEOUT) due to stack overflow while combining PDF files. |
Fix: Improve code to detect XObject Form cycles and AcroForms without fields. | |
4488298 | Summary: Signature panel shows 'Edit' button even though no edit is allowed |
Fix: Conditions added to filter out the option when not available. | |
4488322 | Summary: The label is missing in a few agreements on GET /agreements/{agreementId}/documents API call due to it being set too early in the process |
Fix: The timing for applying the label has been updated. | |
4488449 | Summary: Any subject that includes a dot in the subject is treated as a link. |
Fix: The regex identification for the original template in the Subject line has been removed. | |
4488647 | Summary: GET /users is failing with "Some miscellaneous error has occurred" due to massive full table scans |
Fix: A condition to check for single-use users was removed. | |
4489025 | Summary: Sign then Send option not available in the new Request Signature experience. |
Fix: The functionality has been added. | |
4489028 | Summary: Web Forms section not visible under Account/Group settings for Developer accounts |
Fix: Web Forms have been added to the Developer Tier of service | |
4489132 | Summary: When EXPOSE_AGREEMENT_AFTER_SIGNING_ENABLED is TRUE, the signer is unable to delegate the agreement due to the API providing the wrong status. |
Fix: Updated the code to provide the correct response. | |
4489203/ 4489407 |
Summary: Unable to download form field data for library templates due to performance issues with templates and web forms. |
Fix: Refactored the fetching code to reduce the number of loops for the same object values. | |
4489539 | Summary: The Last Updated column shows a recent modified date but agreement has not been updated due to the column reflecting the last modified date value. |
Fix: LastUpdated column will now use Last Transaction Date instead. | |
4489666 | Summary: Repeatedly clicking the export user data button while the download operation is in progress can generate an excessive number of database queries. |
Fix: The export button is now disabled while the export is in progress, and re-enabled once the export is completed or if an error occurs. | |
4489708 | Summary: If an unverified signer's wet signature is uploaded by the sender, then an error is thrown, because Acrobat Sign is trying to verify the participant first |
Fix: Added a check for the sender's action to allow for this use case. | |
4489748 | Summary: The participant is unable to attach a file in the attachment field due to a conflict with the Content Security Policy. |
Fix: Added the documentcloud.adobe.com domain to the internal .jsp | |
4489806 | Summary: The SMS is getting sent to the recipient and the sender is receiving a false email for non-delivery of the SMS.when Custom Email Templates are used. |
Fix: Corrected the code that manages notifications to the email address when SMS is used. | |
4490094 | Summary: Exported form field data doesn't contain all data fields for agreements created via new Send in Bulk experience when the template was built in the previous version of Send in Bulk |
Fix: Improved the form export from the previous version template to the new environment. | |
4491200 | Summary: The Send in Bulk environment isn't displaying prefilled calculated date fields for recipients. |
Fix: The logic for how prefill fields are related to the child agreement(s) has been updated to ensure the prefill content is populated as expected. | |
4491429 | Summary: Unable to process payments if payment field is calculated field with a read-only field in the formula, but only when prefill fields are present in the agreement. |
Fix: Modify payment logic for prefill case to avoid setting default value for fields that are not present in prefill fields list (like read-only fields). | |
4491502 | Summary: Phone Authentication label text is not legible on smaller viewports |
Fix: The font size was increased to 13px. | |
4492386 | Summary: An increase in file size after Document Processing can cause issues with file size limitations. |
Fix: A new processing library has been put in place to improve the updated file size. | |
4493280 | Summary: Workflow "completed" emails were not delivered to some recipients due to conflicting roles (recipient and Cc'd party) |
Fix: New methods are provided to add logic to utilize the best participation role when multiple roles exist. | |
4493288 | Summary: Time zone does not show the legally correct text for some locales. |
Fix: Additional enum values have been added to the time zone selector to include the additional options. | |
4493570 | Summary: The option to limit access to agreements through the transaction number without login are not respecting group level settings. |
Fix: The setting has been redesigned to accept the groupId's value. | |
4493717 | Summary: Changing the field type for a field using the new authoring environment on the Edge browser causes flickering due to styling. |
Fix: The styling that causes the graphical flickering has been removed. | |
4494031 | Summary: Disabling the new authoring page in favor of the classic compose environment does not respect the configured settings. |
Fix: The authoring controller now uses the agreement originator's group membership and respects that group's settings accordingly. | |
4494284 | Summary: New authoring experience does not use the sending group setting for digital signature. It will use the setting from the primary group. |
Fix: The setting has been updated to respect the group configuration. | |
4496116 | Summary: Custom email display name from AGREEMENT_SEND_CUSTOM_FROM_EMAIL_DISPLAY_NAME setting is not shown |
Fix: Updated the macro that inserts the name value to use a more reliable source. | |
4496561 | Summary: The feature that enforces the setting to prevent users in a specific group from uploading documents from their computers isn't being respected at the group level. |
Fix: Code logic updated to respect group-level setting for local file upload when changing groups | |
4499981 | Summary: IP ranges UI display is not displaying the saved values nor any of the buttons is accessible due to the size of the div on the page. |
Fix: The size of the div has been increased to the height of the element. | |
4501353/ 4503262 |
Summary: Send in Bulk transactions intermittently send emails due to a null point exception. |
Fix: Logic added to help discover the sender's groupId and default to an empty string if unsuccessful. | |
4501414/ 4503383/ 4504559/ 4504619/ 4504658 |
Summary: The new Authoring environment displays fields for participants that aren't added to the agreement and may present error messages preventing authoring. |
Fix: Code has been added to ignore field placement for fields assigned to participants that aren't included in the agreement recipient list. | |
4501428/ 4503930 |
Summary: Signing is blocked when the recipient's name is not allowed to be edited during the signature process and:
|
Fix: Added a check to see if the name matches the saved user name in addition to existing checks. Bypass the check if the participation includes a digital signature field. Bypass the check for ADOBE_SIGN, KBA, and GOV_ID authentication types. | |
4501444 | Summary: Use "Next" instead of "Finish" for the mobile eSign view field navigation header button label when all required fields are completed. |
Fix: Button updated. | |
4501750 | Summary: Signing is prevented when a registered user changes their name and the setting allowing them to edit their name is disabled. |
Fix: Logic added to check the name against previous versions, if the signature includes a digital signature, and when using Acrobat Sign, GovID, and KBA authentication types | |
4502421 | Summary: The sender is being excluded from reminder recipients due to a change in the logic that filters recipients. |
Fix: The code has been reverted and the original logic has been restored. |