The best practice is to associate a single skin with your application.

By default, a portal points to the skin specified in the application, ensuring that all portals in your application have the same look and feel. If desired, you can associate your portal with a different skin.

If you do not specify a skin for your application, the default Pega end user skin, pyEndUser, is applied.

To associate a skin with your application:

1. On the Application rule form, click the Definition tab.
2. In the Skin field in the Presentation area, select the skin that you want to apply to this application.

   The list of available skins is based upon your profile and may include skins that are not available in the current application. If you save an application with a skin that is not available within the RuleSets of the application, then the default end user skin, pyEndUser, is applied at run time. To avoid this, log in using the application.

   For upgraded applications, the skin defaults to pyEndUser, the default end user skin, when the application rule is opened and saved.

• Specifying a skin for your application

  The best practice is to associate a single skin with your application.

• 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 UI placement and alignment. By defining presentation attributes in the skin, you separate the content that is defined in sections and harnesses from its presentati

• Accessing a skin

  Skin rules are part of the User Inteface category. A skin rule is an instance of the Rule-PortalSkin Rule- classes Rule-PortalSkin rule type.

• Creating a skin

  Create a skin to specify the presentation aspects of your application.

• Specifying a skin for your application

  The best practice is to associate a single skin with your application.