Skip to main content


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

Specifying a skin for your application

Updated on December 13, 2022
Applicable to Theme Cosmos applications

Define a unified look and feel for your application by linking a skin to an application. A skin ensures that all portals within an application derive UI settings from a single source, which helps you maintain a consistent interface that is easy to update.

If you do not specify a skin for your application, the application uses the default pyEndUser skin.

  1. In the header of Dev Studio, click the name of the application, and then click Definition.
  2. In the Presentation section, in the Skin field, enter the name of the skin that you want to associate with the application.

    The list of available skins depends on your operator profile and might include skins that are not available in the current application. By default, the list of skins includes several out-of-the-box skins that represent the App Studio color themes. The names of these skins start with pyEndUser, such as pyEndUser_Flame.

    Skin settings in the application definition
    Skin is set to the out-of-the-box pyEndUser_Flame theme.

    Note: If you save an application with a skin that is not available, the application defaults to pyEndUser at run time. For upgraded applications, the skin also defaults to pyEndUser when you open and save the application rule.
  3. Click Save.
  • Specifying a skin for a portal

    Give your portal a look that is different from the rest of the application. By setting up a separate skin for a portal, you ensure that the portal does not share the design of the application, which gives you greater creative freedom.

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