nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Request/Response in oscript

Aruna_Tata

Hi,

Question on submitting an html form within a request handler (set by .fhtml): How can I call another script within that request handler from the form in this html file? I would like to pass parameters from my HTML form to the script.

How can I accomplish this?

Find more posts tagged with

Comments

Appu_Nair

Perhaps a little more on the use case would have gotten you more responses

Here are a few that comes to mind.

When I am on a form and I want to add something in livelink.Programmers will call targetbrowseview won't they ,it takes parameters as well.

If one was following the e.g of webformdata lookup .The user is shown a html form,when a qualifying javascript event happens,like tab or out of focus,OT calls a RH to call the SQL underneath and returns it to your opener(they hide the pop up window towards a pixel that most people can't see that kind,standard javascript interaction between named windows)

You would have seen this notation

;;call < .HTMLPrefix() + "filetag.html" >( .fRequest, "versionFile" )

That tells the OVM to pass the variables .fRequest and versionfile to the script that is called filetag.html in the support directory.This is how commonly used things are re-used,but what I am trying to say is once the response is painted in your browser you cannot call server side and thereby oscript without sending a event to the livelink server,like a post form a form.I may be off here because I am told that JSON and AJAX allows you to call things and change the already painted page.There are lot of good ajax/json and other oscripters around,who ithink will come to your rescue once they know what you are implementing.

Aruna_Tata

Ah yes - I did consider that and backtracked because i thought it would be too confusing. Lesson learnt for next time :-).

Here's what I am trying to do: I have a request handler which takes user inputs through an HTML file (set in .fhtml feature). The "action" parameter of the HTML form refers to another request handler (with its own html file) which then processes the inputs and sends an output to its html file.

I created the second request handler solely for the purpose of having an "action" parameter on the first form - what I'd like is that instead of doing that, I should be able to call another script within the first request handler which will process the inputs and then send output to another HTML file.

When I look at the oscript of other modules, they seem to have a .fURL that they use for the "action" in the HTML form - I don't quite understand how this parameter is set however. Any insights would be great.

Hope this explains it better :-)

Quoted Appu Nair (anair@alitek.com) on 2010/09/01 15:46:

Perhaps a little more on the use case would have gotten you more responses

Here are a few that comes to mind.

When I am on a form and I want to add something in livelink.Programmers will call targetbrowseview won't they ,it takes parameters as well.

You would have seen this notation

;;call < .HTMLPrefix() + "filetag.html" >( .fRequest, "versionFile" )

Appu_Nair

Maybe you are under the impression that the .fHTMLFile of your RH is settable only at the builder GUI.Actually it is not you can pretty much send or dynamically change the html file the browser receives by simple state persistent mechanisms.See attached module and see how I use that to show a form on first launch then if you fill your name I show another file and if you leave it blank again another.I also in that RH show you how to call another script.Perhaps this is what you need.If it is not ask again and I will see if I understand.

https://knowledge.opentext.com/knowledge/llisapi.dll?func=ll&objId=18039355&objAction=download

trace my RH which is called http://localhost/livelink/llisapi.dll?func=appurh.showmultiple

also if you are upto it look at the many beautiful pieces where you start at one,then you get a rereshing pop up windows.Most of it involves going from one html to another and so on.