A new optional site-wide configuration has been created, which when activated will check periodically (at least every 10 minutes) for any computer (“Port”) connected to ACR that has been idle for an extended period of time, and close down (“Timeout”) the ACR application automatically on them. Non-idle computers will remain unaffected.
The new configuration is an ACR only configuration and is called ‘Session Timeout (minutes)’. When this is set to zero minutes, this means that the “Timeout” feature will not be active, and thus no Ports will be timed out as a result of this feature.
When the ‘Session Timeout (minutes)’ is set to a value greater than zero, then the “Timeout” feature will be active and run periodically.
The purpose of the ‘Session Timeout (minutes)’ configuration is so that when the “Timeout” feature runs periodically, it can interrogate a Port to determine if all of that Port’s sessions have been idle for a period of time equal to or longer than the ‘Session Timeout (minutes)’ value. If that is the case, then all of those sessions for that Port will be closed down automatically and without warning.
To determine the time a session has been idle, the system will check to see how long (in minutes) since it has interacted with the ACR system’s database. In normal workflow the ACR system database is interacted at times such as when opening a menu item, running a report or retrieving / updating a piece of information stored in the system’s database.
Below are some example scenarios and their expected outcomes assuming a 45 minute timeout set in the configuration.
Example 1 – No timeout (1 Session on the port)
Port A. Session 1. An operator logs in and goes to Customer Maintenance and continue working “non-stop” within the system for several hours. During that time, the system checks (multiple times) for ports that have been idle for 45 minutes or longer. The lone session on Port A is never idle for over 45 minutes and is therefore never “Timed Out”.
Example 2 – Timeout (1 Session on the port)
Port A. Session 1. An operator logs in and goes to Customer Maintenance. They then go to a meeting and come back an hour later. Prior to them returning and resuming using ACR, the system checks for ports that have been idle for 45 minutes or longer. As there is only one session, all sessions on Port A have been idle for over 45 minutes and so it shuts them down, in this case the lone session on Port A.
Example 3 – No timeout (Multiple sessions on the port)
Port A. Session 1. An operator logs in and goes to Customer Maintenance to check a record. They then open a second session on Port A and continue working “non-stop” within that 2nd session system for several hours. During that time, the system checks (multiple times) for ports that have been idle for 45 minutes or longer. The first session on Port A is found multiple times to be idle, however the second session is never idle for over 45 minutes and is therefore no session on the port is ever “Timed Out”.
Example 4 – Timeout (Multiple sessions on the port)
Port A. Session 1. An operator logs in and goes to Customer Maintenance to check a record. They then open a 2nd session and check a sale, after which they then go to a meeting and come back an hour later. Prior to them returning and resuming using ACR, the system checks for ports that have been idle for 45 minutes or longer. All sessions on Port A have been idle for over 45 minutes or more and so it shuts down those sessions on Port A.
Please note: the new configuration does not affect session close over night.
Please contact the ACR Training team if you would like this feature enabled.