Lawson 9.0 Personnel Action Rule

Hi Paul. It sounds like your trying to secure the select drop-down "Reasons" correct? Well you'll need to create a rule on the Element 'code' (and perhaps 'type') as defined in dbdef PCODES table.

My question is what is the business rule that defines which reason codes are should be visible based on the action code chosen?

Anyway..securing elements is tricky..I've done it successfully once before and it was a lot of trial and error.
Good luck.

Paul, I have to second Alex's opinion, in that I'm not a big fan of coding business rules into Security. In fact, my opinion is that Lawson probably made a mistake in opening up security too much. I think what happened is that it was SO limited in LAUA that they got really tired of hearing about it. Consequently, they essentially said, "OK clients, you said you wanted more control over security--here it is--go configure it!" and decided to open EVERYTHING AND ANYTHING for security rules. It's just a disaster waiting to happen, as clients start coding logic / rules into the security.

Think about that for a second...what happens a year or two from now, when nothing's documented and everyone's gone (hopefully I'm exaggerating a little!)?

My ideal way of handling what you're asking for is to code the business rule via a user exit (where it properly belongs, in my view) based on perhaps a custom table of valid combinations.

Thank you Both!!!