As per the title. If you have :formatted as text, you might think that only the yes or no expression would be evaluated. This is not the case. Let’s take an example condition; Current User is Current User. This is always true. Current User is Current user:formatted as text: Yes: Do a search fo…

Wow, that seems like behavior that’s just screaming to be optimized. Have you reported it? I don’t think I’ve ever used a search operation in that context, but even with WU considerations aside, it seems quite inefficient with the potential to adversely impact performance.

And against this announcement from my point of view [image] [Small performance optimization] boolean operators can now shorthand Announcements Hi everyone, I would like to let you know that we have just rolled out a small change to our evaluation engine, which we believe …

Hmm, we sure about this? I have an API call, the contents of which are dependant upon circumstance, so is something like “This Orders Payment Method is Invoiced:Format at text” Yes = A particular set of values included nested objects No = A particular set of values, not including nested objects I…

To clarify, you mean both searches get called and evaluate their values, but only the truthy comes out as a result of the operator? I too have never experienced issues with the operator and I use it in a ton. Though if true, not good for WU.

[image] ihsanzainal84: you mean both searches get called and evaluate their values, but only the truthy comes out as a result of the operator? Exactly. I confirmed the behavior before I posted my response. It’s actually quite simple to reproduce. With the following setup… [formatted-as-text…

[image] sudsy: Have you reported it? Yes, they say they know about it and all formatted as text expressions are pre-emptively evaluated. I’ll send the full response + test case tomorrow for people in the thread that are curious

Is this the case on both client side and serverside expressions?

[image] georgecollier: the full response I’m going to go on a limb here and say it will be similar to the responses I get when reporting bugs about WUs

I’ve reviewed your video and was able to replicate the behavior in your app when running the call in Postman myself, with and without the formatting as text. I looked into past engineering context that we have internally on this, and indeed it seems like the current behavior is to preemptively loa…

So it looks like this was an intentional decision that factored in the speed of searching vs the speed of execution. Knowing how slow searches are in the chain of events, they just frontloaded it rather than making you wait for the search to complete. There are lots of tradeoffs like this when it …

PSA: :formatted as text evaluates both yes and no options

Tips

Jici April 15, 2025, 8:44pm 3

And against this announcement from my point of view

But this announcement was before the parenthesis feature… maybe this has changed something?
@fede.bubble

Topic		Replies	Views
Search: count is 0? Or Search:first item is empty? Tips	65	14677	April 25, 2024
Workload Units Charging very Inconsistent Bugs	17	261	September 2, 2024
Performance Q&A guide Tips	122	39964	January 15, 2024
Searches - When do they run? How do we optimise them? Database	15	409	November 1, 2024
Submit your WORKLOAD questions! Tips	32	2319	January 21, 2025

PSA: :formatted as text evaluates both yes and no options

Related topics