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

Question

Question

302 redirect of Form submission

asked on May 18, 2016 Show version history

While doing a Fiddler trace of I noticed that all submits happen twice with all of the same parameters.  The first is a submitted to Forms/Form/Submit which takes almost 5 seconds and results in a 302.  The redirect is to Forms/form/avsubmission and submits the exact same parameters except one, the routingResumeId.  This form returns in less than 2 seconds.

 

My question is why the round trip to the browser fore two requests to display one page?  Is there a way to bypass the first request or combine the 2 requests? 

0 0

Replies

replied on May 18, 2016

What version of Forms are you using? I checked with Forms 9.2 and Forms 10 and can't reproduce it. Can you provide an trace with fiddler?

0 0
replied on May 20, 2016

The attached file is an export of my sessions

Export.txt (162.08 KB)
0 0
replied on May 22, 2016

Can you check whether you have selected "Automatically load the next task if the same person is assigned to it" for the message start event from process canvas? If you have this feature checked, then after submit the form in the message start event, it will be automatically redirect to the user task. The " POST Forms/Form/Submit" is for submitting the form in message start event, the "GET Forms/form/avsubmission" is for getting the form in the user task.

1 0
replied on May 23, 2016

It is checked and that is the behavior we want, instead of the user having to go to his/her task page to launch the next -- in this case, obvious -- task.

For processes that require multiple, consecutive forms is there a more efficient implementation that avoids the multiple trips to the server?  In other words, the response to the submit is to send the form directly to the user without the extra roundtrip to and from the server.

0 0
replied on May 24, 2016

I assume the goal is to increase performance after submission and load up the next form as quickly as possible.  The delay you experience is not the html traffic you see in fiddler.  When you submit a form the Form Server extracts the submission data and transmits the data to the routing engine.  If the next page automatically loads then the forms server must wait for the routing engine to process the data before it loads the next page.  After routing engine is completed a signal is sent and the next page is generated.  If you don't automatically load next form then there is no delay because the forms sever doesn't wait for the routing engine signal before it loads next page. 

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

Sign in to reply to this post.