• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 71
  • Last Modified:

Have PDF form recognize local machine -- else disable form fields.

In the past few days, a staff member (Let's name him Mr. Smith) from my unit has done nothing but frustrate both me and my supervisor in regards to the proper way of filling up our time off request form.  While its none of my business, with all of Mr Smith's time off requests, one would think he'd be an expert in filling up our time off form by now.  

Managerial problems aside. . . We've decided to create a form strictly for FMLA.

My dilemma: on this new form I'm creating, I want my supervisor to be able to approve multiple entries without having to affix her signature on each line, since it's tedious. I've decided that instead of signatures, when she clicks on either approved or (not) approved, the approval date gets populated.  To prevent people from falsifying approvals, I want the form to recognize the machine the approvals are being made, either by machine or by Windows Login ID.  While I can do CurrentUser() on VBA,  after doing research found out that unlike MS Office docs, identity.loginName is privileged scripting.

Instead of having to install the .js file on everyone's PCs to recognize the current user and catch the perpetrator trying to fake approvals, I thought it would be easier (and more ethical) for the form to just disable the fields when someone does attempt to.  I plan on installing the .js file on the PCs that are authorized to approve time offs.

I know basic Adobe form making (ooh textboxes. . .  buttons!) and small basic Java Scriplets.   I have some basic experience with LiveCycle. But I do not know where to start in regards to creating a js file, nor how to have the PDF form search for and require it for the fields to be enabled.

 As for Mr. Smith we're just basically waiting for him to finish his probation and finally give him the boot on the exit interview.
0
johnnieborgie
Asked:
johnnieborgie
1 Solution
 
Karl Heinz KremerCommented:
The only secure way to approve a form is by using a digital signature, you may want to look into that. This also would lock the form the way it was at the time the signature was applied.

If you want to stay away from an electronic signature, you can do what you proposed by adding a folder level script that e.g. defines a function to return the login ID of the user. During application initialization (which means in a folder level script), you do have access to the identity information, so you can create a trusted function that returns that.

To find out where such a folder level script goes, see this tutorial: http://khkonsulting.com/2010/12/acrobat-javascripts-where-do-they-go/

Do you have access to the Acrobat SDK? If not, that's essential for working with Acrobat's JavaScript:

http://help.adobe.com/livedocs/acrobat_sdk/11/Acrobat11_HTMLHelp/wwhelp/wwhimpl/js/html/wwhelp.htm?&accessible=true
0
 
johnnieborgieAuthor Commented:
Hi Karl,

Sorry for not replying back soon. . . I'm pressed on time with another project so I'm temporarily scrapping this one,  Thank you for your insight, will consider them once I've picked up this project again.
0

Featured Post

Upgrade your Question Security!

Add Premium security features to your question to ensure its privacy or anonymity. Learn more about your ability to control Question Security today.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now