TagUI - Multi-File and CallServer()

yea I have seen the same behavior in TST, too many events at once to process the call servers. I suspect this was part of the reason that IWOV went back to the single file Tag UI screen for the 1st release.

For multiple TagUI only 1 request is being sent...

callSerer works by sending asynchronous http request from the single Data Capture Form hidden frame.
Subsequent callServer requests override the current one, that's why you've got only the last call executed.

To fix that you would have to play with 'setTimeout' Function plus perhaps some callback Function(s) to let your FormAPI
JS code *know* that current callServer request has been completed and *Client* can run the next one. In other words
you yourself would have to re-synchronize multiple callServer requests.

Alternatively, you can make callServer Script smart enough to process parameter's "Set" and make a single call
supplying multiple parameters, etc

birt_image.png

Yea but I *would expect* that there would be a way to set the events to fire for each file or for all files. Without the event covering all files, you will have a very tough time getting this to work. Of course it makes your JS/CallServer more complex but not much you can do.

Yea but I *would expect* that there would be a way to set the events to fire for each file or for all files. Without the event covering all files, you will have a very tough time getting this to work. Of course it makes your JS/CallServer more complex but not much you can do.

That's probably true but Tim's issue IMO depends on exactly how he performs multiple callServer requests.

If it is some sort of a loop with the callServer without checking that the (previous) call has
been executed (and that seems to be the case) only the last one will work. Asynchronous calls
will simply override each other before callServer process(es) have even a chance to start.

Agreed. I think Tim will need to figure out a way to condense the multi-file events into a single list and then make the call server call. I would be surprised if there is a way to use the timeout and keep from losing any of the events.

new_report_1.rptdesign

anisha

You can create/use a framework that will allow for multiple Call Server requests to be handled in a FIFO process.

JonathonG has created this framework and made it available on Devnet in the past. Not sure if this is still out there.

Agreed. I think Tim will need to figure out a way to condense the multi-file events into a single list and then make the call server call. I would be surprised if there is a way to use the timeout and keep from losing any of the events.

It's not a rocket science to re-synchronize Client - (call)Server threads, I did it many times

As to callServer on (themselves asynchronous) multiple Events - I would've collected Events' Data in
some Object Array and when all the dust settles run callServer in a loop re-synchronizing each call

callSerer works by sending asynchronous http request from the single Data Capture Form hidden frame.
Subsequent callServer requests override the current one, that's why you've got only the last call executed.

To fix that you would have to play with 'setTimeout' Function plus perhaps some callback Function(s) to let your FormAPI
JS code *know* that current callServer request has been completed and *Client* can run the next one. In other words
you yourself would have to re-synchronize multiple callServer requests.

Alternatively, you can make callServer Script smart enough to process parameter's "Set" and make a single call
supplying multiple parameters, etc

Sorry for the lag in my response on this. I've been slammed. Everything you said is correct and I'm doing most of what you're recommended already. That is I have a callback from the callout which lets the form know that its done. That triggers code that uses the data in the JSON object to draw the form.

The issue is the onFormInit firing for each file in the TagUI list. That one will be tricky to solve. Still got to think about it. I'm still reading through the rest of the posts.

Yea but I *would expect* that there would be a way to set the events to fire for each file or for all files. Without the event covering all files, you will have a very tough time getting this to work. Of course it makes your JS/CallServer more complex but not much you can do.

Yes thats what I need. The issue I'm having is that the TeamSite callServer is only executing for the last file onFormInit that is called. The form is loaded my form api collects data for the request and makes the request. The data that is then returned for that last form only has data that applies for that particular form not the rest of them in the file list. The objects being returned from the callServer are returned in the (main)(global name space) as well which just keeps overwriting the returned values anyway. So there are two fundamental issues. Smiley Wink

Yes thats what I need. The issue I'm having is that the TeamSite callServer is only executing for the last file onFormInit that is called. The form is loaded my form api collects data for the request and makes the request. The data that is then returned for that last form only has data that applies for that particular form not the rest of them in the file list. The objects being returned from the callServer are returned in the (main)(global name space) as well which just keeps overwriting the returned values anyway. So there are two fundamental issues.

So, with a recursive function thats calls the server, or does a 1 sec timeout etc.. and a callServer complete flag etc.. I was able to get qued callServers working for the multi-tagui. My problem now is that FormAPI itself includes no name space etc for the returned value (a JSON object). So, when I make the callserver and it completes it says two things. 1). I am done ok to do another one and 2). render the UI using the provided data.

Interestingly though an item address such as /record/Tab/item/address is really the address of the first file only. So when I do my callback regardless of which callServer is completing, only the first file is getting rendered correctly. However that same callServer and render using JSON data mechanism is called when changing a particular field as well. When that happens FormAPI is smart enough to render the UI for that particular file.

sanoboy

So, with a recursive function thats calls the server, or does a 1 sec timeout etc.. and a callServer complete flag etc.. I was able to get qued callServers working for the multi-tagui. My problem now is that FormAPI itself includes no name space etc for the returned value (a JSON object). So, when I make the callserver and it completes it says two things. 1). I am done ok to do another one and 2). render the UI using the provided data.

Interestingly though an item address such as /record/Tab/item/address is really the address of the first file only. So when I do my callback regardless of which callServer is completing, only the first file is getting rendered correctly. However that same callServer and render using JSON data mechanism is called when changing a particular field as well. When that happens FormAPI is smart enough to render the UI for that particular file.

hi, how did you set this timeout between two callServer()?

hi, how did you set this timeout between two callServer()?

Search is a wonderful thing. Maybe type callserver timeout in the search field of DevNet and click search

sanoboy

Search is a wonderful thing. Maybe type callserver timeout in the search field of DevNet and click search

Yes, using recursion, something like:


         function checkCallProgress()
         {
           if (complete == "NO")
           {
            //Check again in 1 sec
            setTimeout("checkCallProgress()",1000);
           }
           else
           {
           nextCallServer();
           }
         }

Hope helps for others later.

testReportListOfCrosstab2.rptdesign

Capture.JPG

Yes, using recursion, something like:


         function checkCallProgress()
         {
           if (complete == "NO")
           {
            //Check again in 1 sec
            setTimeout("checkCallProgress()",1000);
           }
           else
           {
           nextCallServer();
           }
         }

Hope helps for others later.

This is not a recursion, just a series of sequential calls

Search is a wonderful thing. Maybe type callserver timeout in the search field of DevNet and click search

Juts saw this. Funny Smiley Wink

This is not a recursion, just a series of sequential calls

True. Its just a function that calls itself. In the context of the multi-tag UI its a nice way ensure that although onFormInit() gets called n times really fast you can control the process. Mine looks like this but the principal its exactly the same...

When the form loads its executed and makes a callServer(). Just prior it sets the callserver() status to false. At the end of the callServer() I set the status to 'true' again and the process continues sequentially.

function stackCallServer() {
if(callServerStatus == true) {
callServerStatus = false;
getContexts();
}
else {
setTimeout("stackCallServer()",1000);
}
}

I have this part working. Its the rest of it that needs work / clarity. I been pulled off on other things and will be picking this up again soon....