Time Out
Hi,
We are still having issues with people billing things under other people's names. This usually occurs when someone has not logged themselves out of OpenVPMS and a new user sits down at that computer and just starts typing.
Apparently there used to be a feature that would enable automatic log out, however this no longer works in 1.6.
Is it possible to have this re-instated in 1.7 and what would this cost?
Ideally this would let us specify:
- A period of inactivity on a terminal after which OpenVPMS would log out.
This would presumably also be an important feature of any further security/permissions upgrades. Setting user permissions is not much use if an administrator logs in, walks away from a computer and someone else just sits down and starts using their account.
Re: Time Out
If this change was made would it be a feature that was selected at practice level as this would not work for us.
Thanks,
Bernie
Re: Time Out
I believe automatic session timeout hasn't been supported since 1.4. Then it was done by changing web.xml in <TOMCAT_HOME>/webapps/openvpms/WEB-INF/.
This timeout was managed by Tomcat; any session where there was no activity for the configured time was terminated.
The message notification support added in 1.5 (i.e. the mail icon), forces the session to remain alive, as the browser periodically contacts the server for updates.
The most straightforward solution is to basically do what Tomcat used to do, i.e. expire sessions that haven't had user input for a period of time. This would require ignoring browser update requests, in order to determine when the session was last accessed.
This would be configured by web.xml as before.
If you want a solution which doesn't need to be configured each time you deploy OpenVPMS, then support could be added to configurabe at the practice, practice location, or user level.
-Tim
Re: Time Out
Hi Tim,
I guess my preference would be there are two aspects to this.
Option 1 - Can this be done now by my implementor or is this something that would require changes to OVPMS?
Option 2 - Sounds preferable but more expensive.
Approximate costings?
Thanks,
Adrian
Re: Time Out
Both options require code changes. I'd estimate $685 for the former, $850 for the latter, if you just want to configure it at the practice level.
-Tim
Timing out
Hi,
The lady at the workface was complaining at being timed out and I as I hadnt read the forums lately I didnt realize why this was occurring. Seems its been reintroduced in 1.7. I understand the use in multiperson practices but Chris is just finding it an annoyance. Havent had a chance to figure where its actioned as yet as trying to make the printers behave under 1.7.Is it the tomcat web.xml as previously? As for the printers they were going fine for 3 days but now Remote Utilities printer has got in on the act and the default laser has been ousted. Suspect I just need to fiddle with the defaults and restart tomcat a few times. Is this Remote Utilities printer part of Openvpms or something in Windows 7. All was sweet on XP.
Cheers Geoff
Re: Timing out
For Auto Logout, see http://www.openvpms.org/documentation/csh/1.7/admin/organisation/practice
I'm not sure what Remote Utilities printer is, but it has nothing to do with OpenVPMS. OpenVPMS will list and print to the printers it can see from the server machine, and thats it.
You can configure the default printer for individual document templates via Administration|Templates. If you have changed printers recently, you may need to update the default printer for existing templates.
Failing that, it sounds like you may need to get your implementer to look at it.
Re: Timing out
Hi again,
Thanks for that, the expansion of the help section is a bonus. Too easy. I should have delved into the details of the upgrade a little closer. As for my implementer thats me and has been since setting up 5 years ago. The rouge printer turns out to be part of a remote desktop utility that Id been trying out - worked great locally but kept dropping out over the net.
Thanks Geoff