most often, booleans are true/false.
but a lot of the time there is also an “unknown” status.
accepted, declined, unset/unkown.
in other languages this translates to: true/false/null
I'm pretty sure booleans are a very core feature of MX, so not likely to change, but creating an Enum just to add a “null” status seems overkill.
maybe we can have an advanced button, to extend it with unset/unkown/null.
this would save a lot of random Enums needing to be created in applications (or converting booleans to Enums, because the specs werent clear)