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

Question

Question

Submit button not working

asked on July 2, 2021 Show version history

I don't know how to describe this problem other than, the submit button in one of my forms simply doesn't work, and therefore, staff can't submit the task. I have no rules to hide variables and no CSS code. I mean, I did before to center the submit button, but I removed it to see if that was causing the problem. Not only the button remains centered, it still doesn't work. 

 

I've logged off and logged back in of Forms, I removed the code to center the submit button even though it has never been a problem before, all the required fields are filled out... 

What other things can I try?

 

I'm at a loss here. 

 

Thank you!

0 0

Answer

SELECTED ANSWER
replied on July 2, 2021

Right-click the form and inspect the page. Open the dev Console and see if you receive any errors when you click the Submit button.

0 0
replied on July 6, 2021

Hi, Jason!

 

This is what I get when I do what you suggested:

 

It seems that notifications have been disabled, but I don't know where to go to enable them again. Is this a Forms issue or a browser issue?

 

Thank you for your help!

0 0
replied on July 6, 2021

Hi Patricia,

The notification thing isn't something that would affect the Submit button. That just means the "Notification Service" in Forms Configuration hasn't been set up to allow real-time updates to the user's task list.

It doesn't look like there's any unusual messages in the console. If it was related to a JavaScript error it should have added something else besides those messages when you tried to click the Submit button, so something else is going on.

0 0

Replies

replied on July 2, 2021

Watch out for required fields and field validation. Usually a submit error will take you to the offending field but not always.

1 0
replied on July 6, 2021

Hi, 

 

I have checked for this. There are no hidden fields.

0 0
replied on July 6, 2021

It seems like we've had this happen before when there was a hidden field that was required.

1 0
replied on July 8, 2021

Hello, 

I'm back to let you all know that the problem is solved and how I solved it. 

This is a process that is in production. After it was deployed, I realized that my staff wasn't uploading or entering certain pieces of information that were later necessary for metadata, so I made them required. But I did this after some instances had already started and had been submitted without that variable filled. 

In this form, in particular, there was no missing information, but this form had a collection and other members of the collection (that are not visible in this form) had missing values. 

 

How did I find out? I looked at the console side of things in the form. 

Open the form

F12 - This will open the DevTools window.

Click in the Sources Tab and on the right side, go to "Event Listener Breakpoints".

Scroll down to control and then submit (In my case it was the submit button that wasn't working, that's why I wanted the code to stop here. But you can select whichever item is causing problems). 

Go back to your form and click on the Submit button (gain, this was my issue, so that's what I did)

This will show you the code related to that button. Click on "Pretty Print" and edit the code of the submit button to force a no validate (formnovalidate = "formnovalidate"). This will force that task to submit without validation. 

 

Once I was able to submit the task, I got error messages that were super helpful to understand what was going on. This is where I was able to see that variables in other members of my collection (that were not visible in this particular form), had missed required values. Once I fixed that, the form was submitted. 

In sum, I wasn't getting any feedback/errors from the user side, and only when I was able to force the submit, I was able to see the errors from the server-side. 

 

I wish these errors were made visible without these tricks. 

 

Valuable lesson here: don't change variables from not required to required once you have deployed your process. Or, even better, make sure you are certain of which variables should be required before deployment! :)

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

Sign in to reply to this post.