Condition wildcards

Impacts presets for scenario- and column-definitions if they contain conditions with ? or * wildcards.

When defining scenarios and columns within presets, it is possible to specify an optional conditions which limits the amount of tests shown.
In case of scenarios, the test is simply filtered out if it does not match. In case of columns, other or no attribute values are picked to be displayed.

For example, conditions can be specified like:

attribute_x EQ '42' OR attribute_y EQ '42' OR  attribute_z EQ '42'

The above condition can be simplified by using wildcards:

attribute_* EQ '42'

or

attribute_? EQ '42'

Note, that the condition has been broadened as it will now also match other attributes, like attribute_a etc. In the cases we observed, this was used nevertheless, as the existence of those other attributes could be ruled out.

By using wildcards like ? and * the performance to evaluate this condition drops, as the application needs to consider many more possible variants, even if the user knows that they do not exist.
In an effort to keep the performance in a usable range, wildcards are now deprecated.

It is still possible to simplify those conditions by using the [|] notation to list possible variants. For the above example, the condition can be written as:

attribute_[x|y|z] EQ '42'

As a bonus, this does not broaden the condition as well.