The relationship between itemMappings, itemViewMappings, and propertyViewMappings illustrates an important concept in the View Mapping system: view mappings are simply a system of global (or default) settings, which are overridden in specific instances where a deviation from the default is necessary.

An itemMapping contains a reference to a list of itemViewMapping objects, which represent tabs in the view. For example, an asset whose properties are organized for display purposes into three separate tabs has three itemViewMappings listed in the corresponding itemMapping. The itemMapping also has a list of attributes that are passed to each tab. However, each itemViewMapping has its own attributes that can override the defaults; for example, the itemViewMapping can specify an itemView that overrides the default itemView used for that asset type. In addition, each itemViewMapping contains settings that define the appearance of the tab, for example its display name.

Each itemViewMapping also contains a list of propertyViewMappings, which are the property-level overrides that are in effect for this tab. For example, if the property assetX.prop1, which is a String, requires a different property editor from the default simple String editor, the propertyViewMapping for assetXprop1 contains a reference to a propertyView that overrides the default.

For more information on the attributes of each object, see View Mapping Repository.

 
loading table of contents...