How long is the user time-out for Forms? Is it changeable?
Client is wondering the length of time before they need to re-login to forms in order to finish a submission.
In Forms 9.1, we improved the caching logic so that the session information is stored in the database. It will solve this problem when user takes a long time to finish the form, the IIS recycles the session; but when user clicks the "submit" button, it will retrieve the session information from the database, automatically authenticate the user to the server and submit the form.
Lena, does your response mean there is no need to modify the timeout settings in the web.config file? It sounds like the session timing out while the user is completing the form will not be noticeable by the user. If this is the case then your response should be the "Answer" for this question in regards to Forms version 9.1. Thanks!
Right, there should not be a need to modify the web.config file. Forms should handle it unnoticeable to user.
In Forms 9.0, the user's session is based on IIS session timeout settings. By default, the IIS session will expire after 20 minutes of inactivity. If the IIS session expires, the user will have to log in again. You can modify the session timeout value in IIS. See this page for more information.
In Forms 9.1, the timeout value will be stored and editable in the web.config file in the Forms install directory.
saving a draft means a new bit of information they have to keep track of.
and I have had a report from a client that they hit "submit" and then were told to re-log in before the form went through. That doesn't line up with what you are saying
I have a similar scenario with a client of mine as well. They will access a form that requires their authentication, and begin filling it out. If they spend too much time filling it out, and then hit "Submit", they will get a time-out error. When they click "ok", it will reload the form but all fields have been cleared out. You can imagine this will become frustrating for the users.
Also, what about a publicly filled-out form that doesn't require authentication to the form first? Is there an adjustable setting for time-out on those too in addition to the authenticated forms?
Travis,
With a publicly filled out form, your submitter token is filled out as "anonymous" currently. This would lead me to believe that we wouldn't face any time-out issues with forms as no login is needed in the first place and no specific to the submitter information is actually stored.
It is interesting that you say this also happens to your client as well. Maybe this is a case of functionality intention not meeting real-world practice. Can someone from Laserfiche please let us know if this is the case and if this is addressed in the next version of forms? (or if it will be addressed in a hotfix after the next version is released?)
Ah, I goofed and was describing the behavior in Forms 9.1, where this issue should not appear. I've edited the answer above to reflect this change.
In Forms 9.0, the user's session is based on IIS session timeout settings. By default, the IIS session will expire after 20 minutes of inactivity. If the IIS session expires, the user will have to log in again.
You can modify the session timeout value in IIS. See this page for more information.
Is this still the case in 10.4.3? There shouldn't be a need to login if the session has expired? Meaning my client is filing a form out with several pages and the session timesout, they can continue to press next and eventually submit the form?
I'm not sure that anyone from Laserfiche has answered the question/comment posted by Travis Park in a December 6, 2013 post ...
"I have a similar scenario with a client of mine as well. They will access a form that requires their authentication, and begin filling it out. If they spend too much time filling it out, and then hit "Submit", they will get a time-out error. When they click "ok", it will reload the form but all fields have been cleared out. You can imagine this will become frustrating for the users."
The difference with our client is that they are already logged into Laserfiche Forms. They open a form and begin filling it out. When they click whatever button to complete the task, Forms informs them that the form has timed out (not the session, because they have actively been filling out the form). When they click "Ok" and go back into the same form all that data they had entered is gone. We are still using Forms 9.0.
In Forms 9.0, the user's session is based on IIS session timeout settings. By default, the IIS session will expire after 20 minutes of inactivity. If the IIS session expires, the user will have to log in again.
You can modify the session timeout value in IIS. See this page for more information.