Well, you hit the nail with the hammer... I don't have control of the page or this wouldn't be an issue. Actually, if it was me, I'd just have them fill it out in a WebDirect page and have full control <grin>. Oh well, thanks for the input.
& "?script=setf¶m=' + encodeURIComponent(encodeURIComponent(autosearch.value))"
(autosearch is an input element, top right corner in this page)
That sounds interesting. I'll have to find a Windows machine to try it out. I assume from your comments that it does not run on a Mac. But this is the type of answer I was looking for. Thank you user19752.
Would be great to accomplish this without a PlugIn.
If not, It's TROI-URL, 360Works-WebAssistent or MBS PlugIns which would do that job
But the wizards may have found another way around this...
Ahhhh.... efficientbizz, you have helped me the most. I did not realize MBS had WebView functions and I can make use of that since I have a license of that plugin. Pretty slick! I know it won't work for those without it, but that fixes this particular problem for me. Thanks!
I've already sent this thread to Christian Schmitz to encourage him to log in. Wouldn't be surprised if next post is him, telling you which MBS-function you have to trigger.
(Probably another member of this species who catalyzes caffeine into great IT-solutions)
scraping-the-web, however is often a need with forms (and response pages) that are not under our control. Remember also that scraping can be difficult when you are landing on a result that is changed by the content manager anytime between the time you create your "routine" and the next time you need it.
A request that can return xml or json results, can be much easier to work with when permission to do so is arranged with the content providers, if at all possible.
Just sayin' be aware, & I know as I've been providing content (and scraping) since the beginning of the web...
On a related note, for anyone trying to accomplish this sort of thing on OSX when the user is using Safari as a web browser:
Seems to work:
I tested the idea, and it seems to work just fine on a Mavericks machine, though all of beverly's cautions about how easily a scrape situation can break would certainly apply. Another thing to keep in mind is that screen scrapes get harder to set up as the pages make greater use of client side UI scripting.
I realize that Taylor already has a good working solution, but I could see how this might help someone with a use case of automating the filling in of web forms in an OSX context, and figured someone looking to do so might turn up this post in a search.
HTH and kind regards,