Is it possible for automation Rest API to return Max(endTime) from licenses/consumption for each distinct user?

[OdieW]

I am working on a user management automation that is currently using some QVD's for data but I would love to have it use the Rest API instead. I think the only issue holding me up from that is the need to get Max(endTime) , to see when they last used Qlik, from licenses/consumption for each user. I'm fairly new to using API's and I don't see much help on the documentation for this type of question, perhaps because its not possible. Or maybe I can pull all the data with the API and then have the automation get me the Max(endTime) for each user?

[MatheusC]

@OdieW 
You can use Enttitlment analyzer one of the monitoring applications where you will have information about users, access, applications, licenses and more..., as you mentioned about creating qvds so I don't believe you yet have monitoring applications in saas.

See the post below and follow these steps, you will easily have all the monitoring apps.

https://community.qlik.com/t5/Official-Support-Articles/Qlik-Cloud-Monitoring-Apps-Workflow-Guide/ta...


- Matheus

[OdieW]

Thanks @MatheusC, my current implementation of the automation is using data from the entitlement analyzer. What I am trying to do is disable users who either haven't logged in in a while or have never logged in. That part would be easy enough on it's own, but I don't want to disable them immediately on first run of the automation. First run of the automation sends an email to notify the users and tells them to log in if they want to keep their account. Next run of the automation will notify any new users on the list, but also compare users who were on the list from the previous run that are still on the list which means they still didn't log in after being notified so now they get disabled. In order to do this piece I need to create a QVD to compare against, which I am doing. But its recently dawned on me, the way I had the automation flowing (notify never logged in, disabled never logged in, notify haven't logged in in a while, disabled haven't logged in in a while) would cause the people who were notified on run 1 to again be notified on run 2 before they are also disabled on run 2 and I don't want that. I think I can get around that by doing both disabled first, then reloading the entitlement analyzer and then doing the notifications as this flow will have removed those who were notified on the first run and then disabled on the 2nd run before it does the new notifications. It's just getting more complicated than I'd like. I'd love to use the API instead of relying on the entitlement analyzer and second QVD generator apps. But I can't do that if I can't get Max(endTime) from the API