nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Required fields no longer enforcing policy

Michele Bazzani

I have had forms running with required fields linked to issue fields since we went live late last year. Suddenly they are no longer working.

I have relinked them, removed and readded them, put them in front of and behind conditional sections. I got one to work for a moment and then back to not working a moment later.

I am on cloud ITSM working with an out of the box custom form, no add ons. The other form on this project is still working fine.

Any help would be great.

Accepted answers

Aaron Jurrens

I ran into this today. I did some testing and made some progress.

Form A was allowing me to submit from the portal without completing any fields that had been marked as 'required' on the Form; there are many.

Form B is a new form I created today, recreating (did both manually and via copy / paste) Form A's content on a fresh form.

From the portal I confirmed that Form A allows submission with empty required fields.

On the Request Type, I swapped out the problematic Form A for the newly created Form B. Form B

From the portal I tested Form B. Form B, presenting the same content, exactly, as Form A, enforced field requirements correctly, disallowing the use of the Send button on the portal request.

On the Request Type, I swapped back to Form A. I went back to the portal and tried a Form A submission with empty required fields. Allowed.

I cloned Form A thinking a new copy could work. Cloning retained the brokenness.

I copy / pasted from Form A (CTRL + A, copy / paste) to a new form. Copy / paste retained the brokenness.

My solution is to create new forms manually. If you have a working form, it appears that those clone correctly and their values will copy / paste to new forms correctly and you should end up with a functional (required fields enforced) new form.

Good luck!

All comments

Joseph Chung Yin

@Michele Bazzani -

If the request type form works for a time, then it just suddenly stopped working especially when you have checked to ensure everything is working after your action performed to the form and verified it is working.

Please note that any project administrators can change the form configuration/setup at any time by accident. In this case, there are "too many cooks in the kitchen" which cause the problem in the first place.

By default, if everything was working then it stopped, it is always because some configurations have been changed.

Hope this helps.

Best, Joseph Chung Yin

Jira/JSM Functional Lead, Global Technology Applications Team

Viasat Inc.

Michele Bazzani

Hi Joseph,

Sorry for my delay, as I am traveling. No one has made any changes to the project or the form, yet required items are no longer required even though they are marked as such.

As the form is stand alone from the issue layouts etc. I am having difficulty understanding why this form suddenly stopped enforcing the mandatory entry and will submit with nothing selected.

Thanks

-M

Michele Bazzani

Here is a screenshot of the 2 fields I am talking about so you can see they are clearly marked required yet I can go straight passed them

Joseph Chung Yin

@Michele Bazzani -

So, if you access Form configuration right now, fields are still marked "Response Required" right? The form is still associated with your request type layout?

So customers can still create his/her issue using the specific request type from the portal without filling out the fields (element of the Form configuration)?

Please advise.

Best, Joseph

Michele Bazzani

Yes, the screen shot above is from the form config showing the required fields. It’s associated to the request type yet they can just not answer anything and his submit and the form submits completely empty.

I have attached screenshots from the customer and resolver perspective showing the fields are marked as required and are completely empty.

-M

Erik Weinhold

Still happening in June of 2024.

Erik Weinhold

I was having a similar issue and noticed the "Minimum" field did not have any data in it. When I entered an requirement (1 character in this instance) my validation suddenly worked again. Not sure if that's your fix or not but worth a look.