BO.Attribute IS UNDEFINED ignored as applicable (Solved)

ddumas

In the applicable (display condition)

BO.Attribute IS UNDEFINED ignored as an applicable condition

No error, just ignores the code.

Dave

PointsWell

ddumas wrote
In the applicable (display condition)

BO.Attribute IS UNDEFINED ignored as an applicable condition

No error, just ignores the code.

Dave

Odd. Can you expand please

What is the type of attribute? From memory Dates and time stamps are a challenge for finds

What is the rule that controls display, what do you mean display? Is this something changing on the form as you complete it, or after it has already been completed?

aware_support

This should work. Check out Tomcat output - it will have some diagnostics on how this condition is evaliated

ddumas

BO.Attribute is really Event.Organizer, where Organizer is a reference attribute. I use in Business Rules and in Processes all the time. However, in an "applicable" condition does not work. So, as a workaround I created a yes/no attribute named IsEventOrganizerDefined. I set that in the same Business Rule code that sets the Event.Organizer. IsEventOrganizerDefined='Yes' works fine in the "applicable" condition, so this is why it appears to be a bug in its use there.

aware_support

Yes, if it's a reference attribute use ID as a workaround If Obj.ReferenceAttribute.ID IS UNDEFINED

ddumas

Excellent - I will try that..., thanks.

ddumas

As a workaround, in the applicable condition, if the attribute is a reference attribute, you must use BO.Attribute.ID The addition of .ID is the key here.
Dave