I see 3 different ways to indicate required fields in the system:
1. "asterix" generated from form widget when required-field="true" (55
occurrences + 346 auto-fields-service occurrences which also have some
required fields)
2. "gray background of text field " done by widget-style="required" (122
occurrences )
3. "required" the label is set in FTLs and also in form widgets using
tooltip="${uiLabelMap.CommonRequired} (280 occurrences )
There are also different combinations of above 3 ways
I don't know why there are 3 different ways and what is the current best
practice but I think we should agree on one way to indicate required
fields and use it all over the framework.
Here is what I propose:
Remove all the ${uiLabelMap.CommonRequired} tooltips from form
definitions. The tooltip should be used to provide other information as
it is for not required fields (the purpose of the field, the format)
Remove all the widget-style="required" from form definitions.
If a field is required, (on form widget) set only its attribute
required-field="true". In cases when the form is based on service
definition (auto-fields-service) it is not neccessary to set this
attribute. Then no need to add tooltip="${uiLabelMap.CommonRequired} or
widget-style="required" attibutes on the form definition. The renderer
should decide how to indicate the required field.
Change form renderer, so if a field is required it is indicated by
asterix plus required style ( same as widget-style="required")
WDYT?
Bilgin Ibryam
