I have access to a web page that is connected to an Oracle AS report services database.
There are a few fields and drop down boxes to add in filters like date ranges etc
After everything is filled in you hit a button named submit and then a save dialog box comes up, asking you to pick a location where you want the results of your query saved (in excel format)
Id like to pull this button apart so I can insert the code into an access database. This will save users having to go to this webpage all the time and can just stay in the database they are working in.
Looking at the source of the web page there is a bit of javascript but I can't really see how the query parameters are being passed to oracle.
I can see the web address which is like www.servername.com/reports/rwservlet? so im guessing there should be parameters after the ?
Is there a way to intercept the submit button message so I can read it?
Or is there another better way?
Related
Could you please try to direct me which way should I be aiming in order to achieve the following high level requirement related to creating a fillable PDF for a user. The user can open this PDF, change some content, save the PDF, send it back to us via email and our system will parse the content and upload it to a database.
basic steps:
- the user clicks on a web button and the system behind this online web application sends an email to the user with a PDF document having all details from the user's saved application, e.g. full name, postcode, dob, answers to some questions (tickboxes), free text comments area
- the user opens this PDF, changes some details e.g. updates text in the comments area, unticks some check boxes, changes post code
- the user saves the changes and sends the PDF back to us.
- the system reads the PDF, parses the content and updates the data in a database.
Is the above possible? If so, please try to advise which technology can be used.
Thank you.
As mentioned in the other message, why send the filled PDF back? (well, unless you need a digitally signed version for your records).
Instead use the Submit function of PDF/Acrobat, which submits just the data. This is possible (among other ways) using HTML POST, and therefore working as if the data were sent by a HTML form. Updating the database should not be a big deal anymore in this case.
If you have to insist on sending back a filled form, there are AFAIK utilities which can extract the form data, and then, again, updating the database should not be difficult.
I don't really understand why you want to email a PDF for a user to fill out and then try to parse it in the first place? Why not just make some sort of web app that prints nicely for this?
If you really need a PDF, you might want to design your form in TeX and use something like this example.
Say I have a java/spring/jsf/jsp web application. User fills all required fields, chooses all the options, clicks generate report, spring beans do their job, database is queried for information, and user is directed to a "report" page generated according to entered information. I am looking for a way to save that page to be accessed later by link - kind of a share current page link. One example of this might be jsfiddle.net where you can enter information, save it and get a shareable link.
What i thought of, having my current knowledge, is saving some kind of url extension hash along with currently displayed page properties to database and query database for that information when someone accesses www.websiteUrl.com/extensionHash but making a query everytime someone accesses the extension seems kind of heavy on performance. Another way could be saving whole html page or just the content part on the server and serve later on request.
What is the most simple/productive way of doing this?
This is one option instead of link :
What you can do is you can load the required data for that report from database when your application starts, put the data in Application Context ( ServletContext in Java ) and whenever you want to get the information, instead of making a database call, you get that from Application Context.( so basically its like you are loading from cache) this way your perfomance is improved.
in java, You can achieve that by implementing a listner class.
Downvoters : please specify the reason.
A client wants a web application that performs a calculation based on text inputs, pulldown selections, checkbox selections, etc. They want to persist form data input but they are don't want to store them on the server. Instead they prefer to retain the inputs locally.
I've been searching and determined that this not a standard approach. Then I came across HTML5 Storage but it looks like that option isn't exactly what I thought it was.
Client wants to be able to save and load sets of inputs such as mortgage scenario 1 or mortgage scenario 20 year. Basically like a "save as" and an "open" button.
I reported back that this approach isn't really feasible and a server database or some other form of server persistence is the norm.
Am I way off base in being insistent that we need to use a database? Or are there any options I'm not aware of such as jquery?
How about object serialization? If you use PHP as backend, you could gather form data to array, serialize it and output to downloadable file.
Another attempt is to catch form data into JSON using only JS, and then making user save it. Look here for more info: How to generate and prompt to save a file from content in the client browser?
We have a complex form that we created as a PDF. We want users to be able fill out the PDF and then either print it out and mail it in or click a Submit button and have it emailed to the client. What's the best way to do this?
I understand that we can attach javascript to the Submit button on the form. I'm thinking we could use Javascript to submit the form to the website and then write a REST type page that would handle emailing the PDF to the appropriate place. We are using ASP.NET/DotNetNuke on the backend of the site.
Dave,
You have a few options on this but a lot of it is going to be depending on how you want the user to handle input.
If you want the user to fill the ACTUAL PDF themselves, then you have a lot less control. But it can submit to a location and go from there, but saving it as a modified filled PDF requires either licensing for the document, OR for the users to have the full version of acrobat.
Another option is for you to build an input form for the user, then fill the PDF and commit the information, then either send them the file if they want to print or e-mail it off yourself.
I've done both in the past for previous clients/jobs. Feel free to ping me directly with a bit more detail if this doesn't help.
Edit - More detail based on comment
In this situation you have a few options.
Actually it looks like you can get to part of this now via the PDF create process - http://help.adobe.com/en_US/Acrobat/9.0/Standard/WS58a04a822e3e50102bd615109794195ff-7e0d.w.html
From a server side sending you have a few options. They can save it and upload it, which isn't best.
You can have a form post action, this will submit their answers to your server, you could then plug them into a PDF, save it, then forward it on
In the end it will depend on the true workflow.
Have you considered this SaaS? http://www.pdfescape.com/what/publishing/
Based on my Google and stackoverflow search I'm guessing there are no library for this purpose.
The goal is: store some blank forms on my server. Then present these to the user, who edits the form in the browser with Javascript and submits the form back to the server.
The client wants to reuse parts of an old system (the forms) in which users would download an editable PDF, edit it, and email it back to a secretary. Our users aren't very computer savvy and many don't realize they need to email the forms back, assuming instead the forms somehow get submitted when they save their local changes (or something).
I haven't seen the forms yet, so I cannot assess the viability of an alternative.
I don't know of any Javascript libraries but you can use the FDF/XFDF files to do something like this. The idea is that you basically link your PDF file to an external FDF or XFDF (XML version) file. When the PDF is downloaded, so is the associated FDF/XFDF file. You place form fields on the PDF (which it sounds like already exist). They fill that information in and (if you add a button to the PDF form) click on the button which basically does a POST back to the server with these fields.
At that point you can save them to a database, merge them with a PDF, etc.
BTW - the XFDF/FDF files aren't really necessary to just fill in a form. You would only need them if you want to be able to display a PDF that has form fields and to fill those form fields in automatically. If you are always displaying a blank PDF for them to fill in you can get away with just adding a button which posts back to the server.
How about editing the PDF forms to add a submit button?
http://help.adobe.com/en_US/Acrobat/8.0/Professional/help.html?content=WS3593E0A4-C5E2-4cde-A09E-2A984346DDD2.html