You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
What version of Node.js are you using? Not applicable if you use the standalone version of Butler.
What command did you use to start Butler?
What operating system are you using?
What CPU architecture are you using?
What Qlik Sense versions are you using?
2024-Feb
Describe the Bug
In current Butler version a list of all assigned licences (professional and analyzer, respectively) is extracted, then the lastUsed property is examined for all those users.
On large QS environments (thousands of users and more) this may result in the licenses release process taking a long time.
Especially considering that the most likely scenario is that only a few users' licenses will be released.
A better solution is to apply a filter when retrieving the list of which users have (for example) professional licenses, with the effect that we instead get a list where all licences should be released.
The filter is a URL parameter: filter=lastUsed le '2024-04-22T23:59:59' will get all users with who used their licences before that timestamp.
Expected Behavior
No response
To Reproduce
No response
The text was updated successfully, but these errors were encountered:
What version of Butler are you using?
12.1.1
What version of Node.js are you using? Not applicable if you use the standalone version of Butler.
What command did you use to start Butler?
What operating system are you using?
What CPU architecture are you using?
What Qlik Sense versions are you using?
2024-Feb
Describe the Bug
In current Butler version a list of all assigned licences (professional and analyzer, respectively) is extracted, then the
lastUsed
property is examined for all those users.On large QS environments (thousands of users and more) this may result in the licenses release process taking a long time.
Especially considering that the most likely scenario is that only a few users' licenses will be released.
A better solution is to apply a filter when retrieving the list of which users have (for example) professional licenses, with the effect that we instead get a list where all licences should be released.
The filter is a URL parameter:
filter=lastUsed le '2024-04-22T23:59:59'
will get all users with who used their licences before that timestamp.Expected Behavior
No response
To Reproduce
No response
The text was updated successfully, but these errors were encountered: