Dave is correct; this is a license management issue.
If the users are so distracted that they are getting timed out (maybe your timeout is too short), then they probably won't notice any workflow that you come up with to notify them that their license is about to timeout. How about you just don't give Floating licenses to the support people who are only doing Data Entry? It doesn't take anything more than a Read license to SUBMIT new tickets. When we got that straightened out around here, we found that we had more than enough licenses in the Floating pool. Gp George Payne Assistant Director, User Services Information Technology Services University of Texas at Austin 512.232.7513 ________________________________ From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] On Behalf Of Shellman, David Sent: Friday, May 25, 2007 3:58 AM To: arslist@ARSLIST.ORG Subject: Re: Floating License Timeout Isn't this only an issue only if the floating license pool isn't large enough? If that's the case then one should be looking at a license management solution. Let's look at it a different way. If it was possible to provide the warning message, what is the expected action by the user? Not save the change because they may or may not get reassigned a license when the save occurs? If they have made changes, discard them and login again to see if they are granted a write license (another warning message if they don't)? Again I only see this as an issue if the license pool is not large enough. Even if they get the error message when they attempt to do the write, isn't chances of this smaller than the number of times they would get the time out message? When we have been extremely tight on licenses and our folks have gotten the error message, if they waited 5 or 10 minutes they could attempt the save again and often it would got through. Dave ________________________________ From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] On Behalf Of Bradford Bingel Sent: Friday, May 25, 2007 1:27 AM To: arslist@ARSLIST.ORG Subject: Re: Floating License Timeout ** It sounds like Anukampa's concern is avoiding incomplete ticket updates/transactions, as in: - User opens and begins to edit a ticket, pulling a floating license - User gets interrupted or otherwise distracted, and the floating license expires - User's floating license is released, returns to the license pool, and is subsequently reassigned to another user - User then tries to save the updated/edited ticket, but instead receives an error message because the necessary floating license cannot be re-acquired Anukampa, is that correct? -- Bing Bradford Bingel ("Bing") ITM3 California http://www.itm3.com/ [EMAIL PROTECTED] (email) 925-260-6394 (mobile) __20060125_______________________This posting was submitted with HTML in it___ _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:"Where the Answers Are"
