eSign populating to end of document instead of pre-placed / pre-assigned fields

[MCBridges]

In the past, eSign fields worked properly: wherever I placed eSign fields, the signature was appropriately populated within the placed field exactly where they were initially placed.

For the past two months, when following an identical workflow, signatures populate within new fields at the end of the document, even when sending the eSign request to users with official (paid) Adobe accounts.

[Meenakshi Negi]

Hi MCBridges,

Thank you for reaching out, and sorry about the trouble caused.

Please share the workflow used and how you add the fields. Also, share a screenshot of how the signature fields populate. and the sample document so that we can reproduce the issue. We will check this once we get more information.

Feel free to let us know if you need any help.

Thanks,

Meenakshi

[MCBridges]

I have done extensive testing with multiple combinations, all resulting in the same endpoint/poor result. If desired, I am willing to screen share the process. Of note: Personal Settings = E-Signing Setting checked “Use the latest version…”

1. Four to five single-page PDFs are combined into a single document using “Combine Files”
   • Both “drag and drop” and file pick methods produce the same end result
2. One of the following two methods is used to request eSignatures (both methods fail)

      a.    Using Step 1’s document:

                    i.     Click “E-Sign” in top menu after step 1 completed

                    ii.     Click “Invite to e-sign”

                    iii.     Add Recipient 1 email and name, not requiring password

                    iv.     OPTIONAL click “Recipients must complete in order (doesn’t work when clicked on or off)

                    v.     Optional (also doesn’t work): Add Recipient 2 email and name, not requiring password

                    vi.     Use “Auto-place fields” to populate signature field(s) for Recipient 1 (followed by optional recipient

                              1.     ALTERNATIVE: manually drag and place “E-signature” field(s) in appropriate places (also doesn’t work)

                    vii.     Optional (also doesn’t work) place required Text field for recipient 2 to complete

                    viii.     Optional (also doesn’t work) change/edit agreement name

                    ix.     Click Send

                    x.     Recipient 1 experience:

                              1.     R1 opens the email and clicks “Review and sign.”

                              2.     R1 agrees to ToU & Consumer disclosure by clicking “Continue” (if not already completed previously)

                              3.     Originally-placed fields are not available or visible as options for signature, only two fields on the last page (one for R1 to complete and a blank one for R2)

                              4.     R1 clicks on “Click to Sign,” draws/types signature, then clicks “Apply”

                              5.     R1 clicks submit

                              6.     R1 receives message “You’ve signed successfully”

                    x.     Recipient 2's experience is nearly identical, with the exception below

                              1.     Originally-placed fields are not available or visible as options for signature, only two fields on the last page (one completed signature for R1 and one available for completion for R2)

3. Document is returned by signee(s) with only one signature per recipient (regardless of how many signature fields or required fields were placed) at the bottom of the newly-made-multipage document instead of in a pre-placed field

Uploading a multipage document without “combining” also doesn’t work.

Additional symptoms (which may or may not be related): The newly combined document and any opened using “E-Sign” are auto-downloading frequently throughout the process.

Example combined-PDF and screenshots of all users POVs included

[Mary25346032ken7]

Hello, I am having the same issue.  Placed properly within the document as I have done for years, now it is at the top of the page and reversed.  Sometimes it is on a seperate page at the end.  

[Meenakshi Negi]

Hi MCBridges  and Mary25346032ken7,

Thank you for sharing the information. 

Please let us know if you are experiencing this behavior with the web forms or the forms you send for signature individually. 

@Mary25346032ken7 It seems that you have a different issue. Please share the information asked for above and share the screenshots.

We will get the behavior checked.

Thanks,

Meenakshi

[MCBridges]

I have also tested when sending to a single user, and the same results: multiple downloads of the document during the document building/preparation process, the deletion/lack of signature & text fields once sent, and only a single signature field on the last page of the multi-page document. This is also identical if sent as a single-page document. The pre-placed signature field(s) is/are unavailable to use/see and only a duplicate of the signature fields we have seen on the last page of the multipage documents.

See additional information attached. I have trialed this with .org emails (corporate Outlook-based), @gmail.com, and @yahoo.com, all with identical results.

Of Note: During this most recent re-test to produce screenshots, a star rating for the signing experience splashed on the screen for only 1-2 seconds and then automatically moved to the "You've signed successfully" screen without letting the end user (person signing) rate the experience. So, if Adobe has had a low response rate lately for this star-rating question, this may be why.

[MCBridges]

Forgive me for the multiple reponses. I wanted to clarify that I have even tested this using both the    Adobe Home Screen -> hover over "E-Sign" -> click on "Request e-signatures" pathway    and the   Adobe Home Screen -> click on "E-Sign" -> click on "Request e-signatures" pathway. Both produce identical results.....I wouldn't think that alternate paths to the same function would produce different results, but I wanted to ensure that also was not a variable. 🙂

[S. S]

Hi @MCBridges,

Thanks for the descriptive response.

We will be sharing this with the development team and get back to you.

We request your kind understanding and patience while the team investigates and shares further updates.

Regards,
Souvik.