I’ve been reading through the Adobe forums as well as other areas on the net, but can’t seem to find what I am looking for.
At present we are doing the below:
We want to minimize some steps here to make it easier for the users as well as make the form more organized.
Below is what we are trying to accomplish with this form.
So what I am looking for is a way for the first user to lock the editable fields once they are completed filling them in, course except for the signature fields which are about 10 of them.
Can anyone give me some advice on how to accomplish this? Please do note that I am working with “Adobe Livecycle Designer ES2” as well as “Acrobat X Professional”. Would also be good to mention that I knew nothing of LiveCycle until about an hour ago. So I am very new on how this works. My knowledge on Acrobat Professional I would say is between average to advanced.
digging up an old thread sorry.
this looks exactly like what i need, i am new to Adobe, can i how you use the info you have provided?
i have just finished large optioned 3 page form for wheelchair manufacturing. i want clients to be able to sign off on teh details once funding is approved, but when i use adobe sign, it leaves all options open for changes.
any help would be greatly appreciated.
MinusZero's approach will work, however if there are may fields on the document that needs to be locked this would take an unnecessarily long script.
I would simplify it with:
xfa.resolveNode("form1").access = "protected" // this will protect the whole document
signaturefield1.access = "open" // this will reopen and ensure the signature field remains sign-able
button1.presence = "hidden" // this will hide the button
It is far simpler than you think. I also use ES2.
To be sure, you want to lock the fields and then have the signatures unlocked.
Firstly locking the fields.
Create a button and on the click event add:
In this example. there would be no way to unlock the fields again because the button disappears. You would hide a button somewhere else on the form to unlock if you wish. The access would be "open" to enable the field again.
For the signature fields, change this setting in the final signature to completely lock down the form. Uncheck the box for all the preceeding signatures so the form stays open.
Incidentally, the drop down box has a setting to manage which fields are locked on signing, you can select specific fields for locking out while excluding others.
If you like, for the preceeding signatures, add a postSign event to lock down that single signature without locking the whole form.
-Fields are locked with button which is hidden
-First signature field is signed and locked while others stay open.
If you've never used Designer at all then you should probably look at some of the tutorials that come with it.
If you have the time I recommend getting J.P. Terry's book Creating Dynamic Forms with Adobe LiveCycle Designer, it's what got me started using Designer properly. http://www.amazon.com/Creating-Dynamic-Forms-LiveCycle-Designer/dp/0321509870/ref=ntt_at_ep_dpt_1
There are some good tutorials on Niall's site (linked above) and some good video tutorials here: http://truetechtroubleshooting.blogspot.com/
Basically, if you're looking at Niall's example, the code is on the Click event of the "Lock all Fields" button which calls a Script Object (under Variables in the Hierarchy) called AssureDynamics. You need the script editor open so you can see what's going on Window>Script Editor or ctrl-shift-F5 to open it.
I don't think there's an easy way to copy Script Objects between documents, so you would need to insert a Script Object into your Hierarchy (right-click the topmost node in the hierarchy - probably "form1" and select Insert Script Object). Rename it to match "AssureDynamics" and then copy and paste the code from the Script Object in Niall's form into the Script Object in your form. You could then just copy and paste the button from Niall's form into your form.
Check this example by Niall O'Donovan: http://www.assuredynamics.com/index.php/portfolio/lock-all-fields/
It has the script for locking all fields. Basically once that script runs you can add a few extra lines of code that explicitly open access to the fields you want to remain open. ( fieldName.access = "open"; )