1 Reply Latest reply on May 20, 2013 5:10 AM by try67

    Problem with 'bUI: false' statement in automated pdf/email.




      I've recently created a PDF form in Livecycle Designer. This form is intended to be used by employee's in my company to request IT access. The submit button I placed on the form is a regular button with Javascript coding. This is meant to fire off emails to different support email addresses. A sample of the code is displayed below.


      var oDoc = event.target;

      bUI: false,
      cTo: Joe.Bloggs@email.com,
      cSubject: "New Starter IT Access",
      cMsg: "Please assign this request to Security Admin",


      Now, I used the 'bUI: false' statement as the email process may potentially fire off emails to several different teams, and I didn't want the end user that is filling the form to have to click on the Outlook 'Send' button several times. I've tested the form in Adobe Acrobat X and this send's off the silent emails with the form successfully.


      However when I tested with Adobe Reader 9.4 (Which all of our end user's have & Win 7), the 'bUI: false' statement is ignored and multiple Outlook message windows appear with the form attached.


      This is definately no good and I've spent a long time creating this complex form only to get stuck on the final hurdle.


      I've seen on the Net and via the forum that there have been suggestions on using a locally saved Javascript file with the a privileged function, however I am a little stumped by this, and to be honest we have over a thousand employee's in our company and this would not be a working solution.


      Does ANYONE have a solution to this that can be codes within the button rather than using a local .js file.



        • 1. Re: Problem with 'bUI: false' statement in automated pdf/email.
          try67 MVP & Adobe Community Professional

          You're out of luck... As the reference for this method states (see the Note):

          bUI (optional) If true (the default), the rest of the parameters are used in a

          compose-new-message window that is displayed to the user. If false, the cTo

          parameter is required and all others are optional.

          Note: (Acrobat 7.0) When this method is executed in a non-privileged context, the

          bUI parameter is not honored and defaults to true. See Privileged versus

          non-privileged context.

          It would be a huge security risk if a PDF could just send emails without any user consent or action...

          Using a local JS file (or certifiying the PDF) are your only options to silently send an email.