Come for answers, stay for best practices. All we're missing is you.
We moved to DOORS 9.7 and in the release notes it claims there is a new feature that will make modules go read-only if the user is idle for a specified time. Does anyone know how this is setup? I don't see anything obvious in the tool...maybe it is an admin feature?
This is the note in the 9.7 release note:
I found the perms in the DXL Reference Manual that go with this setting but I haven't messed around with them yet.
Void setGlobalVarsForSwitchModuleToReadOnly(bool isEnabled, int timeoutValue) bool getDatabaseSwitchModuleToReadOnlyEnabled(void)
If you go to the DOORS database properties, there is a section for "Switch module to read-only". From there you can enable it and set the desired time for the switch.
testing has proven that module changes made prior to the timeout switching back to read-only are lost if they have not been saved!
In the same release there is an "auto-save" feature that can be enabled. I these features should probably used with together so not to lose unsaved data.
The odd thing is the auto-save seems to be configured by the user but the timeout is configured by that administrator...so I guess it is up to the user to decide if they want to lose unsaved changes or not.
We have found that even with auto save turned on and set for 2 minutes and the read only feature set for 15 minutes that we lose data. It turns out that if you are actively editing but have not lost focus on the object you are editing, then DOORS doesn't seem to recognize it and won't save it with the auto save feature. If you happen to be editing still when the 15min timer set for the read only shift expires, you will loose the data -- even if you are still typing! Does anyone have a fix for that??
This probably has to do with how they are determining if a session is idle. Just typing text isn't a trackable event in DOORS, so this is being considered "idle". And since you are in the middle of editing, the changes haven't been committed locally so the autosave isn't going to work. I would push to increase the read-only timeout...15 minutes is pretty short.