I have a scheduled check in / out mobile app designed to work in disconnected environment. The app is HTML using UIWebView on the iPhone.
Everything works fine as expected except when the session times out and there is no session time out warning.
Scenario:
1. User logs in and retrieves latest schedule as long as the schedule list is clean (if dirty, user must sync before getting new data from the server)
2. User sessions times out, but no warning is displayed. Session length is currently set to 90 minutes. (some drive to sites much longer than 90 minutes)
3. User presses check in button which executes java script to get location and then update the check in time stamp field. I then update the list with the code below.
var lObj = {dialog.object}.getControl('LIST_SCHEDULE');lObj.updateTableRow(primaryKey,data,ops);
4. The app then attempts to execute {dialog.object}.synchronizeLists() which fails because session timed out and user is brought back to login page.
5. When user logs back, the list is dirty so user is notified that the list is dirty and must synchronize data.
Although the data is good, the user experience is not good. I need to have the session time out warning or some method of detecting that the session has timed out without going back to the server since we want to use the disconnected features. Can I set the session time out to 10 hours? Are there consequences for extended session time out settings?
If anyone has a possible solution or workaround, it would be much appreciated.
Everything works fine as expected except when the session times out and there is no session time out warning.
Scenario:
1. User logs in and retrieves latest schedule as long as the schedule list is clean (if dirty, user must sync before getting new data from the server)
2. User sessions times out, but no warning is displayed. Session length is currently set to 90 minutes. (some drive to sites much longer than 90 minutes)
3. User presses check in button which executes java script to get location and then update the check in time stamp field. I then update the list with the code below.
var lObj = {dialog.object}.getControl('LIST_SCHEDULE');lObj.updateTableRow(primaryKey,data,ops);
4. The app then attempts to execute {dialog.object}.synchronizeLists() which fails because session timed out and user is brought back to login page.
5. When user logs back, the list is dirty so user is notified that the list is dirty and must synchronize data.
Although the data is good, the user experience is not good. I need to have the session time out warning or some method of detecting that the session has timed out without going back to the server since we want to use the disconnected features. Can I set the session time out to 10 hours? Are there consequences for extended session time out settings?
If anyone has a possible solution or workaround, it would be much appreciated.
Comment