In the applicable (display condition)
BO.Attribute IS UNDEFINED ignored as an applicable condition
No error, just ignores the code.
Dave
BO.Attribute IS UNDEFINED ignored as applicable (Solved)
BO.Attribute IS UNDEFINED ignored as applicable (Solved)
Last edited by ddumas on Fri Jan 24, 2020 1:41 pm, edited 1 time in total.
-
- Posts: 1462
- Joined: Tue Jan 24, 2017 5:51 am
- Location: 'Stralya
Re: BO.Attribute IS UNDEFINED ignored as applicable conditio
Odd. Can you expand pleaseddumas wrote:In the applicable (display condition)
BO.Attribute IS UNDEFINED ignored as an applicable condition
No error, just ignores the code.
Dave
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?
-
- Posts: 7526
- Joined: Sun Apr 24, 2005 12:36 am
- Contact:
Re: BO.Attribute IS UNDEFINED ignored as applicable conditio
This should work. Check out Tomcat output - it will have some diagnostics on how this condition is evaliated
Aware IM Support Team
Re: BO.Attribute IS UNDEFINED ignored as applicable conditio
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.
-
- Posts: 7526
- Joined: Sun Apr 24, 2005 12:36 am
- Contact:
Re: BO.Attribute IS UNDEFINED ignored as applicable conditio
Yes, if it's a reference attribute use ID as a workaround If Obj.ReferenceAttribute.ID IS UNDEFINED
Aware IM Support Team
Re: BO.Attribute IS UNDEFINED ignored as applicable conditio
Excellent - I will try that..., thanks.
Re: BO.Attribute IS UNDEFINED ignored as applicable (Solved)
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
Dave