Skip to main content


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

Skin form - Included Styles tab

Updated on November 15, 2021
Applicable to Theme UI-Kit applications

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

Component CSS support

Select the check box next to a component that you want to support in your skin. When you build an application, you can reduce the size of the CSS files in your application by selecting only those components that you plan to use in the application.

Select the Include legacy CSS for applications built prior to Pega 7 check box to include support for legacy components and environments. The legacy CSS supports old controls such as tabs or accordions.

When you create a new application and you are not using old controls, do not select this check box.

Additional Style Sheets

Avoid adding custom style sheets to your skin. If you are currently using a custom style sheet:

  • For custom or non-autogenerated controls, you can add these styles to the skin rule as custom styles.
  • To create additional styles for layouts and controls, such as grids, tabs, buttons, and links, you can create new style formats in the skin rule.

If you choose to add a custom style sheet to the skin:

  1. Click Add style sheet and enter the file name. Click the Open icon to create a new file.
  2. Click Save. Note the caution message about maintainability.

The order in which you enter style sheets is significant; the bottom style sheet is applied last. Select the number beside the file name and drag it to reorder additional sheet sheets.

To delete a style sheet from a skin, select the style sheet that you want to delete and click the Delete icon.

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