I have a portal form (v6.6.1) with several mandatory fields. If I leave some of

smcgill over 9 years ago

I have a portal form (v6.6.1) with several mandatory fields. If I leave some of these fields without values the form flashes up some red validation messages very quickly but then submits the form anyway.
The forms designer shows the fields with the mandatory star and although the required options also show the mandatory status it is greyed out. There also seems to be a mismatch on the input parameters where only some fields are shown as mandatory.
I am using IE9 but am wondering if some of my settings could have corrupted the process model when I published it as the problem is appearing for some forms which i haven't changed.
Any answers greatly appreciated....

Discussion posts and replies are publicly visible

0 Eduardo Fuentes
Appian Employee
over 9 years ago

There are two "Required" flags one at the node input level and one at the forms designer level. You may want to confirm they are both checked, one is in the Data tab - Input and the other in the Forms Designer for each component.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 smcgill over 9 years ago

Hi Eduardo,
The problem is that the flag onforms designer is greyed out so I can't edit it but the fields are showing there as mandatory. If I make sure both are set it still doesn't work and when I check again on the input fields only some fields show as mandatory even though I've just reset them.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 Eduardo Fuentes
Appian Employee
over 9 years ago

Can you post a screenshot please?
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 smcgill over 9 years ago

Once the process is started if the submit button is clicked before the mandatory fields are completed a brief bit of red flashes up which is the mandatory fields messages but then the form immediately submits as if it no longer recognises them as mandatory.
I have only recently inherited this application and it does use javascript but i can't find any autosubmit or reason for it to do this.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 Eduardo Fuentes
Appian Employee
over 9 years ago

In the data tab when you click on Payee on the right side you will see the input properties, can you send me a screenshot?

If this app uses JS it could be that JS causing the problem
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 smcgill over 9 years ago

There is JS validation on this particular field but some of the other fields which don't have JS also show the problem. There is no JS on the load or buttons.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 Eduardo Fuentes
Appian Employee
over 9 years ago

You need to select the "Required" checkbox for the mandatory fields as shown in the attachment to avoid your JS to break the mandatory validation since this enables back-end validation
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 smcgill over 9 years ago

I have already tried setting the required check box in the input and also the required radio in the forms designer. When I then run in debug it ignores these with a quick flash of red before submitting the form and when I check the settings afterwards it hasn't retained them as required fields.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 smcgill over 9 years ago

If I set up a new model and import the form it works fine once I have removed the data elements. If I then copy that form into the problem process model it then stops working properly. Is there any way to tell if a process model is corrupt and fix it?
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 Tim
Certified Lead Developer
over 9 years ago

Can you try disabling all javascript calls from the form events and all individual field events. Incorrect javascript can cause some very strange behaviours, disable it all and then check if the required property behaves as it should. If so then somewhere in one of the javascript calls there is likely to be a syntax issue.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel