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

Question

Question

User submitted one form, Forms appears to have submitted twice

asked on March 24 Show version history

While reviewing a custom report for a fairly simple straight forward form, I noticed for one staff member, the form was submitted twice. And then she also needed to submit the form two more times with new data. The form is asking staff for any accreditations  or accomplishments they have. This person had 3, the expectation would be for only 3 Instance IDs to appear in the Monitor and the Report. The form also kicks off a File Re-namer work flow, which then kicks off a File Filer workflow.

At first, I thought the workflow was running twice, but then when I went to the monitor and the report, I do see each of the 3 submissions (only for this user) are all unique... a total of 6 instances (for 3 form submissions).

Here is a screenshot right from the report only revealing relevant information. I am trying to re-create the problem and have not been successful. This appears to be an isolated issue as well, this has not happened to any other user. She also confirmed she did not submit each form two times, only three forms one time each.

Next question to follow this is how can I tell a LF Form what fields to look at to see if there is already a matching entry? There are a few logical combinations of fields they are filling out that if I can tell the form to validate, then the end user would get an error "that form has already been submitted" type of response. I did research through the KB here, but am not really finding this is easily accomplished unless I tell the form to write to it's own form specific sql table and then I can build in my validation checks that way.

I also attached a screenshot of the process diagram to show what I mean by "simple form"

EE Certification Process Diagram.png
0 0

Replies

replied on March 24

Similiar issue was reported in support cases before: user clicked once on submit button but it produced two instances.

Although we could not reproduce it, we suspect that it was related with sql server bad performance.

As for the follow up question, the submitted forms belong to different instances so the save to repository step would run for each of the instances. You may add a workflow service task before the save to repository service task, and let workflow check if a document already exists, then use gateway to skip the save to repository step.

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

Sign in to reply to this post.