Expressions CaseOperation compare with undefined/null

redacted redacted redacted

I would say “null” is not available in the kernel langage. As a workaround, I suggest modeling a helper field, calculated as “true if FieldFilled(UI_Pfad)” and false otherwise, now you should be able to access it in your expression…

Hi @alicia-secure-haze

The undefined fields should work exactly the same as the defined but empty fields in Expressions.

There’s an open bug ticket, A12-16232, which is tackling this problem in the 2024.06 release line.

The workaround proposed by @marieestelle-firm-summit would work in the meantime. You can model a computed helper Field (Boolean):

Precondition Calculation
FieldFilled(UI_Pfad) True
FieldNotFilled(UI_Pfad) False

If you use this helper Field in the case, then everything works.

case [UI_Pfad_helper]= "false" {"Allgemeiner Kommentar"}

The downside is that you have to maintain this extra field.

redacted redacted redacted

The fix for A12-16232 mentioned in the thread is planned for 2024.06-ext3 release.