Copy link to clipboard
Copied
Greetings,
PRODUCT:
"Adobe for Teams" -> E-Sign
GOAL:
My use case is to offer a web-form via a QR code or static link for all new employees to fill out a form when hired.
PREMISE:
Web-Forms seem ideal for this in every way, except that signers' names are not captured reliably on the signature capture screen.
PROBLEM (SPECIFICS):
When Adobe Acrobat E-Sign Web form prompts for the user to type their signature, it only provides a single box and assumes that everything before the first space is their first name and that everything after the first space is their last name. This is not correct when a signer decides to include their middle name for their signature. When a middle name is present in the typed signature box and the web-form's creator has included fields in the form designated as "Signer Info Fields" to display the signer's "Name" with the "Name Style" option of "Last Name", then the field will display both the signer's middle name and last name in the form's "Last Name" box. When such a form is publicly standardized and we do not have the option to change the form label from "Last Name" to "Middle and/or Last name" (which would be strange), then users do not understand why their middle name is showing up in front of their last name.
EXAMPLE:
SOLUTION:
Adobe should include a 3-box system for signature capture window so as to include a box for "First Name", a box for "Middle Name (Optional)", and a box for "Last Name". This would remove any last name ambiguity.
TEMPORARY WORKAROUND:
The only workaround for this issue seems to be temporarily using a "Data Field" on the web-form instead of a "Signer Info Field". However, using a "Data Field" for name requires that the user must manually type their names into every box throughout the form when there is already a built-in feature to claiming (and failing) to provide this service. This experience diminishes the convenience and value of using the Acrobat Web-From.
CLOSING NOTE:
Using this temporary workaround is not the same as a solution to an existing problem with the product offered by Adobe.
*If anyone else has observed this issue or overcome it in a better way, please comment to let me know, but be aware that pre-filling and addressing a new agreement for every new user needing to fill it out will not be practical for our use case and fails to acknowledge the existing issue with the product offering. Adobe Support has been extremely hesitant to acknowledge this issue during my support interactions. They've only made a couple suggestions that seem to illustrate that they do not comprehend this issue with the existing signature capture dialogue.
Thank you all for your attention to this matter.
Have something to add?