Change or supplement the Active User Query View to be more accurate / useful

The Active User Query View uses the ACTIVEUSERMONITORINGLOG table which only logs API calls. So, if a user doesn't do something that results in an API call, then they will not show as being active. If, perhaps, it was based on USERPAGEHISTORY or the logging was made more comprehensive, it would be far more useful and dependable. As it is, I'm not sure what value it brings.

  • Mitchell Gibbs
  • Feb 1 2018
  • Reviewed: Voting Open
Organization Name (Please enter full organization name) Providence St. Joseph Health
Reported Version 4.0
  • Attach files
  • Mitchell Gibbs commented
    18 Jan, 2019 05:03pm

    This is still a key need - especially for organizations with HIPAA compliance needs. I've created a customization that scrapes the USERPAGEHISTORY into a table, but it is klugey and something more integrated and robust would be beneficial.

  • Guest commented
    22 Aug, 2018 01:16am

    Agreed.  It's not useful as it stands.  The most basic use of this table would be to track who is logged in, but it doesn't work for that.  I can't even use it to find out who is logged in so I know who to notify that we need them to logout for maintenance purposes.