Adobe forms Reader ext.

[sawedoff]

OK, I have looked through thread223-853888, and the extended comments on confusing product info, and while I agree it is confusing, I wasn't able to find the answer to my question in your answers either.

I am looking for a product that can take existing paper forms, created with text and graphics as Adobe pdfs, turn them into forms which can be filled out online, or downloaded, filled in and emailed, printed, saved onto local machines, all without requiring the user to have additional software (other than Reader.) The additional clink in the works is that the users need to be able to highlight and annotate parts of the form.

Any suggestions?

Thanks

Sawedoff

 

[tgreer]

It doesn't exist. At some point, a human must build the form fields, form actions, validations, etc.



Thomas D. Greer

http://www.tgreer.com

Providing PostScript & PDF
Training, Development & Consulting

 

[sawedoff]

OK,I guess I didn't make that part clear.

We accept the design phase as necessary, but I just wanted to note that we will be starting with existing pdfs.

We need to take existing pdfs, redesign somewhat to add form fields, and actions etc, THEN be able to have them downloaded, saved, filled out, highlighted, annotated, etc. and emailed or submitted. We have found a couple of solutions, but either got hung up on the email requirement, or the highlight and annotate part.

The completed form should become a separate pdf file, capable of being stored, printed, and transmitted electronically, via email.

Thanks.

Sawedoff

 

[tgreer]

Everyone in the process will either need the FULL VERSION of Acrobat (Reader will not work), or you must use the Adobe Live Cycle Reader Extensions to author your forms.

I would suggest that the forms be stored on a web-server. Users would fill out and submit the form to the server.

The server would do all processing, including emailing or serving-back, the completed PDF.

I think you'll find that the money spent on developing the web application is less than you'd pay Adobe if you go the LiveCycle route.



Thomas D. Greer

http://www.tgreer.com

Providing PostScript & PDF
Training, Development & Consulting

 

[sawedoff]

We can't leave them on the web server, due to the fact that our customers would download and save them to their own PCs, and would prefer to email them back when they are finished. Then often they are modified and emailed back to the customer, etc.

How much is the Live Cycle Extensions package, and would it do what we want? I can't find a price on their website.

Sawedoff

 

[tgreer]

Last I checked, it was a metered application. You pay to produce a certain number of PDFs. Then pay more when you need more. Or, you could pay a one-time fee for unlimited forms.

You have to call to have a sales representative visit you to design the most lucrative err, I mean, most beneficial license structure.

In other words, big bucks.

In a web-based solution, the users could certainly save local copies. They could even fill them out in Reader, and click "submit". Reader would automatically connect to the internet and submit the form.

Once the data is on the server, you can do whatever you like with it. Including, email the data and/or "final" PDF to the user.

Here are a couple of articles on the topic:

http://www.tgreer.com/pdfSubmit.html

http://www.tgreer.com/fdfServe.html

You could also use a 3rd party forms service, such as:

http://www.formrouter.com/pdf/index.html

Thomas D. Greer

http://www.tgreer.com

Providing PostScript & PDF
Training, Development & Consulting

 

[sawedoff]

We are much more interested in having the forms emailed back to our sales reps, since every time it would go to a web server, it would have to be routed to the proper sales person. Although some customers download the forms from the web, most then keep a copy on their PC and just fill it in and email it back when they are ready to reorder form us.

So having a repository for submitted data is not an issue. How the forms behave after being completed is the issue. We would prefer them to be just another file that can be attached to an email. Although with some the Submit button would be a nice addition, it is certainly not a necessity.

Thanks for the info, I will pass it on and see what others think.

Sawedoff

 

[tgreer]

I'm saying that the entire process could be automated by means of a web server application. Including routing the data to the correct salesperson.



Thomas D. Greer

http://www.tgreer.com

Providing PostScript & PDF
Training, Development & Consulting

 

[tgreer]

Trust me, I've done this before. One application I was involved in was for a phonebook sales force automation project. The contracts were PDFs. They were filled onsite, and submitted to a central server. The data was processed, and the final contract emailed back to the customer.



Thomas D. Greer

http://www.tgreer.com

Providing PostScript & PDF
Training, Development & Consulting

 

[sawedoff]

But can the dealer actually email it directly to us, or does it have to be emailed via an "EMAIL" button or "SUBMIT" button? in otherwords, can it be just a file on someone's desktop that they can attach to an email?

Sawedoff

 

[tgreer]

No. Reader won't let you save forms. You submit the data. That's the most efficient way to handle it. You would eliminate all the overhead of the PDF itself.

Plus it's much cleaner. Instead of:

1) Fill out the form
2) Save
3) Open Email
4) Enter recipient, title, message
5) Attach PDF
6) Send email
7) Wonder if you really got the email
8) Wait for a response

The process would be

1) Fill out the form
2) click "submit"
3) get instant response



Thomas D. Greer

http://www.tgreer.com

Providing PostScript & PDF
Training, Development & Consulting

 

[sawedoff]

And what if the salesperson receiving the form wants to send it back to you for revision?

Sawedoff

 

[tgreer]

He can do so. Just email it, if you must. When the user gets it, he fills it out and re-submits.

I'm not saying this is trivial. I'm just advocating that you program the functionality through a web application, instead of spending big big bucks with Adobe.



Thomas D. Greer

http://www.tgreer.com

Providing PostScript & PDF
Training, Development & Consulting