Ok, thx. I guess I ll stay with my condition trick for a while

Hi,

Murkein, i unmarked this as a valid solution, as it's not the same issue: the "immediate" boolean on actions does have the same meaning than immediate attribute on JSF command tags, here's a good explanation of how it works http://balusc.blogspot.fr/2006/09/debug-jsf-lifecycle.html#AddImmediateTrueToUICommandOnly

If the need here is to make the field required only depending on which button is clicked, setting the action as immediate will not help (especially, submitted values will be ignored, required or not)

ok, I thought he wanted the same behavior when a person develops a classical form with the accept and cancel buttons, where the person pressing the cancel button does not matter any validation

Well, I understand the difference, however, the case suggested by murkein might be enough for me. In my specific case, I don't care about the field value when I reject the form.

thanks, it works

Ok, I will try this one, I thought the "required" custom property was only evaluated when the form is rendered so it's value is precalculated before the form submition. I'll see :)

well it is evaluated once, so that the form can display a "*" marker to show the user that the field is required, but it's evaluated again at submit

I tried the given solution, but it is not working. The form is submitted and no validation error is thrown.

strange, i tested it, and it seems murkein made it work too, so i don't know what could be wrong in your case, unless you have more details?

Remark: Hello,

I have try this solution to test if a widget value is mandatory compare to an other widget value in the same workflow form task. like,

{ layoutValue.get('var') != null && layoutValue.get('var') != "" }

this need to click on the "next button" and come back with "previous button" of second form to see its mandatory setting up :-(

Hi, I tried use it with a input user suggestion widget but not working. It Only worked with my input type: text, file, textarea …