Question? If a person has a Named CAL, do they override the Session Timeout settings?

[Rahul_03]

Question? If a person has a Named CAL, do they override the Session Timeout settings? Our current setting are set for 20 minutes, but user is complaining that they are in the applications all day long and if they walk away, they are timed out. Is there a way to set individual users to bypass the environment session timeout. We cannot increase session settings as we run out of session cals which is why it's set to 20 minutes.

#CALs.

[Sonja_Bauernfeind · Accepted solution]

Hello @Rahul_03 

The type of CAL used does not impact the Session Timeout configured in the QlikView Management Console.

The Session Timeout affects all CALs equally - and also all users equally, as it is a global setting that cannot be set for individuals.

If your system has session recovery enabled, your users should not feel too much pain though. Since that will re-connect to the previous session parameters (selections, etc) even if the session itself has been properly closed.

[Rahul_03]

Hi @Sonja_Bauernfeind 

Thanks for your response.

Quick question: Is there any disadvantages or negative impact on servers if we enable session recovery?

Thanks,

Rahul.

[Sonja_Bauernfeind]

@Rahul_03  Nope!

Here is some more info about it if you need it: Session Recovery in QlikView: How to enable it and how it works 

[Rahul_03]

@Sonja_Bauernfeind ,

we disabled session recovery option in past as we were having issues with the .shared files becoming too large allowing staff to recover their settings, this caused performance issues as apps were taking too long to open.

Thanks

Rahul.

[Sonja_Bauernfeind]

Hello @Rahul_03 

Yeah alright, I can see that if people have too much selected (for example if you have very large apps and they ended up getting kicked out of their session while having a LOT selected), the resulting bookmark would be large.

It doesn't generally happen, so this is unfortunate that you ran into that in your system. 

In this case, we are back to the session timeout being server-wide and not configurable.