Skip to main content


         This documentation site is for previous versions. Visit our new documentation site for current releases.      
 

This content has been archived and is no longer being updated.

Links may not function; however, this content may be relevant to outdated versions of the product.

Inheritance

Updated on April 5, 2022

The inheritance tab displays the parent styles for the current skin.

In the Skin inheritance text area, enter the name of the parent skin from which you want to inherit styles. Click the crosshairs icon to open the parent style sheet. Click the trashcan icon to delete the parent style sheet.

The Calculated inheritance order displays the precedence structure of the parent and child skins. Click the crosshairs icon next to the skin name open the skin.

  • Skin rules

    Use the skin to specify the presentation of your content. You can style all presentation elements of your interface in the skin, including typography, borders, backgrounds, layouts, and the placement and alignment of elements.

  • Skin rules - Completing the Create or Save As form

    Create a skin or update an existing one to specify the presentation aspects of your application.

  • Mixins tab of the Skin rules form

    Use the Mixins tab to define mixins (reusable style patterns). Mixins can define a reusable typography, border, or background style, or a style that is a combination of these styles. Using mixins helps ensure consistency across your user interface, maximize re-use, and minimize future maintenance.

  • Base Settings

    The Base Settings tab sets the style for container or layout selected in the component styles tab.

  • Component styles (custom style formats)

    Use the Component styles tab to define the presentation of components by creating custom style formats. After you define style formats, reference them on property panes for sections, harnesses, and controls.

  • Skin form - Included Styles tab

    Use this tab to select which style sheets to add to the skin, and select the components to be supported in your application.

Have a question? Get answers now.

Visit the Support Center to ask questions, engage in discussions, share ideas, and help others.

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best.

Pega.com is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us