Help with Security Rule on PA52.1 Effective Date

I have been asked to apply a security rule on PA52.1 that would restrict our end users from entering specific Action Codes with effective dates that are earlier than the employee Hire Date. Someone accidentally entered a PA with a 'very wrong' effective date and it passed through the approvals..... This should be fairly simple to do but here I am two days later... and I'm beginning to feel like I've falling down a rabbit's hole. I swear, I've written rules like this before but naturally now I cant find any of them.

I've modified the rule to be similar to: if( (form.PCT_ACTION_CODE=='NEWHIREII') && (getDBField('EMPLOYEE','DATE-HIRED',form.PCT_COMPANY,form.PCT_EMPLOYEE)<=form.PCT_EFFECT_DATE). That was no good because the DATE-HIRED is returning 2018 September 10 (where does that come from?) and PCT.EFFECT_DATE is 09/10/2018. I've tried a multitude of combinations, incorporating the use of strToNum and dateFormat functions and can't break through this. Any suggestions would be greatly appreciated. PS: I did see somewhere that there were issues with the dateFormat at one time, but can't seem to find the related KB now.

Also, if anyone is aware of a listing anywhere that shows what the valid DateFormats for this security function are, I would love to refer to it because when it is really wrong - the error is 'outside of IOS'. Additional insight into why the getDBField is returning the date in the format of '2018 September 10' instead of a something simple, like maybe the SQL value of '2018-09-10' or even 'yyyymmdd' would also be appreciate. (Possibly the user locale def ?.?.?)

Find more posts tagged with

Infor Lawson Technology Group - Discussion

Comments

unknown

Another possible option since you mentioned approvals would be to look at this in IPA (effective date vs. hire date) and then reject the action and send an email to the creator so they know what they did wrong.

unknown

Great thought Kyle! We may end up having to go that route since a completed approval and process creates a mess. Thanks!

don-peterson

If I'm understanding this correctly, what is wanted is something like:

If effective date entered is less than the hire date, and the action is NEWHIREII, then notify the user that an invalid date was entered.

If you are using the Portal this could be done with Design Studio (or Scripting in Smart Office). In the OnBeforeTransaction event, that is before it goes to the server, add script to retrieve the hire date from the employee record, then compare it to the date entered. Then display a message for the user, showing the hire date. Then set the focus to the Effective Date field. The OnBeforeTransaction event would then do a "return false" so that the call does not go to the server.

Then make this Design Studio Modification the default view.

Don

unknown

A very good suggestion Don! Your interpretation of the restriction is accurate and the record should never even be entered into the system. Currently we are using a design studio form for the PA Inbasket approvals only and the Lawson delivered form for PA52.1. Since some of our actions can be processed immediately and override the approval process (which would never get to the process flow), this may be a better course of action. We try to reserve custom processes such as Pflows and DS forms as much as possible so there is less to maintain and migrate during upgrades but sometimes there are no other choices.

Copyright © 2025 Infor. All rights reserved.