Company: Link Technologies
Case No: L13076. Project: 15.60: LinkSOFT Version 15.60
Logged By: Sanjay (Link Technologies) on 03 Oct 2024 01:05PM
Priority: Low
Product: Framework
Group: Enhancement
Time Taken: 8.00 (Weight: 15.00)
Assigned To: Sanjay (Link Technologies)
Circulation: Sanjay
Resolve By: Thursday, 03 October 2024 01:05 PM [121 days since logged date]
Status: Closed
Subject: Application Timeout Management
Summary:    

Application timeout to change as follows:

Add a configuration in "Web.Config" in the "AppSettings" section that will allow the user to Enable/Disable this feature. Name the configuration: "KeepSessionAlive". Options are "Yes/No". Default value is "Yes"

  1. If "No" is selected, the session will timeout based on the Web Configuration session value, which is defaulted to 20 minutes. i.e. After 20 minutes of inactivity, the user will be directed to the "login" screen.
  2. If "Yes" is selected (Default value)
    1. Between 6am and 8pm AEST:
      1. Keep the session alive even after 20 minutes of inactivity
    2. Before 6 am or after 8PM
      1. Send the user to the Login Screen after 20 minutes of inactivity

Notes:

  1. In the case of part 2 above, we force the user to the "login" screen before 6am and after 8PM as we want to allow for System Maintenance.
  2. We show the Session Remaining time on the top right-hand side of the browser

Reason:

  1. Users are finding it frustrating when the form is logged out while users are doing work
  2. Outside 6am and 6pm, we pass the user to the login screen as we do not want the application to remain open overnight during system maintenance.
Audit Notes:Edited by sanjay on 14/01/25 17:40. Edited by sanjay on 04/10/24 14:36. 
03 Oct 202401:06PM Comment 1 by Sanjay (Link Technologies) Assigned To: Sanjay (Link Technologies) Followup Date: 11-10-2024 01:05 PM Time Taken: 8.00
PART A - Development work for this case has been completed.

1. The change will be available in version: 15.51

2. The following changes were made (Include Database object names, Program classes, and any other relevant information):

  1. Added functionality to follow requirements stated in the case header.

3. Affected Areas:

  1. Application Framework

4. The issue was caused by:

  1. Improvement

5. Other Relevant Notes
6. Next Step
(Review and System Test (Developer) -> UAT (Quality) -> Documentation): Closure


If you have any queries regarding this support incident, please email admin@linktechnologies.com.au and include the Case No: L13076 in the subject line of all emails regarding this issue.

Document size: 3.8 KB
For call complaints, please contact the Managing Director of the company using this form