I would like to use a decision table to determine a particular display configured as an expression. If an object is of type A and Status B, then display rule!AB. The configured expression would not take in any inputs and is only for display purposes.
Discussion posts and replies are publicly visible
This is super ghetto but you could always wrap the decision in an expression rule and direct the expression rule to call different [expressionable] outcomes based on a particular plaintext output from the decision.
Though at that rate, it seems hardly worth it to even bother with the decision rule anymore - which is why I've ended up hardly ever using them.
Kind of. The use case is perfect. I don't want to create some giant if statement, but it looks like that's the only option.
Your decision could just return integers 1 - N, then an expression rule wraps it in a choose() statement, to avoid a thousand nested if() levels.
But yes I agree, decisions will only ever be actually useful for any use cases more complicated than very simple ones and/or demos, when they're more expressionable in the inputs and/or in the outputs.