How to make a field required based on condition in LPL

dheeptha-meenakshisu

I am trying to make a field required in LPL form only based on a condition.

The below command is marking the field with red astrick but its not actually requiring for "Submit".

When the user clicks on "Submit" without entering a value, it still goes through.

Please help how to fix it.

visible when (MSSPayExceptionCurrentGradeIsStep)

valid when(actor.initiator)

MSSPayExceptionStepType

label is "EnterNewStepException"

display as required when (MSSPayExceptionCurrentGradeIsStep)

when value changed

refresh MSSPayExceptionStepUp

0905290750040159.pdf

Find more posts tagged with

LSF/Landmark Development

Accepted answers

All comments

Joseph Van Denburg

Would you add the "display as required" to the field in the form as you have done just to conditionally display the red asterisk - then add a conditional constraint as an exit rule on the action?

0911060553270289.pdf

dheeptha-meenakshisu

Thank you for replying.

I want to add the red asterisk and also make it required on condition. Does it need to be done on the exit rule in action?

Joseph Van Denburg

I have not tested - but that is what I would try. Add a constraint in an Action Configuration Exit Rule.

cleverly

It looks correct...

Is this a User Business Class, or have you added the various MSS* User Fields to an existing business class, if so which one?

A couple of straws you can grasp at to see if they make any difference—

Straw #1

Page 10 of the LPL guide, under General Definitions, says "Scope is defined by indent level. An indent level is 4 spaces or 1 tab." It might be purely an artifact introduced by copying and pasting into the text editor here on the web, but as rendered by the forum software here your LPL has inconsistent indenting. If indenting really isn't a multiple of 4 spaces (I'd avoid tabs), maybe it parses well enough to display the asterisk, but not well enough to enforce the condition?

Straw #2

Does your business logic define any field rules on MSSPayExceptionCurrentGradeIsStep at either the Business Level scope, or at the action level already? I think the later (based on a thread here a few months ago) seems to win out over the UI LPL.

Bonus straw #3

The work around Joseph Van Denburg proposed will work, though depending on any other processing your update [and/or create?] action(s) do you might want to check it as part of an entrance rule rather than an exit rule.

Nathan Baker

I'm interested in how this is solved. We have this requirement as well. On a user business class this seems rather straight forward with a field rule

Field Rules

<field>

required

This presented the visual required clue of an asterisk and an error message on save when the value isn't present.

But my requirement is to make a delivered field on a delivered business class required. I take it we can't add or edit field rules on a delivered business class. So we have to configure the form to display the asterisk and configure the Update action with an entrance or exit rule to require the field?

cleverly

Nate,

Chad Dirst who frequents this forum, has an enhancement request (#89400) that I would encourage you to endorse that proposes that Infor develop some method for customers to functionally achieve the equivalent of additional field rules on delivered business classes.

As far as making an existing field on a delivered business class required, the "display as required" syntax generally works (in my experience).

For example, here is a snippet from the FSM PayablesInvoice MainFormWithTemplate form that I've customized:

                    paragraph
                        GlobalDocumentType
                            display as required when (AriCompanyUsesGDT)

that works to make GlobalDocumentType required when our derived user field AriCompanyUsesGDT is true (which it is for some of our international business units), but optional otherwise.

In this case Dhee is getting the red required asterisk to display, but for as yet unknown reasons (bug?) Landmark isn't actually enforcing it. Using an action configuration to add a constraint in an entrance or exit rule is just a work around.

Nathan Baker

Thanks Michael. That enhancement request is certainly in line with how I wish I could implement field validation. Your and Chad's comments in the request regarding the multiple actions requiring configurations to enforce even the simplest of validations such as mine is spot on.

Attachment_4299.zip

Copyright © 2025 Infor. All rights reserved.