Last updated on
Sep 13, 2024
Missing elements in the new e-signing experience
The new e-signing experience supports most of the features used when sending agreements, but not all of them. The experience is still in development, and updates can be expected in future releases.
If the new experience is enabled and an unsupported element is involved, Acrobat Sign will fall back to the classic e-sign experience, allowing the recipient to complete their portion of the agreement with no issues.
We encourage administrators to use the new experience when they become comfortable with how the experience functions.
For your awareness, the differences between the classic e-sign experience and the new are:
|
|
Supported elements |
Unsupported elements |
|---|---|---|
|
Signer Roles |
|
|
|
Form Fields |
|
|
|
Signer Authentication |
None of them |
|
|
Agreement Type |
|
|
|
Implicit Consent |
|
|
|
Signer Actions |
|
|
|
Additional Functionalities |
|
|
|
Integrations and Embedded experiences |
|
Removed elements in the new e-signing experience
As the new e-signing experience evolves, some elements will be eliminated due to improvements in processes or technology. Below are the removed elements identified:
Read Agreement - The Read Agreement option existed to present a PDF that was accessible for screen readers. In the new experience, the screen-readable PDF is presented immediately, so the Option is no longer warranted.