Standard Skin rules

Your system contains several standard skin rules, most with availability set to final (). You can copy them (using a new name) and alter the copy. These skins differ only in appearance. You can choose any skin to use, or to copy and adapt as a starting point for your application.

You can use any one of the following approaches to review the appearance styles defined in a skin:

• You can choose the default application skin for your portal. This points to the skin specified in the application, ensuring that all portals in your application have the same look and feel. You can select the skin in the User Interface, Skin field on the Application form's Definition tab. The default skin is pyEndUser.

• You can use a different skin created in the application for your portal by updating the Skin field in the User interface panel.
• To override the application or portal settings when running processes from Designer Studio, set the Using skin preference.

Name	Description
CompositeBrand	Recommended for composite portals. Lighter styles.
Developer	Metallic look with compact work item styles. Referenced in the standard portal rule Developer.
pzDesignerStudio	Styles for the Pega Platform Designer Studio portal. See Designer Studio basics.
pyEndUser	Styles for the Pega Platform Case Manager portal (pyCaseManager7). See About the Case Manager portal.
EndUser62	Styles for the Case Manager and Case Worker portals in PRPC Version 6.2 and later.
MetalBrand	Metallic styles for composite portals.
pxLiteBrand	Pale gray and blue for composite portals.
pxMacBrand	Mimics Apple MAC styles for composite portals.
pxXPBrand	Mimics Windows XP styles for composite portals.
User	Metallic look with compact work object styles.

About Skin rules

Open topic with navigation