Skip to main content

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 Portal rules

Suggest edit Updated on September 13, 2021

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

Transcript

The appearance of the Process Commander user interface (UI) is based on several factors that are coordinated by portal rules. The portal rule form specifies skins, gadgets, menus, and toolbars, all of which provide the HTML or XML that renders the UI.

Skin rules identify a collection of style sheets, or .css files stored in the PegaRULES database as text file rules.  These style sheets are used to format the appearance of the portal.

Gadgets are rectangular areas on a portal display.  Each gadget contains a control that a user can interact with.  For example, sections of pages that appear in the left navigation pane and the workspace panel are gadgets.  Specifically, gadgets are HTML stream rules that belong to the Data-Gadget class. They provide the JSP code that renders a section of the page in the browser.

Portal rules are part of the User Interface category of rules in Process Commander and the Portal instances are found in the Rule-Portal class.  Most portal rules have five tabs: 

  • Skins
  • Tabs
  • Custom
  • Options
  • History

However, Developer portal rule instances only have the Skins, Options, and History Tabs available.

Did you find this content helpful? YesNo

33% found this useful

Have a question? Get answers now.

Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.

Ready to crush complexity?

Experience the benefits of Pega Community when you log in.

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