You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Dashboard explains that some model objects' fields are 'Critical for licencing configuration'.
Forms for those objects editing mark those fields as 'mandatory'.
A model object can have a potentially arbitrary set of fields that are crucial for the object instantiation. These fields are 'mandatory'.
'Critical for licencing configuration' fields are less numerous and, besides being mandatory, should also suit more strict requirements: must be readable, talkative, informative.
So the corresponding ui controls should have a specially dedicated decorator. That would be also useful for a user to achieve some textual explanation (tooltip?) advising the nice-to-have merits for such a field's value.
Dashboard explains that some model objects' fields are 'Critical for licencing configuration'.
Forms for those objects editing mark those fields as 'mandatory'.
A model object can have a potentially arbitrary set of fields that are crucial for the object instantiation. These fields are 'mandatory'.
'Critical for licencing configuration' fields are less numerous and, besides being mandatory, should also suit more strict requirements: must be readable, talkative, informative.
So the corresponding ui controls should have a specially dedicated decorator. That would be also useful for a user to achieve some textual explanation (tooltip?) advising the nice-to-have merits for such a field's value.
Version: 0.4.0
Ported from bugs.eclipse.org: 546503
Ported from Eclipse Passage issue 960
The text was updated successfully, but these errors were encountered: