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

Question

Question

Forms loses data when a large form is being edited on a slow connection

asked on May 7, 2018

We have a very large form currently in production. We noticed that changes we make to the form sometimes don't "stick". We observe behavior such as inserting a new field, then switching to the Field Rules tab and having it not appear in the list. We switch back to layout and the new field isn't there.

What is the largest form that LF Forms has been internally tested with?

We are on 10.3.1

0 0

Replies

replied on May 7, 2018 Show version history

I've had Forms Business Processes with over 700 variables, many of those in collections. The business process has nearly 200 steps. It also communicates to multiple workflows throughout the business process. 

One form (the largest form) has nearly 500 fields. A lot of these fields are in collections. 

1 0
replied on May 7, 2018

Ok, but what about testing it over slow connections? On the internal network everything will be blazing fast. What happens if you throttle your connection speed?

0 0
replied on May 7, 2018

There are a bunch of errors in the event viewer that correspond to this issue:

 

An unexpected error has occurred. [LFF502-UnexpectedError]

Details:
URL: /Forms/webapi/v1/form/SaveFormLayout?id=1&formId=1
Error: UnexpectedError
Date: 5/7/2018 3:50:28 PM (Central Standard Time)
HTTP Status Code: 500
Business Process ID: 0
User: xxxxx
IP: xx.xx.xx.xx
Browser: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/66.0.3359.139 Safari/537.36
Business Process Name: 

Stack Trace:
Caught exception: Laserfiche.Forms.CommonUtils.Exceptions.LFFormsException
Message: An unexpected error has occurred. [LFF502-UnexpectedError]


Inner exception: System.OperationCanceledException
Message: The operation was canceled.
   at System.Threading.CancellationToken.ThrowOperationCanceledException()
   at System.Web.Http.Filters.ActionFilterAttribute.<CallOnActionExecutedAsync>d__5.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at System.Web.Http.Filters.ActionFilterAttribute.<ExecuteActionFilterAsyncCore>d__0.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at System.Web.Http.Filters.ActionFilterAttribute.<CallOnActionExecutedAsync>d__5.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Web.Http.Filters.ActionFilterAttribute.<CallOnActionExecutedAsync>d__5.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at System.Web.Http.Filters.ActionFilterAttribute.<ExecuteActionFilterAsyncCore>d__0.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at System.Web.Http.Controllers.ActionFilterResult.<ExecuteAsync>d__2.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at System.Web.Http.Controllers.ExceptionFilterResult.<ExecuteAsync>d__0.MoveNext()

 

0 0
replied on April 30, 2020

Hello Ege,

Were you able to find a resolution for this?

I have a customer whose users are getting the same error. 

Form has approximately 20 fields and is being filled out mostly on Tablets with Mobile Data connections.

Appreciate any feedback.

Jeff Curtis

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

Sign in to reply to this post.