Adobe Acrobat Sign Release Notes

Keresés

Utoljára frissítve: 2024. aug. 13.

Megjegyzés:

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

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

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

Production deployment: August 13, 2024

GovCloud deployment: August 15, 2024

Improved Functionality

Power Automate access points on the Manage page—The Manage page now has new links to the Power Automate Template Gallery, which makes it easier to access.
- The In Progress filter provides a link to the Notification templates.
- The Completed filter provides a link to the Archival templates.

Links are exposed in the ellipsis to the right of the filter label and in the list of available Actions for any individually selected agreement.

Available environments: Commercial | Available tiers of service: Enterprise | Configuration scope: Enabled by default; No configuration

Review the documentation for the new Power Automate links >

Megjegyzés:

The above feature to insert Power Automate links into the Manage page was released on July 25, 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:

The new post signing page showing the four actions the recipient can take to try Adobe products

Megjegyzés:

Countries with stricter communication laws will not display the four "Try now" offers. Those countries are currently:

Belgium
Canada
Germany
Slovenia
South Korea

This list of countries may change as local regal requirements change.

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.

The post-signing page for unregistered recipients that have exceptions from their signing environment

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:

The post-signing page for registered recipients

Available environments: Sandbox, Commercial | Available tiers of service: Individual, Teams, 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."

An example of the email delivered to a recipient requiring Phone/SMS authentication.

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

REST API/Webhook Updates

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

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
- Agreement Participant Info needs to be checked in the Notification Parameters for userId to appear in the Webhook notification payload.
authenticationMethod - The authentication method used for the participants to have access to view and sign the agreement.
- Agreement Participant Info needs to be checked in the Notification Parameters for authenticationMethod to appear in the Webhook notification payload.
createdGroupId – The ID of the group from which the webhook was created.
- Agreement Info needs to be checked in the Notification Parameters for createdGroupId to appear in the Webhook notification payload.

The "Create" panel for a webhook with the Agreement Info parameter checked.

Resolved Issues

Issue	Description
4465123	Summary: Using SSO authentication may result in "review and Sign" emails having faulty hyperlinks.
4465123	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.
4479831	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.
4479994	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.
4483513	Fix: The code has been updated to properly manage the use case of an apostrophe in the Display Email field.