FM Go 13 FMreauthenticate extended priviledge

[rkass068]

Hello, 

 

I have made a FM solution that is fully compatible for the iPad and I am having trouble doing something for its connectivity. I currently have FM Server 13 and the Disconnect when idle on for 15 minutes. The feature works perfectly with FM Pro where it disconnects the user on idle and quits all windows. However, this does not seem to happen with the iPad. Instead if FMreauthenticate is active, it asks for the username and password of the user and goes straight back to where the user left off.

 

When the file opens and because the user sometimes opens the database in front of patients in the hospital, I have a script that asks the user to either go to the patient list, or to a blank layout with search fields. This is due to confidentiality. This script does work but on FM Go 13, the person when they reinsert their credentials resumes back to the previous page they were working on, which may have confidential information of another patient. 

 

I tried shutting off FMreauthenticate and it works but it asks the user if they want to try and reconnect and therefore it bypasses the login screen AND goes back to where they left off.

 

So i want to either:

 

A. perform a script on reconnection or reauthenticate that goes to the blank page so the other patient will not see the confidential info

 

B. exit the windows completely like FM pro does and reassessing the database gives the file open script i mentioned above

 

C. disable the dialogue box (Host disconnected would you like to reconnect?) so that the client cannot reconnect and the database will close when FM server disconnects the client.

 

I dont understand why Filemaker Go acts so different from Filemaker pro and why FM doesn't at least give us similar options as FM pro on Filemaker Go. 

 

Sorry for the long explanation but I want you guys to understand.

 

Thank you for taking your time

[Agnes Riley]

The answer is simple: they probably can't. We, developers are used to doing workarounds for things that should just work out of the box.

You could probably start a timer on the layout and see if the timer stops if the DB locks the user out. Then check with a script trigger on layout load if the time is different then direct the user to the starter layout.

Thus has not been tested. Just an idea.

[rkass068]

The answer is simple: they probably can't. We, developers are used to doing workarounds for things that should just work out of the box.

You could probably start a timer on the layout and see if the timer stops if the DB locks the user out. Then check with a script trigger on layout load if the time is different then direct the user to the starter layout.

Thus has not been tested. Just an idea.

Thanks, ill look into that. I will have to explain to the docs its just not possible yet