Today I found a problem regarding evaluation of logical functions and boolean va

Today I found a problem regarding evaluation of logical functions and boolean variables with null values. The function "and(null())" evaluates to "true", "or(null())" evaluates to "false" and "not(null())" tells me that null parameters are not allow. Adding some true() or false() values to the and() and or() functions return correct values.

When I bring the if() function into play which always handles null() values to false() the whole behaviour looks quite inconsistent to me. I think that "and(null())" as well as "or(null())" should evaluate to "false". The function "not()" should take null() values as "false" and for consistency "not(null())" should evaluate to "true"....

OriginalPostID-125072

OriginalPostID-125072

  Discussion posts and replies are publicly visible

Parents
  • As a computer scientist I understand that very well as well as the surrounding implications. What I want to say is: Do we want to bother a process designer with this? Even I would want a NOT that handles a NULL like FALSE for example just because I do not want to think of a 3-state boolean.

    In more than 5 years with Appian I had several cases like this. Maybe we can get rid of one.

    Maybe someone is listening who is in Amsterdam next week so we can discuss this.
Reply
  • As a computer scientist I understand that very well as well as the surrounding implications. What I want to say is: Do we want to bother a process designer with this? Even I would want a NOT that handles a NULL like FALSE for example just because I do not want to think of a 3-state boolean.

    In more than 5 years with Appian I had several cases like this. Maybe we can get rid of one.

    Maybe someone is listening who is in Amsterdam next week so we can discuss this.
Children
No Data