Configuration Console Conditionally Required

My users want to add a custom user field to a form. They want this new field to be required, if the value of another (existing) field is "X". Is this possible thru configuration console/LPL? If you have been able to do this, can you provide the snippet of LPL that makes this work?

Thanks in advance.

Natacha

Find more posts tagged with

Comments

rmbell

We made OtherDate1 required based on the value of a user field using a constraint. If the user field is populated with HRADMIN, the field is required to have a value of some sort, otherwise, it can be empty. Here is the code we used:

constraint (OtherDate1 entered

and last PendingActionRequestRel.GCSNode = "HRADMIN"

or last PendingActionRequestRel.GCSNode != "HRADMIN")

"BenefitDate1Required"

Legacy Contributor

Thanks for your reply but I cannot get my constraint to work - I can't save due to LPL errors. Where is this constraint in your LPL? Is it on the OtherDate1 field? Is it before the OtherDate1 field or under the OtherDate1 field.

rmbell

In my example, it is under the OtherDate1 field. Here is the entire field:

OtherDate1

label is untranslatable:"Benefit Date 1"

constraint (OtherDate1 entered

and last PendingActionRequestRel.GCSNode = "HRADMIN"

or last PendingActionRequestRel.GCSNode != "HRADMIN")

"BenefitDate1Required"

Dr. Awesome

The constraint LPL suggested below is good. It would be need to be added to each form the field is used (assuming you desire the same logic there). Potentially updateable lists too.

You can also define a UserField itself as conditionally required when (SomeCondition). Take a closer look at your UserField definition. You'll see radios for Optional, Required and Conditionally Required. This can be safer if your user base is into using ISD and web services and personalization.

Legacy Contributor

I'm totally missing something here with getting this constraint to work. If anyone can help me figure this out, I'd be forever grateful!

I only want the constraint on the JobRequisitionInformation form, not everywhere the field might be - if a job requisition is entered and the reason for opening is new/not budgeted, the manager needs to enter a comment to justify the job req.
The ReasonForOpening is a delivered field. The comment field is a custom field (defined with no constraints).

Below is the code I'm trying. I am getting an LPL error when trying to save my change and the "CommentRequired" is underlined in red. I assumed that would be the message the user got but maybe I shouldn't assume...

ReasonForOpening
     required
JobReqCommentGHS
     label is untranslatable:"Comments"
     constraint (!(JobReqCommentGHS entered) and last ReasonForOpening = "NEW/NOT BUDGETED") "CommentRequired"

Dr. Awesome

This is more what you want. Is ReasonForOpening a relation? Do you know it’s “last”

Think - “this constraint MUST BE true” or else it fires.

ReasonForOpening

required

JobReqCommentGHS

label is untranslatable:"Comments"

constraint (JobReqCommentGHS entered and last ReasonForOpening = "NEW/NOT BUDGETED")

“CommentRequired"

Legacy Contributor

ReasonForOpening is not a relation but a field in JobRequisition - it is a drop down field with 3 values (currently).

I was finally able to get my LPL to save and do what I want with the below:
JobReqCommentGHS
     label is untranslatable:"Comments GHS"
     constraint ((JobReqCommentGHS entered
     and ReasonForOpening = "NEW/NOT BUDGETED")
     or (ReasonForOpening != "NEW/NOT BUDGETED"))
         "CommentsRequired"

Thanks for all the help!!

[Fixed] CSI Product Enhancement Request Process 2022 Update-20220310_130043-Meeting Recording.mp4

Copyright © 2025 Infor. All rights reserved.