For option 4, to maximize performance especially across the WAN, you may want to piggyback existing Window Open initialization type Service calls made on forms today (and actually code the PUSH's at the service filter level). This is of course if the forms you are talking about have an existing initialize type of Service being called.
If there is no existing initialization type Service, instead of coding an active link PUSH, I might code a NEW active link service call, and have the server side SERVICE do the push. This will be more extensible (performance wise) in the future if there are other SET & PUSH type activity required on access of a form. Regards, -----Original Message----- From: Action Request System discussion list(ARSList) [mailto:arslist@ARSLIST.ORG] On Behalf Of SUBSCRIBE ARSLIST theReel Sent: Tuesday, October 29, 2013 8:42 AM To: arslist@ARSLIST.ORG Subject: Re: How to determine when a user last logged in Hi Guys, Thanks a million for all the feedback; I am not the first person to hit this requirement then. Looks like there are a few different approaches we can take, most of which will require customisations. I am surprised/disappointed that Remedy doesn’t store a user’s last login time OOTB. We have just built a customisation which enables our various customer’s end users to self-register a new account which assigns them a Read only licence and permission only to the SRM portal for their company - we don’t have access to their AD so can’t use that. We want to be able to supply each of the customers with a list of registered Users and the last time they logged on – shouldn’t be a big deal I said :( Ps. We are not concerned if we cannot get historic information. The options: 1) Enable User audit log and extract data: Ideally I don’t want to have the user audit logs enabled, mainly for performance reasons and the size of the log. 2) Enable Licence usage and extract data: If the licence usage form does not track Read licences then this is no good to me. The main users I am trying to track have Read licences. 3) API approach: I like the sound of this but unfortunately this is currently my weak spot. May need to do some studying but would not be confident I could achieve this. 4) Active link on main homepage forms that triggers on Window Open and pushes time to new field on user form: This may work, although I am not a big fan, as I believe there is already far too much workflow that triggers on Window loads. An issue is that this would update each time a user opens the form and not just the first time for their session. Misi mentions setting a field which would stop the multiple records per session but I am not sure how I would clear this when the users session ends? – not everyone will click Logout so can’t use that. I think option 4 is my best option so far but it’s not ideal…yet. Thanks for all the help and any more ideas are more than welcome. Tony _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org "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"
