It’s actually a section 508 compliance issue – it’s one of the items where I keep telling BMC they are not 508 compliant but they insist on telling clients they are. My client doesn’t agree.
From: Action Request System discussion list(ARSList) [mailto:[email protected]] On Behalf Of Lockwood, Teresa L Sent: Wednesday, August 7, 2013 10:36 AM To: [email protected] Subject: Re: Auto-logout and session expiration on the midtier ** Patrick - Here is how I tell my users to get around this. The first window I have them open is the Approval console. Then from there they click Home which opens a new tab and then they can open whatever they want from there (Incident, Change, etc). Then if they get a timeout on say a Change tab they can go back to that first Approval console tab and refresh the screen which prompts them to log back in. Then they can go back to the Change tab and continue working without losing anything. Note: This only applies to the tabs that they have opened from the original Approval tab though. AR Server: 7.6.4 patch 4 on Windows 2008 SQL - Windows 2008 ITSM v7.6.4 patch 4 MidTier 8.1 Windows 2008 Terri -----Original Message----- From: Action Request System discussion list(ARSList) [mailto:[email protected]] On Behalf Of Patrick Snyder Sent: Wednesday, August 07, 2013 10:00 AM To: [email protected] <mailto:[email protected]> Subject: Auto-logout and session expiration on the midtier Our users are getting frustrated with the way Remedy handles session expiration on the midtiers. If a session expires and you are in the middle of filling out a form, you receive no preliminary warning and no indication that your session has expired until you perform an action, which by then it is too late and you must open a new remedy session in another window and manually copy and paste the information from the incomplete form into a new form in order to save it (this is BMC's advised "solution" to the problem). I have been working on a way to notify the user that their session will be expiring but am running into issues. I realize this is a common issue but have yet to find any useful threads that answer my question in the forums. So far I have been working with the existing client side status bar timer that is running based on the timeout settings it receives from the server upon session changes. I am showing the user a message when they have five minutes left and have given them a prompt which, through an ajax call, will reach out and touch the session on the server so that they can avoid the timeout, or if they choose they can immediately end their session. I also have it actively kicking the user off as soon as the session clock hits 00:00 and they have not chosen to extend their session. The issue I am facing occurs when users have remedy running in multiple browser tabs. The client side clocks do not stay in sync and therefore the user may choose to extend their session on one tab but the client side timer from another tab will still expire and kick them out. I attempted to use a session variable to universally track the amount of time left and reach out to it incrementally to keep all the client windows in sync however, I realized that since I am reaching out and touching the session, remedy assumes this is action committed by the user and resets the session timer thus infinity extending the users session. Regardless of my attempts summarized above, has anyone had any luck finding a method to make remedy's session expiration more user friendly? If I have missed an active thread with a solution to this please point me in that direction otherwise I would appreciate any solutions anyone can provide. _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org <http://www.arslist.org> "Where the Answers Are, and have been for 20 years" This email (including any attachments) may contain information that is private or business confidential. If you received this email in error, please delete it from your system without copying it and notify sender by reply email so that our records can be corrected. _ARSlist: "Where the Answers Are" and have been for 20 years_ _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org "Where the Answers Are, and have been for 20 years"
<<image001.png>>
<<image002.jpg>>
