When clicking "Send for Signature" how do I get it to open in EchoSign first so I can place signature fields?

Question

It seems Acrobat Pro XI recently updated and now when I chose to send for signature via echo sign, it just ships the doc off to the recipient willy-nilly with out asking what other fields I may want input, where I may want to sign myself (upon first getting a signature from the other party).  I can of course open the Echo Sign page in my browser, then upload the document, then do all of this, but Acrobat was uploading to Echo Sign and allowing me to skip a few steps.  Are there some preferences I can adjust to change the behavior back to the procedure that was in place previously?

Answer 1

The above noted problems remain.
And to add to it, there also seems a problem with having a pdf and then, in acrobat, allowing one to sign the document first via in echosign before it is delivered to someone else, in echosign, where all parties have a paid echosign account.  There doesn't seem to be a way to sign via echosign in acrobat.  Acrobat will route a document to a echosign like system, but it is NOT the full featured system that one sees with an echosign account.  It is as if the two services are completely unrelated.
One solution is to save the pdf to desktop.  Then, open the web browser and echosign.  Then drag the file from the desktop into echosign, and go from there.  The drag feature works really well, except you cannot drag a pdf file is an attachment to an email into echosign, as that is not supported.  You must first drag it to the desktop, then drag into echosign.
While this solves the problem this is NOT integrating Echosign with Adobe Acrobat Pro XI, as advertised, and it is no different from any other version of Adobe.  Thus, if you are like me and considering buying the latest version of Adobe Pro for use with Echosign, don't as it is a waste of money.  I will update when this issue is fixed.
BTW - support in Echosign says that it has no influence over how Adobe Acrobat implements Echosign and directed me to contact Acrobat.  The problem, of course, is that it did work well, then Acrobat changed it without notice, doesn't appear willing or able to fix it, explain a workaround, or otherwise acknowledge that a change was made.  This is not a cheap product and the incremental improvements for a mature product do not seem to implemented well.
DAG