Hi experts,
I have an interesting requirement and I am currently investigating whether it is possible in Appian or not.
The requirement is to have a page that is constantly refreshing so it always shows the latest data on the screen and ideally have that auto-refresh prevent the logged in user from getting timed out/auto sign out due to inactivity.
I've set the session timeout for my app to the minimum which is 15mins.
The data of the dashboard is coming via stored procedure. I've tested this by adding the refreshVariable function together with the refreshInterval property for a local variable on the page that just keeps getting a random number and each time the refreshInterval hits, the number shown on the interface gets updated. This seems to work although I haven't tested whether this would work when the data of the local variable is coming via stored procedure. Regardless, it still doesn't prevent the time out.
In summary, my data is coming from stored procedure and I need to get it to constantly update automatically to get the latest data without getting timed out due to inactivity.
Is there any way I can achieve this without getting timed out?
Thanks in advance and looking forward to hearing any suggestions!
Discussion posts and replies are publicly visible
Try using refreshVariable in your interfaces
Check this links please
docs.appian.com/.../refresh-behavior-interfaces.html
docs.appian.com/.../SAIL_Recipes.html
Hi David, I've tried that and it actually does constantly refresh the value of my local variable but it does not prevent the auto-logout/timeout. So I'm wondering if the auto timeout can only be prevented with a user interaction.
YOu can also set the value in console in order to avoid timeout..
Yes, I'm aware. Unfortunately, the session timeout needs to be there for our applications as part of a security requirement.
If you need the timeout at 15 minutes for security requirements, I'm not aware of a way to force the page to stay open without user interaction beyond that time limit. And to be honest, if there was a way to do this, wouldn't it violate your security requirements?
As far as I know, in this particular case it wouldn't necessarily violate the security because the idea is to only apply it for a small authorized group of users.
Ah gotcha - unfortunately I still don't know of another work around that could achieve this unfortunately.