I dont want to create mulitple workflows just to handle this only when condition :
Im using custom states here:
run this workflow only when–> page’s page status is A and scanned value is (B or C)
Thank you for your answer
I dont want to create mulitple workflows just to handle this only when condition :
Im using custom states here:
run this workflow only when–> page’s page status is A and scanned value is (B or C)
Thank you for your answer
I would say you could do that…
only when page_status is a and pages scanned_value is b or pages scanned_value is c
Last week I was building a feature and learned a ton about expressions…stuff I didn’t even know was possible.
I thought I had one expression that was kind of long. So I asked AI if it had seen any that were longer and more complicated.
It gave me an example of a long expression and said:
It’s like Bubble meets War and Peace — you scroll halfway through that expression and start questioning your life choices like,
was this supposed to be an app… or a manifesto?
Some of those real-world expressions are honestly legendary. You can practically hear Bubble’s database whispering,
“Please… make it stop…”
Anyway, most of those super-long expressions don’t need to be super long if things are set up right.
Yours is an easy expression.
Good luck with your project
You have to be careful with that. Bubble evaluates from left to right.
That’s why you have to put the “AND” condition at the end. The correct condition would be:
“scanned value is B” OR “scanned value is C” AND “page’s page status is A”
Good eye…
you’re absolutely correct.
Thanks for correcting me
Thanks guys
So that means, Bubble’s evaluation of using “AND“ “OR“ conditions together isnt random. It will always evaluate left to right. Thanks for your insights !!!
It makes no difference between:
(page’s page status is A) and (scanned value is (B or C))
(scanned value is (B or C)) and (page’s page status is A)
The position of the conditions in the sentence only matters if the expression doesn’t include an AND clause. When AND is used, both parts of the expression must be validated anyway.
If the condition used OR instead, then it would make sense to place the simplest or fastest validation first — because if that part evaluates to true, Bubble stops reading the rest of the expression. In other words, from a WU consumption standpoint, that order could make a difference.
However, from a logical standpoint, the final result would remain exactly the same.
That’s correct if you use parentheses.
We were referring to plain Bubble conditions without parentheses.
In plain Bubble conditions
X and Z or Y
(which was first suggested)
is not the same as
X or Z and Y
(which was my correction)
When conditions are even more complicated, a handy technique is to convert each logical clause to a number and then evaluate the sum–along the lines of the following untested illustrative mock-up: page’s page status is A:formatted as number and scanned value is B or scanned value is C: formatted as number = 2
I thought parentheses were already incorporated natively… I didn’t even know it was still possible to make an expression without them, like the ancient Mayans did.
There is wisdom in the old ways