Hi Jean,
Launchurl has no return value. GDC could return a boolean if successful, not sure about GWC, but today there is no return value.
Anyway, in your case, the return value will always be "success", as it would return if the document could be open, and not if the user was able to do anything special on the opened document.
Maybe this would be a right candidate for the WebComponent: we provide a javascript API, which is a bridge between the Front-End (GWC or GDC) and the html world.
So in your case, you would need to:
- add a small javascript library to your web portal, which would use our API
- have your portal use this library to send feedback to your 4GL application
A big picture: GWC and GDC publish an object, named gICAPI. This object can be used in two ways:
- via callback methods, data/focus/property is sent from 4GL to your html component
- via public methods, data/focus request/action can be sent from your html component to your 4GL program
So the idea would be to have a small javascript function that would be called with the login status, and one when the user logs out:
function sendLoginFeedbackTo4GL( success ) {
if (success)
{
gICAPI.action("loginok");
} else {
gICAPI.action("loginfailed");
}
}
function sendLogOutTo4GL( ) {
gICAPI.action("logout");
}
And in your 4GL:
INPUT BY NAME webComponent
ON ACTION loginok
...
ON ACTION loginfailed
...
ON ACTION logout
END INPUT
Of course this means you will have your web portal inside a 4GL application (so inside GDC if you're running GDC, and not your browser), but this is the only way I can see where you can really make a web portal interact with a 4GL application.