You are viewing limited content. For full access, please sign in.

Discussion

Discussion

Manage session timeout in Forms

posted on December 19, 2016

Are there any ways to improve management of sessions in Laserfiche forms? By default, if your session times out before you submit a form you get a very uninformative error message that says, "Laserfiche Forms has encountered a problem." A second line says, "Invalid form data was sent to the server. This can occur if the form is out of date. Please refresh this form and try again. [LFF2016-InvalidDataSent]" This would suggest to me that the  form needs to be updated by the developer so that it submits the correct data to the server. It says nothing about a time limit on the web session.

I can think of several things that would improve the situation. If anyone knows how to do any of these, it would help.

  1. When the form is almost ready to time out, pop up something that gives the user the option of keeping the form open if they are actually present. This is the only option that would avoid throwing away the user's work if they are working at the computer collecting information for a form that is in front of them.
  2. When the form times out, pop something up letting the user know that the form has timed out, so they don't keep wasting time filling out the form.
  3. Replace the error message above (as shown in the attached file) with a message that accurately describes to an ordinary user what happened and what to do about it. Preferably it would also let the user know how long he or she has to submit the form before it times out again.

 

Banking web sites routinely use options 1 or 2. I'd like to think that my Laserfiche Forms can do the same.

Are there techniques for achieving these results in the current version of Laserfiche Forms or would this require new features to be developed?

Timeout Error Message.PNG
3 0
replied on February 20, 2017

If you use Laserfiche Server to do authentication, but ran into this issue, then you can change the the recycling conditions of FormsAppPool to a specific time such as 1:00 which is the midnight to prevent the application pool is recycled when user is filling form to reduce the chance it happen. We are working on fixing it;

If you use Laserfiche Directory Server to do authentication, there is no workaround yet. This is a known issue that the session will be timed out in one hour and we are working of fixing it.

0 0
replied on August 7, 2017

Is there a workaround at this point for LDS authentication? We need more than an hour.

 

Regards,

Lydia

0 0
replied on August 8, 2017

This was resolved as early as Forms 10.2 Update 1 (10.2.0.834); the bug reference was 144911).

0 0
replied on December 7, 2017

Hi James-

Is this an inactivity timeout, or an absolute timeout? I ask because 5 hours seems fine for inactivity for my situation, but if it's 5 hours even if they're doing things in Forms that'll be a problem. (Hope I'm making sense.)

Thanks.

0 0
replied on December 8, 2017

One more question on this. What's the interplay between LFDS and Forms? I get the impression I can be timed out of either one. For example, this morning I stepped away from Forms for a couple of hours--not the full 5--but had to log in when getting back to things. I wonder if this is from LFDS.

Basically, people are being timed out after spending 30-60 minutes working on a complex Forms task, and they're understandably upset. I'm trying to figure out how to not make it happen.

Thanks.

0 0
replied on May 18, 2018

Is there a resolution for this?  I have the same issue with my client who uses forms to complete an employee performance eval.  It might take longer than an hour to fill out the form.  If they submit, they get the Forms Encountered and Error message, saying invalid data was sent to the server.  They get no warning of a timeout or anything.  they authenticate through LFDS.  Does anyone have a fix or suggestion for this??  Thanks.

2 0
replied on April 5, 2023

I see the note that this was resolved in the update to Forms 10.2, however, we were still having problems last year and the version we were on was 10.4.  We are now on version 11, however, I just found out that one supervisor is skipping over getting signatures on the form from all the attendants in a Toolbox Meeting and the reason is because this form used to timeout on him after one hour. 

0 0
replied on December 19, 2016

Hi Tim, you can increase the forms Timeout setting by changing the FormsAppPool default timeout in IIS.

0 0
replied on February 20, 2018 Show version history

I thought it was session timeout and default timeout is how long until the entire application is removed from memory.

Edit: scratch that, its done in the web.config. Details here

https://answers.laserfiche.com/questions/74450/Forms--where-to-change-the-timeout-in-the-Webconfig-file#74545

 

.

0 0
You are not allowed to follow up in this post.

Sign in to reply to this post.