Inactive Users (OpenInsight 32-Bit)
At 30 SEP 2006 12:00:03AM John Grant wrote:
Is there a way in OI 7.21 to automatically log out a user when no activity has taken place for "x" amount of time? I would like to optimize use of my user licences
At 30 SEP 2006 04:14AM [email protected]'s Don Bakke wrote:
John,
Look into the TIMER property and event.
At 30 SEP 2006 11:13AM [email protected] wrote:
John,
Don hit it on the head. We use timer to kick people off in unused. Also when we want to shut down we send out a message and then kick them off at a specific time. Timer is great for many things
At 30 SEP 2006 01:43PM Richard Hunt wrote:
I just thought I would offer this…
I have handled inactivity this way…
1) Use TIMER event to count down inactivity. Once the timer is set, and the TIMER event gets called (counted down), the user is logged out.
2) I set the timer when the user logs in. I reset the timer during a LOSTFOCUS, CREATE, CLEAR, CLOSE, READ, WRITE, and menu event. I also start and stop the timer when I do a READNEXT sentence, SELECT sentence, or a sequential file process.
3) I have an AUTOLOGOUT proceedure to START, STOP, RESET, VERIFY, SET, and STATUS the autologout timer.
4) Since I use promoted events, or proceedure calls for these items… I only have a very limited amount of code to deal with.
5) You might want an option to be able to deactivate the "AUTOLOGOUT". And you might want to set the "AUTOLOGOUT" based upon each user. You will probably want to set the "SAVEWARN" property when forcing users logout. Also be able to interrupt all proceedures safely, like selects, readnexts, sequentially opened files.
At 03 OCT 2006 11:37AM Sandra D'Angelo wrote:
Just throwing my two cents in:
We use a timer event on the main window to check a common variable and increment it. We use a Gotfocus promoted event to set the common variable to 0. When the common variable is over a specified value, we put up an "Logout warning" window that the user can click to stay logged in. If this window remains up - the Logout window's timer event will log the user out. During the logout, we grab the controlmap for each open child window that have the savewarn on and loop through to get the default values for each prompt. We then save out the record(s) for each open MDI_CHILD to a temporary file and set the savewarn off. Then when the user logs back in later, the system checks the temp file and restores the windows and values.
We also use the timer event to do a temp save so the user doesn't lose any records during a power outage. In addition, we have setup the timer to check for an autologout time (so we can force all users to logout during a specified time range) and to check for user log out time so we can logout a single user (we are control freaks).
In short, the timer event is extremely helpful.