Asteriks for mandatory field not visible on form

Alex Kraemer
Giga Guru

Hello all

Have an interesting issue in the Agile Development module. The field "Acceptance criteria" is mandatory, but the asteriks is not displayed in the form. For the Short description this is displayed correctly.

find_real_file.png

If you leave the field empty and save, the asteriks then appears briefly and of course the message that the record could not be written.
The asteriks then disappears again immediately and is no longer displayed (good timing on the print screen below was required to capture the asteriks).

find_real_file.png

It does not help if the field label is shortened, I have already tried this.

Any idea?

Thanks for inputs and greetings
Alex

1 ACCEPTED SOLUTION

Willem
Giga Sage
Giga Sage

Hi Alex,

Have you checked for a Client script or UI Policy that is making it not mandatory? The timing you describe could be that shortly after load a Client script f.e. starts and sets the field (on your screen) to not be mandatory. Example script to search for would be:

g_form.setMandatory('<acceptance criteria field>', false);

Or any UI Policy for this specific view could also cause this.

View solution in original post

7 REPLIES 7

Saurav11
Kilo Patron
Kilo Patron

Hello,

How are you making the field mandatory UI policy? Client script? Dictionary?

Also if you are using script are you suing in the below format:-

g_form.setMandatory('fieldname', true);

Thanks.

Thanks for your hint and it was a UI Policy that caues this issue

Regards

Alex

Hello,

Glad you got the answer . if my answer helped you can you also amrk it correct/helpful based on Impact.

Thanks.

Willem
Giga Sage
Giga Sage

Hi Alex,

Have you checked for a Client script or UI Policy that is making it not mandatory? The timing you describe could be that shortly after load a Client script f.e. starts and sets the field (on your screen) to not be mandatory. Example script to search for would be:

g_form.setMandatory('<acceptance criteria field>', false);

Or any UI Policy for this specific view could also cause this.