At the moment we have at least attributes that affect field UI representation and data mgmt:

• read-only state
• default value
• locale

Those three are logically connected and depend on each other, i.e. changing a locale to a new language must ensure the default value is set and should not trigger ReadOnlyException if read-only mode is on.

Currently the support of these attributes is scattered between various components involved in Admincentral form framework, e.g. FieldFactory, Transformer, TransformedProperty and even I18nAuhoringSupport, more to come.

Obviously since amount and complexity of the fields we ship is quite large - there are cases when something works not correctly (e.g. MGNLUI-3488, MGNLUI-3489, MGNLUI-3424, to some extent - MGNLUI-3221).

What we could do - is to take step back and see how we could implement the same functionality given all the features we had to add since the first effort.

The goal would be to try to move functionality to the places where it belongs and to make the handling of these attributes more transparent.