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.

About skins and CSS style sheets

Updated on September 10, 2021

 This presentation is part of the Portals Overview Self-Study Course.

Transcript

Changing the skins and style sheets can radically change how your UI is presented.  Out of the box, the standard Portal rules utilize the "User" type and "Metal" skin.  For backwards compatibility, you can set the portal to the "Classic" type with a "Classic" skin.

If you set the portal to a Type of "User" with a "Classic" skin, it will NOT present you the same look as a 4.2 PRPC system.

If you have the portal set to a type of "User" and the skin set to "Metal," and you would like to select from a variety of metal skins, you can open the Rule-PortalSkin via the class explorer.  In the PortalSkin rule you will see the first tab is labeled "Styles" in this section.  You can choose the specific style sheet you would like applied to the various screens such as the desktop, workform, reports, and rule configuration screens.  Each one of these four screens is a record in the Rule-File-Text class with css as part of the key name.

The magnifying glass at the end of each line (screen) allows the user to "preview" that portion of the application to which the style sheet applies.  For example, if you want to try a variety of workform displays, click the magnifying glass on the line starting with "Work".   A pop-up will display the work object view in the current style.

Once you have the pop-up displayed, you can choose from the various options in the drop-down labeled Style Name.  For example, you can select "css/workform_mac".  When you do this, all of the various headers change as well as some of the icons in the dialog box.

The Style Picker is an excellent tool to use to evaluate and test changes you make to the style sheets and UI presentation.

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