Adobe DC eSign widget - users are abandoning form after completing signature

  • Profile Image
    Asked on June 05, 2015 at 05:39 AM

    I have a form which asks users to attached documents, I also use the Adobe DC eSign Services widget. Clicking ‘sign with adobe esign means’ gets the document signed etc. however because the form submit button is not clicked the attachments don’t get attached and submitted with the final document. 

    Asking users to use the submit button would mean the Adobe DC eSign Services widget gets skipped altogether. 

  • Profile Image
    Answered on June 05, 2015 at 01:04 PM


    You can check the screenshots shown in this widget page of Adobe DC eSign Services:

    Based from my understanding and the screenshots shown, they'll need to sign in to Adobe Document Cloud eSign Account, close the Adobe window and then click the submit button. It is part of the process. 

    You can check it on our blog post here: There's also a video explaining the process. 

    I hope that helps.

    Thank you.

  • Profile Image
    Answered on July 03, 2015 at 10:50 AM


    they'll need to sign in to Adobe Document Cloud eSign Account, close the Adobe window and then click the submit button

    By following this procedure we are finding people are not going back to the page and pressing SUBMIT, therefore we are not receiving the attachments. Is there any way I can show the ADOBE widget after submit has been pressed.




  • Profile Image
    Answered on July 03, 2015 at 12:12 PM


    I believe this is how the widget is designed, they need to sign in their Adobe account then sign it, they will need to close the Adobe window and they should be back to the form again.

    If you want, I have a workaround in mind.

    You can create two forms.

    Form 1: This is the main form, this is where all the text field and information you need form the client is filled out.

    Form 2: This form is solely for the widget Adobe DC eSign Services.


    Workflow process:

    1. User fills out Form 1

    2. After clicking submit button the user is redirected to Form 2

    3. User then need to sign the Adobe DC eSign Services here.

    4. He/she needs to still submit Form 2 to be successful.


    The good thing with this process is that you already have the main information from Form 1. If the user did not submit Form 2, you can easily contact that person based from his/her submission in Form 2.

    How to set this up.

    1. I've made 2 Forms. Form 1 has a widget named Unique ID, I want to pass this to Form 2 so that I can easily cross match the submissions.

    2. I will then setup my Form 2. In addition, this is where you will add the Adobe DC eSign services widget. I also added a plain text box for the Unique ID, I will prepopulate the value of this from Form 1.

    3. To prepopulate Form 2, you need to get the field name. To learn more about Prepopulating a Form, you can check this guide: 



    4. In your Form 1, change the "Thank You" custom URL to Form 2's URL.

    This is the URL that I will input there:{uniqueId}


    Blue highlight: This is Form 2's URL but we added "?"

    Green highlight: This is Form 1's Unique ID widget name.

    Yellow highlight: This is Form 2's Plain text box field name BUT we wrapped it in {} 



    You can test my sample form here: See how it works. You can also pass other values, not necessarily a unique ID. You can pass the full name of the user from Form 1 instead.

    I hope somehow that helps. Do let us know if you need more information on this.



  • Profile Image
    Answered on July 06, 2015 at 05:35 AM


    Can you please show me to do this on my form; I think I know what you are trying to say.  I have created to forms below. I’d be grateful of you can show me how it will work with my form.



  • Profile Image
    Answered on July 06, 2015 at 09:07 AM

    Or, you can put a note before the Adobe DC eSign widget that would tell the user to sign up, close and submit the form. I think this is the easiest you can do. I'm sure that would make sense to the users.

    But as explained by my colleague, you have to create a new form (2nd form) and add the textbox field and eSign widget there. The textbox field will be filled based on the generated ID in the first form - through URL parameters.

    Here are sample forms: (This is a cloned version of your form)

    This is my new form ( with only the eSign widget and Unique ID.

    Submit to the first form, you will be redirected to the second form to sign in the widget and submit it.

    The method is again to capture the information in the first form and sign into the widget into the new form.

    Let us know if you need further assistance.


  • Profile Image
    Answered on July 08, 2015 at 05:03 AM

    Hi, sorry, I can’t work out how to pre-populate the form and how to link the form with just the widget 

  • Profile Image
    Answered on July 08, 2015 at 09:55 AM


    The primary purpose of the Adobe DC eSign widget is to 

    1. Capture the form as it was filled

    2. Submit the information to Adobe DC (echosign)  - where a signature will be legally assigned

    3. Return the user to the form for completion. 

    I think step 3 still needs a little work. 

    On the suggested workaround by my colleagues, whatever the users will sign on the second form should have all the information entered on the first form - which will make prepopulation incredibly tedious (possible, but it will involve a few hours of debugging to get everything right). 

    I'm going to raise a feature request to the widget team to consider the following feature for implementation:

    1. User completes the form and enters their details into Adobe DC esign  - clicks to sign

    2. User completes the signature and returns to the form

    3. The form automatically submits. 

    We will update you on any progress via this thread. 

    In the meantime, please add a similar note on your form: 

    "After completing the signing process, close the widow as instructed and click on "submit" to complete application"

  • Profile Image
    Answered on July 28, 2015 at 05:28 AM

    Hello, any updates on the feature?

  • Profile Image
    Answered on July 28, 2015 at 09:23 AM

    Upon checking the status of the ticket, it is still assigned to one of our developers as a feature request. I'll notify the widget team if there's any news on the progress of this.

    We'll update you on this thread as soon as we hear anything.

    Thank you.