There maybe use-cases where such parametrized variables have a benefit but as a more general approach it's just dividing the work to two places without reducing the complexity. Rather the opposite will be happens - the readability will be poorer and you get problems if you want to use multiple values or expressions within your parameters.
Therefore I would probably just use "simple" expressions which contain all of the conditions.
Thanks for your reply. Yes I am agree with you of using simple expressions.
But for some business scenarios I am trying to generalize a list of expressions that can be used in multiple dashboard apps. In such use-cases just trying to incorporate the common business requirements.
Not only the readability of the expressions, but also the performance hit needs to be checked.
In this case it might be more useful to maintain the variables with their expression-content externally maybe within Excel. Within this posting: Variables are several links how this could be done.
From a performance point of view there is no difference if an expression is directly written or if variables contain the expressions (unless the expressions are slightly different - beginning with an equal sign or not, different number of spaces or brakets and so on are creating a different hash of the expressions and they couldn't be cached together).