Submitting a form to a request handler

C_Fly

Hello,

I'm fairly new to Livelink and I'm a little unclear on what's needed to submit a form. One of the requirments I have is to create a form that a user will enter data in as well as uploading a file I would also need to show a status while the data is being processed. I saw a couple post about using the BrowserBegone function so I'm trying to use that in my request handler. The problem is when I post my form with the action pointing to the request handler it never gets to the Execute script, the form is being submitted but I'm not sure what module it's going to.

 

Thanks

 

Appu_Nair

Not sure if what I post will help you or not.When I want a form in livelink to post here are the steps I take.

First create a module,= mymodule

Add my Request Handlers=mymodule.RH1,RH2 and so on.

Then if sombody gets to this URL ?llisapi.dll?mymodule.RH1 I show them a weblingo that is set in .fHTMLFile.the user eneters whatever and in that second submit I may have ?llisapi.dll?mymodule.RH2

Note you can show the output of that yet in another weblingo or you can use one RH for everything as well.I must have posted a sample here shwoing how to use the same RH with different  query string variables that you pass.

For long running processes I use the method that opentext uses when you apply permissions and stuff a popup window starts .It is pretty hard for me to explain this methodolgy but it is rather simple if you trace that functioning.I just opened up a project i did way back and here is my thought process (psuedo code on it)

I used browserbegone like this

When the first submit happens you use browserbegone to another RH's .fhtmlfile.In my case I was using a cache object(you don't have to go that far a simple write to a file might suffice).Immediately the user will get a page that is just polling that file.Ot has a meta refresh polling that as well.Right after the browser begone the first RH's execute method is still running which will complete and update the file that the other browser session is polling.In effect the user's browser is the second RH's .fhtmfile which is polling for some event that you have setup.You have to throw some logic in there to stop the meta refresh and help the user get out of that page.

I hate to show my rather inelegant  code that is the reason why I am psuedocoding this,it is not as tough as you think it is.

If you are talking about form as in form template,livelink forms it gets trickier,it can be done as well.