I went down the road of attaining finer control over the user experience when submitting a form or document, things like aborting the submit if the user responds negatively to a popup warning. The common wisdom seemed to be, "Instead of the LiveCycle submit button you need to use a simple button, do whatever scripting you want to do, and as the final step use the Acrobat API event.target.mailDoc() method."
I've tried that, and it does indeed work. However, I feel like the LiveCycle Submit button has a little better handle on actually orchestrating the dispatch of the form. Most significantly, the LiveCycle Submit button provides the popup with a radio button choice between desktop email and browser email, which I think is an important feature. I don't get that with the Acrobat API event.target.mailDoc().
So, here is my point. I'm wondering if I can have both... provide a simple button that does whatever fine-tuned scripting I want to do, and THEN it causes a LiveCycle email submission to fire?