Using WEBUTIL in the Menu - problems when not in current form..

Advertisement

Using WEBUTIL in the Menu - problems when not in current form..
We make a webutil call in the menu - but it is a problem when the current form does not have webutil attached to it.
Is there any work around other than putting webutil in 100 forms?
OPEN_FORM/CALL_FORM both affected.
Message was edited by:
brian952
Message was edited by:
brian952
Repaly
I've just spotted this thread, so my comments might be too late to be useful, but... I had a similar problem, and as Eric suggested, went for the approach of having a single, small form dedicated solely to running Webutil functions. Any form or menu option that needs to do something WebUtil-related (e.g. 'I need to have File A moved from the apps server to the client') calls a library routine which then calls the dedicated form, passing it all the instructions it needs to carry out the action. Control then returns to the original form. At the moment, I leave the dedicated form in the background in modeless state, so it can be used again if needed elsewhere without having to be reloaded. (If the user tries to click on the modeless form, it shoves control straight back to the 'main' form.)
I read somewhere that ideally you shouldn't WebUtil-enable every form, if most of the time, most of them won't use it. There's the overhead of initialising all the beans every time a form is opened, and it seems to me that that's relatively intensive, as bean usage goes. Not a showstopper by any means, though.
James
Read More: The other 4 answers