Conditional WF checking cust state=no hits on null val

Questions
1

I have a workflow conditioned to fire when a group’s boolean custom state=no.

But it’s being triggered when that custom state’s value is null.

Is this by design?

Thank you!

TF

2

yes, it is.

1 Like
3

There is no “empty” when it comes to true/false with bubble… Empty = false.

2 Likes
4

thank you

1 Like
5

I suspected as much. I’ve just gotten myself into a logic trap as I rely on “ignore empty values” to return different versions of a repeating list from only one search. Guess I’ll figure that out in v1.5 :confused:

6

I could test it again to see if it was ever fixed (doubt it) but I had this issue: How to Sort Yes / no (Bool) type on Repeation Groupe - #2 by tylerboodman

7

This topic was automatically closed after 14 days. New replies are no longer allowed.