[Thread Edited By Adobe]
/*Don’t forget to meet and greet your fellow peers virtually by telling them about yourself here.
Go ahead and to it now: https://adobe.ly/3eDnB4v */
I've created a form in LiveCycle which will be seen and filled by users who only have Reader.
Once the form is completed, the user has to click three buttons: one prints the page (for a specific paper-based usage required by the filler of the form). The same button sends the entire form to one e-mail address.
The second button prepares the form for submission to a second e-mail recipient. This recipient must not be able to see some of the filled fields on the form. As well as setting these fields to invisible, the second button also hides key fields behind a text message, telling the second recipient where to find the information that is most useful to them on the form. Again, this recipient will be using only Acrobat Reader.
Everything works fine, apart from when it comes to e-mailing the form to the second recipient. I've used various scripts I've found on this forum and elsewhere to lock fields before sending and I've extended Reader rights in Acrobat. But, whatever I do, the form received by the recipients is STILL editable, the "invisible" fields are visible again and also editable, and the test box that obscured key fields has become invisible again.
I've already tried using a range of scripts that I've found both on this forum and elsewhere (including Paul Guerrett's 'Lock All Fields' and 'Lock All Fields Not Buttons' scripts. I've also tried using the scripts in different 'events' - mouse up, mouse down, click etc.
What am I doing wrong? I've spent days trying to figure this out and I'm getting nowhere.
I know that this solution isn't a simple button press, but it's what i do when I don't want users to be able to edit a completed form.
I use a virtual printer ('Adobe PDF' or 'CutePDF') to "print" the form to a new flattened pdf document. All scripts are lost, and all fields are made 100% uneditable. No fancy code required, and you can make use of '.relevant = "-print"' in the initialize event of fields that you don't want to include in the printed version. You can then email this printed version the the client.
I've tried a handful of scripts to lock down forms, and I've even written my own. None of them have been perfect, and while this solution does have a manual aspect, it just feels so much cleaner to me.
Just my two cents,