LPL Enhancement Request - Add ability to create Field Rules at business class level

We would appreciate your vote of approval for the following enhancement request.

Configuration Console currently does not support/allow you to write Field Rules (edits) at the business class level (for delivered business classes). This means if you want to ensure the edits are followed, regardless of action, you need to code the Field Rules in multiple locations. This requires a.) additional time to research which additional actions might require the same code, b.) additional development time to implement solutions, c.) creates additional/unnecessary configurations requiring support during CU upgrades, and d.) if you don't take into consideration these actions allowing unexpected data within your system which can cause negative impacts.

This enhancement request is to add the ability to write field rules at the business class level allowing for you to write the edits once and be followed regardless of what action is being run.

The enhancement request is: 89400

And a direct link to endorse it can be found here: Enhancement Request 89400

Thank you for your time and consideration.

Find more posts tagged with

Accepted answers

All comments

andy

Can you provide an example of where the inability to modify delivered field rules is a shortcoming?

0712131256598360.doc

cleverly

I'm not the author of the enhancement request (though I have already endorsed it). We would find it VERY helpful.

To use just one example, on the FSM PayablesInvoice business class, in several countries where we have business units the invoice numbering must follow certain government mandated standards.

We end up having to put in place an ActionOverride with an Entrance Rule to check and see if the PayablesCompany is located in one of these countries, and, if so, add a constraint check to make sure the Invoice field is syntactically well formed for the local requirements. To make sure it is always enforced we have to create a separate ActionOverride for each Create & Update action (and since the business class implements state cycles there are multiples of each).

It would be much nicer to just be able to define it once for the business class and be done with it.

Chad Dirst

We would like to ensure the ShortDescription on the Supervisor business class does not exceed 10 characters as that the maximum field length in Lawson S3.

We create an action configuration for the Create action and add the edit there. We ensure we do them in actions in the event someone comes along with ISD and does an upload. Next we need to add the same code to the Update action to ensure one doesn't get changed after initial creation. In reading the delivered actions we also see there are loop holes unless we put this same code in the ImportRecord, ImportHistoricalRecordLite,etc... actions.

We want the ability to write a rule once and have it be followed regardless of action being run.

andy

Thanks for the follow up Michael and Chad. That makes sense, and I agree such a change would be helpful, though I think it might be difficult to implement. Nevertheless, you've got my vote.

cleverly

It looks like you were correct Andy that it would be difficult to implement... but at least they are still seeking example use cases so they can try and explore other solutions. (Please add a comment on the enhancement request if you have any!)

I added the following suggestion as a comment on the ESR:

Right now Landmark has ActionOverrides that give us a hook to run on Entrance (prior to the delivered action) or on Exit (after the delivered action). Rather than User Field Rules (which this enhancement originally proposed but which development says isn't possible), would it be more feasible to give us the capability to have an ActionTypeOverride on a Business Class basis? Essentially a way to define an action override for all creates, or all updates, all deletes, etc. I would expect that the sequence would be: 1. Run the Action Type Override Entrance Rules (if any); 2. Run the specific Action Override Rules (if any); 3. Run the delivered Action LPL; 4. Run the specific Action Override Exit Rules (if any); 5. Run the Action Type Override Exit Rules (if any).

0911060553270289.pdf

Copyright © 2025 Infor. All rights reserved.