I have a police report application that seems to "timeout" rather quickly. In this scenario, the user is not logged out of the system, just the application he or she is working on, and I'm trying to find a way to stop it from happening.
Here's what happens:
An Officer uses the login page to log into the main system, and is presented with a menu of applications. (All of the applications require the user to be logged in to access them.) He chooses the "incident report" application from the main menu, which consists of a tabbed gridlinker with 8 tabbed pages.
The officer starts writing the report, and maybe gets through the first two or three tabbed pages, and has submitted the data on those pages, then, while working on the next tabbed page, stops for a short time to answer the phone or talk to someone, but has not yet submitted the data on this particular page, and has not closed out of it. Basically, the report is sitting idle with half the page filled out.
He goes back to the page he was working on, enters in some additional information, and when he clicks the submit button, the system returns a message saying "No Records Found." At this point the officer has to close out of that particular incident report application, and use the main menu to open it back up again. (Logging back into the system is NOT required.)
The officer opens up the report application again, goes to the tabbed page he was originally working on, and nothing is there, because apparently when he hit the "submit" button the first time, he was somehow logged out of that particular application or page, and nothing was saved, even though he is STILL logged into the main system.
Any ideas what is causing this or how to stop it, or at the very least, extend the time allowed to remain on an "open page?"
Here's what happens:
An Officer uses the login page to log into the main system, and is presented with a menu of applications. (All of the applications require the user to be logged in to access them.) He chooses the "incident report" application from the main menu, which consists of a tabbed gridlinker with 8 tabbed pages.
The officer starts writing the report, and maybe gets through the first two or three tabbed pages, and has submitted the data on those pages, then, while working on the next tabbed page, stops for a short time to answer the phone or talk to someone, but has not yet submitted the data on this particular page, and has not closed out of it. Basically, the report is sitting idle with half the page filled out.
He goes back to the page he was working on, enters in some additional information, and when he clicks the submit button, the system returns a message saying "No Records Found." At this point the officer has to close out of that particular incident report application, and use the main menu to open it back up again. (Logging back into the system is NOT required.)
The officer opens up the report application again, goes to the tabbed page he was originally working on, and nothing is there, because apparently when he hit the "submit" button the first time, he was somehow logged out of that particular application or page, and nothing was saved, even though he is STILL logged into the main system.
Any ideas what is causing this or how to stop it, or at the very least, extend the time allowed to remain on an "open page?"
Comment