Description of problem:
Custom properties go through input validation in the GUI, during which a UI field is marked as invalid if the value doesn't fit the regular expression for the specific custom property as configured in the DB.
However, currently the error displayed upon hover on the invalid UI field uses the regular expression itself to explain why the input is invalid - this is incomprehensible for a typical user.
When configuring a custom property, I suggest to allow adding an optional validation explanation. If no such text is supplied, then the current explanation may be used by default.
Even though this will only used by the GUI, I have marked it as core it should be managed on a per custom property basis (i.e. different custom properties have different regular expressions, therefore could have different validation explanations), which is handled at the DB level and performed by users via engine-config. And likely all other layers up to the GUI will have to be modified to accommodate this.
One small correction: the validation explanations won't necessarily be used exclusively by the GUI, they could also be embedded in the errors returned by the backend for better readability when using REST.
Related to Bug 1119265.
Any solution that is config-based currently won't support localization (see comment in Bug 1119265). Will consider including that in 3.6.
I would advise to wait for the PatternFly UI overhaul in which we will be able to solve similar problems for other fields as well, potentially -> not sure if should be targeted for 3.6.
Comment 5Red Hat Bugzilla Rules Engine
2015-10-19 10:58:54 UTC
Target release should be placed once a package build is known to fix a issue. Since this bug is not modified, the target version has been reset. Please use target milestone to plan a fix for a oVirt release.