A timer won't work, because they are not user specific, they will trample all over each other as multiple users sign in. Also, a timer cannot interact with an open page. Finally, doing anything client side isn't going to work either, because multiple browser tabs/windows will interfere.
Any requests from the client to the server will restart the 20 minute countdown. Instead, you should do something like the following:
* Implement an entity to associate user to their most recent page load.
* Use the "OnBeginWebRequest" system event to update that entity, so you can keep track of when the most recent page load occured. On actions that should keep the session alive, you can update that too.
* Using a JavaScript timer, call a REST service that checks the most recent page load time from that Entity. If it has been more than 20 minutes, do whatever it is you need to do (plenty of posts in this forum to understand how to make a popup open from JavaScript).
J.Ja
Any requests from the client to the server will restart the 20 minute countdown. Instead, you should do something like the following:
* Implement an entity to associate user to their most recent page load.
* Use the "OnBeginWebRequest" system event to update that entity, so you can keep track of when the most recent page load occured. On actions that should keep the session alive, you can update that too.
* Using a JavaScript timer, call a REST service that checks the most recent page load time from that Entity. If it has been more than 20 minutes, do whatever it is you need to do (plenty of posts in this forum to understand how to make a popup open from JavaScript).
J.Ja