As of now, our JAWS GUI is not timing out. Is there a specific parameter that can be set/modified in order for the GUI to timeout after specific time of inactivity?
Release : 5.8.6
Component : AUTOMIC AUTOMATION INTELLIGENCE ENGINE
This is working as designed.
The analysis of the code shows that when the Java client starts, a heartbeat thread is kicked off. As long as the client is running on the user's computer, the session will not time out. The web client has a similar "heartbeat" for updating the UI via "pull" requests on a near-real time basis.
The software is designed such that if the client (or browser) is closed without logging off, the user's session will time out. Otherwise, as long as the user has a client up (either the Java client or the web/GWT client), the session will remain active.
The product is often used in a NOC environment where it is being used for monitoring purposes and users are not interacting with it at all. It would not be desirable for the client to time out in this situation.