Good Morning All,

I want to log a user out of a solution if no edits or creations are made in a specific time. Is it possible to capture a last modification time across all layouts that I can base a trigger on. this is a hosted solution, not served

"Hosted" as in hosted in the cloud?

 

FileMaker Server can be set up to disconnect idle users after whatever time interval you set.  If you can't use the FMS feature then your only option would be to install on OnTimer on each window that quits the solution after a certain idle time.

Hi,

Thanks for the reply, no, I mean hosted as in locally held on a computer rather than linked via a network. How would I capture the idle time ?

You don't have to, FM does it for you.  Check the help on the "Install onTimer Script" script step

Thank you but I don't see how that can be used. The OnTimer script would run immediately the application was idle so if nobody typed anything for five seconds they would be sent to the Log_In unless the Install OnTimer script can be triggered by other actions and then re-triggered if further actions occur ??

The OnTimer would run *AFTER* the interval that you specify:

 

  

Yes, I see that but the timer is running whether there is activity in the application or not. So someone is entering new records while the timer is busy running down. If the timer has reached it's set point, as soon as the application is idle the script would run in effect giving no idle time.

Not sure if this one will fly but...

 

You could write a cron script that checks the file timestamp vs current time, and if greater than a set time, triggers another FM file that runs a Close Application script on startup... As FM file timestamps change when anything is done in the file.

Yes, I see that but the timer is running whether there is activity in the application or not. So someone is entering new records while the timer is busy running down. If the timer has reached it's set point, as soon as the application is idle the script would run in effect giving no idle time.

 

No, that is not how it works.  When the app is idle the counter starts ticking towards your cutoff.  But as soon as someone does something (in the window that the timer is on) the counter is reset.  If you have onTimers on a background (= idle) window then you would see what you are experiencing.  So you have to do a lot of window management if your application allows the user to spawn windows.

Thank you, it does indeed work that way. The documentation does not make it clear at all about the way that it works.