Test for Blank User Attribute

Blank vs. empty might return different results. If my experience is correct, Lawson RM only creates the attribute values when they are populated, so I'm guessing the rules engine probably returns lack of a value as an undefined variable. So you might want to try putting the attribute value into a variable and then seeing if it returns as undefined.
var plc = trim(user.getAttribute('ProcessLevelControl');
if ( (typeof plc == 'undefined') || (plc == '') )
...

Hi John, thanks for the reply!

I am trying to do this as a security class rule in Lawson Security Administrator.   I am a relative newbee to this but I don't think I can use variables that way in a security class rule.  All the statements exist inside the If statement.  How would you get the variable assignment  before the if statement?

(typeof user.getAttribute('ProcessLevelControl')== 'undefined') || (trim(user.getAttribute('ProcessLevelControl'))== '')

Thanks John.

The secret did turn out to be the 'typeof' function, but not comparing to 'undefined'.  I tried, 'undefined', ''null' and I also tried to check for a length of < 3.  Nof of which worked.  However, checking for a typeof 'string' worked.  If the attribute does not contain a value, it is not a typeof 'string'.  If it has a value, it is a typeof 'string'.

Hi Rick,

When all else fails, try this...
(typeof user.getAttribute('ProcessLevelControl') != 'string')
to test for a blank attribute.

We may not know what getAttribute is returning, but if it does not return a string type, then you do not have a value for that attribute.

Marcia