Hi Mark
Thanks for the reply.
We’re using V8.
What you’ve described is correctly occuring. The Growler has a ‘login’ link and a close button. If the user clicks the login link, they are taken to the login screen - no problem. If they press the Close button they are left on the page.
The complaint that they have (after closing the Growler) is that when they next click a link or a button that invokes a command nothing happens on the screen - no action, no growler or script error.
When MWS invokes the Growler - is there a property set in the form that indicates that the session has expired?
I’ve previously looked at CAF.Request - specifically SHOW_LOGIN_FORM without success. I was hoping that setting this to true would force the login page rather than the Growler.
Shane
#MWS-CAF-Task-Engine#webMethods-BPMS#webMethods