Hi to all ...
I am back to my beloved thread, looking for information on how to implement new certain requirements...
I have upgraded to new LiveCycle Desinger 8.1 few days ago, and still do not know all the new features.
I was requested to develop new LiveCycle Form, but this time it has to be secured by Digital Signatures or what every appropriate method.
The form has exactly 2 sections and 2 Digital Signatures:
1. The first section/part is to be filled by the Staff (let us call him the Authoring Staff).
Any one can fill the first part.
After the first part is signed, the Data Entry on the first part should be locked, and no one on Earth should be able to change the data on the first part. Only the signer of the first part is allowed to update/clear the signature but only and only of the Second part is not yet signed.
The staff should not be allowed to sign the form unless all mandatory fields and other validation logic is statisfied.
Only the Signer of the Form and special authorized staff/group of staff will be allowed to open the form. Let us call them Group01.
2. The second section/part is to be filled by special authorized staff/group (say Group02), they are basicall HR Staff (this is a secret).
The second part can only be filled if the first part is filled and signed by the Authoring Staff.
The second part can be signed only if the validation logic on the second part is true (no errors, and all mandatory fields are filled).
Once the second part is signed, the first part the the second part should be locked, and no one on earth should be able to change anything on the form.
Only the signer of the form should be able to clear the signature of the 2nd part and make any changes requried.
If the 2nd part is signed, the Authoring Staff should not be able to change anything on the form.
*****End of Requirements.*****
I have just started, and I am requested to desing the form and implement the required security in 10 days only.
Can any one please help me ?
I am doing my research now.
I am really thankful to you for initiating this thread; I printed all the 50 pages of this thread and went through them over a 2 hour reading. Thanks for being not only an initiator but the major active contributor to this thread. Actually, I am not replying to your question addressed in the thread but asking for some inputs from you.
Just FYI; I have worked with LC designer 8.1 for more than a year now. I have developed a few Dynamic XML PDF forms which use ODBC connecting option to pull data from MS Access DB ( all client based) to publish the same on the PDF. This app was a 2-Tier approach.
My current requirement:
I need to develop the ASP.NET version of the same form developed by me earlier in 2008 so that I can publish this form over an IIS for everyone over the internet to use the form on-demand. I will use a .NET application to accept the Input Parameters (Request) for which the data needs to be fetched from DB and published in the PDF form (over the browser). The final PDF published in the web browser needs to be saved in a WORD document since the clients cannot afford Adobe Acrobat in every client.
My Limitations: My case is similar to all the limitations mentioned in this thread. Budget does not permit the following.
1. Cannot buy or install Adobe Reader Extension Server in the Server.
2. Cannot buy or install Adobe Livecycle Designer ES or Adobe Livecycle Forms.
3. Cannot buy or install Adobe Acrobat Pro in all the clients
4. No third party tools are allowed to be installed in the client for any export import purposes.
Only Adobe Reader 9.0 is allowed for all the clients. All clients will have MS office for sure.
1. My complete technical design of the data flow depends on the contained object (PDF form or plain HTML form) rendered in the web browser. The contained object should allow me to save the form embedded in the browser into Word format (saved in the client). Also the word form saved here should have editable form controls for further edits in the manual workflow. I love to use Adobe Livecycle designer since the form look and feel is absolutely great. Do you think I am just trying to waste time? I strongly feel forms are best looking in Adobe LC designer. Do you think I still can use this tool to achieve what I want?
2. Do you think I should just forget about Livecycle and design a pure Visual Studio form or MS Word Form and be done with export to word using some APIs published by Microsoft?
2. Also a question answered by you to PIRZADA from your earlier thread dated June 29 2008. You had mentioned that you were planning to develop .NET Class wrapper for the form submission, initiation and Processing. Do you have that class published anywhere? Or could you please share that to this forum.
I would also appreciate if PIRZADA or anyone like Jeff Lawrence or Vidya could comment on my requirement and suggest an approach or examine my appraoch.
I am really happy to know that this thread was of value to you.
Here are my quick answers to your questions:
1. Use Adobe Platofrom only if the following criteria is applicable to your situaiton:
- You can afford the cost of Implementation. You can use Adobe LRES which is the ultimate solution and very costly. Or, you can use Single Adobe Acrobat 9 version and Reader Enable the LiveCycle Form on the Server and will give about 70% of the feature provided by Adobe LRES.
- You want to have a ture Paper Replacement and provide the end user with an electronic form in PDF that will take advantage of PDF Security and all the pther features such as annotations ...etc. For example, if the users does not want to save an off-line copy of the form on his PC and does not care about the authenticity of the form, then there is no need for PDF.
- Ability to use the form accross all platforms and reduce the problem of compatibility issues.
- To use Digital Signature, not only to secure the form, but to keep track of all the versions and changes made inside the PDF.
- You need to secure different parts of the form according to the authenticated user (the new requirements I posted in my previous thread). As a matter of fact, this is really a great feature, which I found a solution for.
2. Use HTML Form, aspx Form, or MS Word Doc (rendered on the client from the server), if the above criteria does not apply to you.
3. Yes, I have developed the .NET Class Wrapper, and it was really greate. This new class, not only it will make development easier, also, it will allow me to generate large number of PDFs, and cach the result in Text File (instead of String Variable), to be pushed back to the client (download via response.write) at the end. I will publish the class as soon as I am back form my vacation on 10-Aug-2009. Please send me a reminder if you do not mind.
Thank you very much for your quick response.
Now, to respond to you...
Customer cannot afford Adobe LRES at this point of time. I must tell you, at the outset that the form I am working on is a standard form and the look and feel of it should be so close to the paper form. That is the purpose why we chose Livecycle Designer in the first place. So to answer you, specifically, YES! I want to have pure paper replacement as much as possible ( say 70% close to the original paper form). Customer is willing to live with what I give as web-enabled electronic form but I want to give my best. I know HTML form/ASPX form is anyways known options
So I want to go with what you have told in the first point. to quote you "Or, you can use Single Adobe Acrobat 9 version and Reader Enable the LiveCycle Form on the Server and will give about 70% of the feature provided by Adobe LRES." I hope this means that the I can install and use Single user Adobe Acrobat 9 Professional version (WHICH INCLUDES LC DESIGNER) at the server and Reader Enable the Livecycle form. Yes I can do this. However I need to always remember that any form shown with values on the broswer should be editable and, I should be able to save the browser form into a word document.
Now my question: Using your idea I came out with the following logic. will this logic work?
Step 1: Accept Key input params from the user using a .NET application (request object). User submits the data
Step 2: Fetch the relevant form data (data sets) from the database for the INPUT params
Step 3: Programmatically Generate instance(s) of the PDF (I call it generated PDF(s)) using the LC designer PDF form by populating the fetched data (sometimes this generation could result in a multi-page form and/or multiple instances of the form)
Step 4: Store the generated PDF(s) in a SOURCE folder inside the server
Step 5: Reader Enable the generated PDF(s) "programmatically" using the SINGLE ACROBAT 9 Professional installed in the server( This is your idea!!!!!)
Step 6: Store the Reader Enabled generated PDF in a DESTINATION folder
Step 7: Now show the browser (response object) with Reader Enabled generated PDF extracted from the DESTINATION folder
Step 8: Now from the web broswer allow save of this form into MS-Word ( how this will happen - donot know now..hmm I need to test it out)
Please feel free to criticize if any of the steps mentioned above is beyond your imagination. If I am sounding too abstract for you, please feel free to comment. I would wait for your valuable feedback. In the meanwhile let me do a Hello world run of the whole logic to test it out. Shall keep you posted.
Besides. I will, for sure, remind you after Aug 10, 2009 regarding the class you will be publish it for this group