WebDirect timeout may prove a deal breaker

Discussion created by vaguiar on Dec 11, 2014
Latest reply on Dec 11, 2014 by wimdecorte

Having used our WebDirect administration solution for almost a year, it is becoming more of a problem that users connot remain logged in for more than an hour. The solution functions very well as an intranet providing acces for our staff to timekeeping, expense reports, mileage, support ticketing, and more, except that users must re-login and re-navigate if they timeout. If FileMaker doesn't allow longer timeout limits, say four hours or more, our powers that be are likely to direct that we go with a different system. As the FM developer, I would really prefer to avoid this. Why does it have to be this way?