Config Console - making a checkbox required -> checked

Looked at a ton of other similar posts and tried a number of things. None working for us.
Business requirement is for all employees to verify their personal contact information 2x/year.
We have added a boolean user field 'blnValidated' and added it to the EmployeeContact.EmployeeContactUpdateForm. We're trying to put a constraint on it so that it must be checked for the form to submit. Our attempts are not successful, even though we seem to be doing things very similarly to other community posts.

YNHHValidated
Constraint when (not blnValidated)
"Check_the_box"

(first post, so indenting above not rendering properly)

Other things we've tried:
Constraint when (true)
Constraint when (false)
Constraint when (blnValidated)
Constraint when (blnValidated = true)
Constraint when (blnValidated = false)
Constraint when (blnValidated entered)
Constraint when (blnValidated not entered)

Also tried some Parameter Rules and Action Rules. Nothing seems to be sticking. This should be simple...what are we missing???

Find more posts tagged with

LSF/Landmark Development

Accepted answers

All comments

smodarressiyazdi

Parameter Rules

YNHHValidated

required

untranslatable:"Check the box"

Make sure you tab the field , "required", and message lines correctly.

Joseph Van Denburg

It's more overhead - but I would explore creating a Transition Program that presents the Personal Information form for review. The TM program can be assigned and tracked within TM.

Looking forward to the LPL answer though.

smodarressiyazdi

Sorry misread, replace "YNNHValidated" with your field name "blnValidated", place the LPL above underneath parameter rules and it should work.

cleverly

Field names in LPL are case sensitive, and as far as I know, a field has to begin with an uppercase letter. So I wouldn't expect blnValidated to work or be valid; perhaps it is BlnValidated?

smodarressiyazdi

Also I don't think you need "when" on the form for your constraint. Not sure if that's throwing it off. I always have trouble with Boolean and whether or not to use = "yes" or = true or "is true".

unknown

Put constraints into Submit/Create Action - Entrance Rule. It should work.

David Casperowitz

I mucked up some of the field names, but you all seemed to get where I was going. Thanks

David Casperowitz

Have tried this. No luck.

David Casperowitz

Can you share an example?

kmelche3

I added a constraint to a homemade boolean field recently. I had to ISD out the field to find the correct value to use for LPL. I found I had to use "TRUE" and "FALSE" in the end and that capitalization mattered. Other things I tried that didn't work were true / false , yes / no , 1 / 0 .

we wrote it like:

YHNNValidated

constraint BinValidated = "FALSE"

"Check_the_Box"

David Casperowitz

what's driving us nuts is that we have a checkbox constraint on an action form that works just fine with constraint ( checkbox not entered)

This is just the delivered EmployeeContactUpdateForm. Top line of the config is:

EmployeeContactUpdateForm is a Form

Whereas the one that works is:

CustomFormX is an ActionForm

I can't imagine the type of form makes a difference on whether a constraint works. That would be dumb...

David Casperowitz

constraint BinValidated = "FALSE" doesn't do anything for us either.

Chad Dirst

I've suspected for some time field rules do not fire when the field is not filled in, blank, or false. Can you test putting the constraint under a different field that is filled in (i.e. HROrganization would be an example of something always filled in). It's definitely undesired since the edit message shows on a different field but we have seen success with at least getting the edit to fire).

David Casperowitz

Still not firing. Creating an Xtreme ticket. Has to be something simple.

David Casperowitz

Ended up being way simpler. Shaheen gets points for being closest.

single column

YNHHValidated

required

smh...

Copyright © 2025 Infor. All rights reserved.