How make field conditionally required when select list exists

Business Case: Make fields selectively required
Example: Business Class: JobRequisition
Form: JobRequisitionInformation

The fields Category and SubCategory have been hidden and are not required for the requisition initiator. Those fields are visible AND required for the Recruiter. Since the fields are not initially required, I can't make the field required and leave it blank until the Recruiter gets to it.
When I apply a constraint, it performs as expected however, it also has the unintended consequence of affecting the select lists - which return no records when the constraint is applied. When the constraint is removed, the select list performs as expected.

1) Is there a way to make a field "required when (<condition>)"?

2) Is there a way to apply a constraint to a field that has a select list attached without affecting the select list results?

----------------------------------------------

This is the example that did not work - the constraint performed as expected however it also affected the select list so it returned no results.

visible when (IsARecruiterLH)

Find more posts tagged with

LSF/Landmark Development

Accepted answers

All comments

unknown

following. we have this situation also. we were recommended to use IPA as we had a requirement on a action request form for the same.

cleverly

Based on the LPL syntax for a form field (pages 78 and 79 in the current LPL Configuration Guide) I would expect this to work:

Category
    select is PositionCategorySelectNoStatus
    display as required when (IsARecruiterLH)

SubCategory
    select is ResourceSubCategorySelect
    display as required when (IsARecruiterLH)

Vikram Reddy

@mcleverly In my scenario, I need to make a field required when reason code = "VOLUNTARY" and RelationshipStatus = "CONTRACTOR". When I create a derived boolean field with these conditions, the derived field doesn't consider the reason code (since it's part of the currently executed transaction). How do I tackle this?

cleverly

You're obviously working in GHR. I spend most of my time in FSM where reason codes aren't used nearly as much.

So while I've never done this, from reading the LPL guide, I don't see why it wouldn't work...

Add a transient field (TheReasonCode in this example). Then under the change the form LPL from:

reason code

to be (see FormField on pages 79-80:


    when value changed
        TheReasonCode = reason code
        refresh YourDerivedBooleanreason code

Then in the definition of your boolean consult the value of the transient field (TheReasonCode).

2022 Webinars - Attracting and Retaining Talent final 5 December 2022.pptx

Copyright © 2025 Infor. All rights reserved.