Recently we hit exceptions because our shared passivation folder was not large enough. We are considering expanding the size of that folder, however I am also curious about using an inactivity timeout. If we could implement an inactivity timeout using OOTB rules to autoamtically log a user out rather than saving their passivation files on a storage device it seems like that would be a better solution. I have looked for inactivity timeout information but am unable to turn up much. If anyone has answers or any kind of input for the following questions I would certainly appreciate you responding.
1) Has anyone already implemented a solution using an incativity timeout?
2) Which OOTB rules are involved? In what version are these rules a part of PRPC?
3) What information/guide/article/resource helped you implement your inactivity timeout?
I am told that there is a JS function desktop_showTimeoutWarning() but I am unable to find any documentation on how to implement this. If anyone can point me to docs on this or anything around inactivity timers, I would certainly appreciate it.
Thank you for your response. We have decided not to go with the timer - we will simply use database passivation instead of file passivation. PRPC 7.1.9 uses DB passivation by default - all we're going to do is remove this entry from prconfig: