How Does Decisions Determine Last Login Date?

Greetings,

I am trying to create a process that fetches accounts based upon their last date of login into Decisions. However, I've noticed that I'm getting a lot less results than I was expecting. I fetch users who have logged into Decisions during the last three days, but I'm missing users who have been active everyday.

Is Decisions not fetching these users because they have never logged-out? If so, how do I get users who have been "Active" within the past three days?

Comments

  • gregory_Decisions
    edited April 11

    Hello!

    You are correct. The account field last_login_date fetches the last time a user has logged-in to Decisions, not the last time a user was active.

    You can enable auditing to track most user activities within the portal/studio:

    https://documentation.decisions.com/docs/enabling-auditing

    There is the catch that this will fill you audit table quickly, and a scheduled job would be recommended to clear that data after x amount of days.

    However, it sounds like you goal is to track users who are actively using the portal/studio. If this is the end goal, might I recommend logging-out users after a selected time of inactivity in the studio/portal. This can be configured under System > Settings > Portal Settings by enabling "Auto Lockout":

    https://documentation.decisions.com/docs/portal-settings

    By doing this, users who aren't actively doing anything in Decisions during off-hours will be logged out automatically. This would give you more accurate results for who is accessing the studio daily.

    We hope these recommendations help!

    -Gregory, Decisions Support

Sign In or Register to comment.