Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
Does anyone know how to find out where my development licences have been allocated?
The NPrinting web console only shows the number allocated and the total available but not where it has been allocated. I have 2 development licenses, of which only 1 should be used. But, for some reason, both have been used and I am unable to find any way to release one of them.
There doesn't seem to be an equivalent page to the QlikView Server Management Console page that shows CAL usage.
Anyone had this problem?
Just gotten off the phone with Qlik Tech Support (thank you for Bastien for his help).
It turns out that the Administrator role takes a developer license and so does the Developer role. If a user has both Administrator and Developer roles then that user takes 2 developer licenses!!! Counter intuitive to say the least.
This has been marked as a bug to be fixed in a future release.
Just gotten off the phone with Qlik Tech Support (thank you for Bastien for his help).
It turns out that the Administrator role takes a developer license and so does the Developer role. If a user has both Administrator and Developer roles then that user takes 2 developer licenses!!! Counter intuitive to say the least.
This has been marked as a bug to be fixed in a future release.
Why would you give someone both roles? If they are the admin, then they have developer privileges.
For the 2 designer limit for the SMB edition, the Admin does not count against that total. Remove the developer role from the admin account and then you can allocate both developers to other users.
Why would you give someone both roles? If they are the admin, then they have developer privileges.
It is common practise to give users overlapping roles in any application. Many applications also have admin roles that do not give them developer rights and even if NPrinting does not follow this convention, it shouldn't result in additional licenses being taken when both are granted.
It has been accepted as a bug and will be fixed in a future release.