[ https://jira.jboss.org/jira/browse/TEIID-606?page=com.atlassian.jira.plug... ] Steven Hawkins resolved TEIID-606. ---------------------------------- Resolution: Done Changed all console property panels to only have a concept of hiding expert properties - and insured that required properties without a default are not treated as expert (which is a metadata error). Previously we've ensured that no required values are marked as expert - however is perfectly fine to have a required value in an expert field as long as it has an acceptable default. In general we have too much metadata: required from multiplicity 0..1, 1 hasDefault expert hidden preferred modifiable which gives us 64 possible state combinations. we should simply treat hidden should mean the same as !modifiable, and !expert should mean the same thing as preferred. Assuming that !modifiable means to not display the value regarless of the other metadata. That leaves us with only 8 states to consider based upon required/expert/hasDefault - but there's only 1 state we even care about the presense of a default value (other than for a display color). That leaves us with: required expert modifiable outcome t t t 1) Valid only if there is a default value, then it's an Editable property that should only be shown in expert mode t f t 2) Editable property that should always be shown f t t 3) Editable optional property that should be shown only in expert f f t 4) Editable optional property that should always be shown -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira