LPL Code for Changes to a Form

Hi,

Can someone provide LPL code on how to handle the following situation. On the PO main form, when someone hits manual approve for a PO, we want to add some LPL code for an exit rule on the manual approve action where the code would check to see what fields changed during the previous save action and if only certain fields changed like delivery date then we would allow the manual approve to occur, but if other fields changed a warning message would appear saying you cannot manually approve the PO - must go through the normal approval process.

The ultimate goal would be to allow for some minor changes to the PO without having to go through the PO approval process a 2nd or 3rd time, but if the PO change was big enough like a price change then manual approve wouldn't be allowed.

What is the LPL code or syntax that shows a change occurred to a field on the form and can the developer know what exact fields changed to store it or reference it later to make that if case on the manual approve action.

If delivery date changed then allow manual approval

else

warning message - don't allow manual approval

Thanks.

Jeff

Find more posts tagged with

LN Development

Accepted answers

All comments

andy

One way to accomplish that would be to loop through the audit log records in a for loop and break after you've completed the desired comparisons.

Something like this...

    Count = 0
    for each audit log records descending
        if(Count < 1)
            if(each.DeliveryDate != DeliveryDate)
                AllowApproval = true
        else
            end for each
        Count += 1

There's also "old" and "changed" operators, so you could possibly just use those for field comparison.

    if(DeliveryDate != old DeliveryDate)
        AllowApproval = true

    if(DeliveryDate changed)
        AllowApproval = true

cleverly

If you were running an exit rule on the update action itself you could directly use the changed field condition (see page 43 in the current LPL guide) to test whether certain fields had changed or not; similarly, you could access the prior value for those fields that had changed using the old field operator (see page 14).

ManualApprove, however, is an instance action, so I think you'll need to iterate through the audit log records using for each audit log records (see pages 20-21).

Within that loop you can get a list of changed field names which is apparently a csv string of the fields that were changed. You can use action type to test whether or not the change was from an Update or not. One of the only places I could find it used in FSM is in the PurchaseOrderLine business class. Here's a screenshot from the LPL viewer in Configuration Console—this is a Rule Block definition that gets included in the definitions of a couple of derived fields:

You can find other examples of for each audit log records being used in the business class LPL for these FSM business classes:

ContractImportGPOMembership
ContractLine
ContractLineDistributionSpread
ContractLineMember
ContractSpread
ProjectAssignmentEffort
ProjectAssignmentLabor
ProjectEmployee
PurchaseOrderLine
SampleDocumentTemplate
SourcingEvent
SourcingEventResponse

cleverly

<blush>I had this tab open from last night and didn't see that Andy had already responded with essentially the same ideas before I hit submit.</blush>

[quote userid="68127" url="~/infor-developers/f/ln-development/36833/lpl-code-for-changes-to-a-form"]we want to add some LPL code for an exit rule on the manual approve action where the code would check to see what fields changed during the previous save action and if only certain fields changed like delivery date then we would allow the manual approve to occur, but if other fields changed a warning message would appear saying you cannot manually approve the PO - must go through the normal approval process.

Unless I'm misunderstanding something, be sure to check all prior saves (at least back to some prior approval step). Otherwise someone could, either intentionally or inadvertently, make sequential changes and the ability to manually approve would depend on which one they did last.

If you only look at the immediately proceeding update then:

Copyright © 2025 Infor. All rights reserved.