Suggested enhancement to lockout
When a user is locked out it is at times in the middle of a workflow, eg. investigation creation or invoicing and sometimes the user has not saved the work they are doing. If another user comes up to use that computer they can only enter the previous users password to save it or logout which loses the information which hasn't been saved.
Is it possible to apply and changes prior to locking the screen to prevent this?
Re: Suggested enhancement to lockout
We have just started using individual log-ins and auto lock function. I agree it would be great if it could auto save before logout.
Re: Suggested enhancement to lockout
Hi,
This is very minor issue, but some of our vets have noticed that the auto lock function happens even though they are typing in OpenVPMS. I think this is because they are just typing a long history and haven't moved through the program using tab or a mouse. It's not really a major issue as they can just put their password in again and continue typing, but I said I'd ask if it is something OpenVPMS can change or just a quirk of the internet browser.
Thanks, Greta
Re: Suggested enhancement to lockout
In order to prevent auto-lock, you need to periodically do something that triggers synchronisation with the server. This resets the auto-lock timer. Things that trigger synchronisation include:
The following will not trigger synchronisation:
The reason for this is to limit the amount of network traffic between the browser and the server; it would slow everthing down if every keystroke or mouse movement was sent.
-Tim
Re: Suggested enhancement to lockout
Hi,
We have had this issue in the past as well. While something that is manageable once people know about it there are times where it can be somewhat bothersome.
Would an option be for a synchronisation trigger to be sent every few hundred keystrokes? This way just typing will trigger a synchronisation and reset the clock. But you will not have too many triggers/so many that it becomes a server issue.
Re: Suggested enhancement to lockout
Where are you seeing this behaviour? Looking at the code, it might occur in the new email editor - this doesn't synchronise with the server when Enter is pressed. Is it occurring for you elsewhere?
Re: Suggested enhancement to lockout
This behavior occurs in the letter editor screen. I.e. when we copy and paste text into an input field. Then are basically just editing by adding a few words here or there. Enter is often not pressed as the templates are pretty complete. However you can end up not having pressed enter, or clicking a button (no apply button for input fields) for some time... thus nothing is saved.
Re: Suggested enhancement to lockout
OK. Raised as OVPMS-1847
Re: Suggested enhancement to lockout
I would like to suggest making this a role level security feature. I am getting a lot of requests from the doctors that they need more time before the system times out while writing notes but I don't want to lengthen the current time available.
Additionally, we would like to use the current workflow as a whiteboard and it just isn't feasible with the current configurations. (yes, we have considered the 3rd party options but passed due to the costs).
Thanks, Alan
Re: Suggested enhancement to lockout
The OVPMS-1847 change has been implemented for the 1.9.1 release, so it is less likely that the screen will lock while note entry is taking place. You have to be actively typing within the timeout period to avoid the lock.
I think the whiteboard comment needs to be started as new topic, and you need to elaborate on what you are after.
Re: Suggested enhancement to lockout
other thought. Perhaps an option for a new user to login and continue the current session (but change and update user)?
Re: Suggested enhancement to lockout
This could cause issues if the new user doesn't have the same rights as the prior user.
Re: Suggested enhancement to lockout
true - was just a request by staff as sometimes they wish to continue someone elses workflow.
Re: Suggested enhancement to lockout
On a slightly related note, does anyone get the issue that sometimes after a period of inactivity, after a click the "Please Wait" dialog pops up and will hang there until the browser window is refreshed and then it will ask for a new login?
Cheers,
Matt
Re: Suggested enhancement to lockout
Matt - yes I see this. My 'fix' is that when I know the session must have timed out (becasue I had breakfast or did something else for a while) is to press the Back button on the browser - gives an immediate loging screen.
Regards, Tim G
Re: Suggested enhancement to lockout
A better approach is to click the browser refresh button (or Ctrl-R). If the session has expired, it will return to the login screen. If not, it will force a synchronisation with the server.