Action Configuration / Field Rules

Chad Dirst

I am trying to configure an edit on the Job Business Class / Update action using Field Rules.

I am able to add various types of Field Rules to various different fields and they all work with the exception of ShortDescription.  No matter how basic the Field Rule it will not fire.  At its simplest level I can not get the following edit to fire:

Update is an ActionOverride

    Field Rules
        ShortDescription
            constraint (false)
                "TheConstraintFired"

All tabs are correct and I can take the exact same constraint and have it fire under different fields.  Its the ShortDescription field that seems to be the problem.  I can write Entrance Rules for the edit but find the display of inline red text to be much more user friendly and consistent with other edits in the form.  I am also able to write constraints inside of the form itself to simulate the behavior, however, these will not get fired when users use ISD and find Field Rules offer the most simplified approach.  I would also like to understand what is special about this field/situation.  

The only thing I am seeing is there is a delivered Field Rule on ShortDescription.  Is that what could be impacting this.  I would not have expected that to be the cause but maybe I'm missing something.  Please let me know if you have any insight.  Thank you!

cleverly

I love a good puzzle and trying to figure out why Landmark does what it does has taught me far more about LPL than taking the multi-day Infor Campus course ever did.

You asked whether the fact that the base LPL for Job has a Field Rule on ShortDescription made a difference.  I would guess no since Job also has a Field Rule defined for Description and a Field Rule in the ActionOverride fires just fine for it.

I had several hypothesis, most of which I've managed to find counter examples to disprove them.  But maybe the last one holds promise still? 

The ideas I experimented with that didn't pan out:

• ShortDescription was somehow special because it was the first Persistent Field on the Job business class (in the base LPL)?  
  
  Disproven via HRLocation's Description which does fire the rule when a constraint is placed upon it.
  
  
• ShortDescription is marked as translatable in the base lPL and that made it special?  
  
  Disproven since all the other translatable fields on Job seem to fire.
  
  
• The very name "ShortDescription" has some special meaning/behavior?  
  
  Disproven since a field rule for ShortDescription on the Experience business class works.
  
  
• The Job business class has a ByShortDescription Set defined that uses ShortDescription; fields that participate in Sets don't fire rules? 
  
  Disproven since a field rule on Description on the Job business class works and it has a ByDescription Set.
  
  
• Ok, but maybe there is a difference between those sets?
  
  Possibly: the ByShortDescription set is marked as no duplicates while the ByDescription set isn't.  However, there is a counter example in the EmployeeIdentificationNumber which has a ByCountry set that has no duplicates and a field rule on Country does fire.
  
  
• Ok, but does it matter that the ByCountry set is both no duplicates and idexed; the ByShortDescription on Job is only no duplicates (nothing is said about indexed or not indexed)?  
  
  Well, Position has a ShortDescription and a ByShortDescription set that is no duplicates and also doesn't specify indexed or not indexed at all... a field rule on ShortDescription there doesn't fire.  So maybe?

I will try and script up an exhaustive inventory of business classes that have columns that are part of a no duplicates (but specify no other restriction) set and see if I can find a counter example.  

Regardless, it seems like a bug to me.  I'd report it to Support and with a little luck maybe it'll be fixed in 2023.

One workaround I also thought of — but that ended up being a total failure — was to define a "SubType IsUpdate Field Rules" in the ActionOverride.  Configuration Console doesn't accept the syntax even though it will on a User Business Class.