![]() |
Telelogic DOORS (steve huntington) | ![]() |
new topic :
profile :
search :
help :
dashboard :
calendar :
home
|
||
Latest News:
|
|
Topic Title: Trigger to end user session after N minutes of inactivity Topic Summary: Can a script monitor users who "forget" to close DOORS and walk away? Created On: 27-Sep-2007 19:17 Status: Post and Reply |
Linear : Threading : Single : Branch |
![]() |
![]()
|
![]() |
|
Has anyone developed some DXL that keeps track of users who go inactive? I can see how Triggers could be used to see when a user opens a Module, and maybe even monitor if they've changed to different Objects within a Module. Thus, it seems possible to measure whether a user is inactive (Logged in, but no new Modules opened or Objects selected in past N minutes). Does anyone do this? |
|
![]() |
|
![]() |
|
I don't think what you are wanting to do is possible via a DOORS trigger. DOORS triggers execute based on an action the user takes, hence they wouldn't be inactive. Other than that I'm not sure there is a way.
There is one problem with what you are wanting to do anyway. You have a user that got up and went to lunch while leaving DOORS open. You kick him out and he didn't save. Now he's just lost all his/her work. Though any smart person would be saving every few minutes, but you have those few in every organization that never save until their done. ------------------------- Scott Boisvert Engineering Tools Administrator L-3 Communications - Avionics Systems scott.boisvert@l-3com.com |
|
![]() |
|
![]() |
|
The core of the script would exit DOORS, first closing all the modules. You can have this part either automatcially save everythijng or close without prompting to save. It would then exit DOORS, I think the command is "exit_". You'd want to loop through all open module (closing them) a couple-three times, in order to make sure you got them all.
What you really want is this: some background script running that after X minutes initiates the core processing above. Module-open and object-sync triggers cancel then restart that background script. The background script is a problem. I've got some 'wait for a while' functions that use 'client' and 'ipc' commands that wait for a certain amount of time and then wake up and check the clock. I use that to defer the execution of a DXL for further into the night (e.g. i would initiate the archive program and go home, it would wait until 1am and then proceed to archive). Problem is that the entire DOORS interface is shut down while the script waits. I cannot think of a background technique that wakes itself up after X minutes and still allows that DOORS session to be GUI interactive. Its possible to approach it this way: the triggers simply set a time stamp in a configuration file. The config file somehow uniquely identifies the current DOORS session. Have a background script that runs on the DOORS server or some client that periodically checks all such config files. If the time stamp on the files is too old then this script aborts the user. I don't recall the 'abort' commands but I'm confident they do not provide any mechanism for saving the user's work. This looks tough. Sorry. - Louie |
|
![]() |
|
![]() |
|
Just to be really awkward as well as those who do not save there are those who are 'what iffing' in a live module, so they don't want to save on exit. Close and save for them could cause as much extra work as not saving.
If people won't be educated, and you can't live with the problem try embarrassment by instituting a 'thug of the month' award for those who don't logout and so deprive others of access. (Assuming your reason for wanting to do this is to free up licenses.) |
|
![]() |
|
![]() |
|
I have a routine that closes all sessions at midnight every night, I said it was for backup purposes, and no one seemed to quibble with that. This way people soon got used to logging out at least once on the way home.
------------------------- Andrew Tagg Thales Air Systems, Melbourne Australia. andrew.tagg@thalesatm.com |
|
![]() |
|
![]() |
|
Andrew, could you share more details about the routine that closes all sessions at midnight?
Thanks, |
|
![]() |
FuseTalk Standard Edition v3.2 - © 1999-2009 FuseTalk Inc. All rights reserved.