Types of skins and their priorities
Applying skin priorities
Higher priority skin types take precedence over lower priority types. The following table shows some scenarios:
Scenario | Example |
|---|---|
The skin type View Name takes precedence over the type View Label; which takes precedence over Skin Selector, and so on. | If you have a View Name skin with a blue background and a Form level skin with a green background, the blue background is displayed because the View Name skin has the higher priority. |
If you have multiple skins with the same priority level and the same properties in an application, the skin that was created most recently takes precedence. | If View Name Skin A is created at 08:30 A.M. on 02/07/10 and View Name Skin B is created at 10:30 P.M. on 02/07/10, and both skins define a panel header color. Skin B takes precedence and overwrites Skin A. |
If the two skins define different properties, they do not overwrite each other. | If Skin A defines a panel header color and Skin B defines a background color), Skin B does not overwrite Skin A. |
Applying field display property priorities
Before rendering the HTML for the form, the Mid Tier server uses the display properties defined for the skin to override the field display properties stored as part of the form definition. These properties have the following priority levels:
- Field ID
- Field Skin Selector
- Field Type
Properties for a field skin selector take precedence over properties for a field type. Properties for a field ID take precedence over properties for a field skin selector.