I have a real world business app which is generally running "all day long. Users often
leave their computer for extended periods of time as well as "fall asleep" for extended
periods of time (ie. actually they just get too busy doing something else).
In any event, the A5 App just sits there with no keyboard input at all. Yes I do
use session vars and yes I know some of the problems are related to these vars
expiring. I "do" know how to make the session last longer in configuration.
The question(s) is : Where can I strategically place eval_valid("session.my_var") functions
to effectively thwart errors that might occur because a session.var is required to
"complete a query"? Remember the app is open and just sitting there. Normally that
next key action would perform okay. Problem here is that they simply waited for too long.
Real World Situation: I've got a Tabbed UI interface with 8 buttons that open tabs
with a grid component in it. When the user waits too long to click a button, the Tab
action doesn't error but it also doesn't open my grid because the grid is based on
a filter and session Client_id value that has expired. A 1/2 inch strip of the new tab is displayed
and that's it. I want to place some user friendly script to prevent this from occurring.
Please advise how and where to put it!!!
leave their computer for extended periods of time as well as "fall asleep" for extended
periods of time (ie. actually they just get too busy doing something else).
In any event, the A5 App just sits there with no keyboard input at all. Yes I do
use session vars and yes I know some of the problems are related to these vars
expiring. I "do" know how to make the session last longer in configuration.
The question(s) is : Where can I strategically place eval_valid("session.my_var") functions
to effectively thwart errors that might occur because a session.var is required to
"complete a query"? Remember the app is open and just sitting there. Normally that
next key action would perform okay. Problem here is that they simply waited for too long.
Real World Situation: I've got a Tabbed UI interface with 8 buttons that open tabs
with a grid component in it. When the user waits too long to click a button, the Tab
action doesn't error but it also doesn't open my grid because the grid is based on
a filter and session Client_id value that has expired. A 1/2 inch strip of the new tab is displayed
and that's it. I want to place some user friendly script to prevent this from occurring.
Please advise how and where to put it!!!
Comment