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.

Learning about portal structure

Updated on April 5, 2022

A portal is an interface through which users interact with your application. By applying the principles of modular design to your portals, you can create optimal work environments with greater flexibility and less effort.

Pega Platform applications use a modular UI which encourages prototyping, and design consistency. You can reuse out-of-the-box UI components, group them into structural clusters, or nest one component inside another.

For portals, the most basic structural component is the harness. Harnesses organize the structure of the user display. When you create a portal in App Studio, Pega Platform automatically creates an associated harness to contain the screen layout. If you design your portal in Dev Studio, you must manually create a harness and associate it with a portal.

Harnesses comprise sections. Each section defines the content of one part of a user interface, such as the navigation pane or a header. You can populate a section with properties and controls, and choose a template to organize the section in a consistent manner. Like harnesses, sections are reusable and support nesting – you can embed a section inside another section.

  • Creating and managing pages for applications

    Present additional resources to users by creating, configuring, and adding pages to menus in your application.

  • harnesses

    Organize the content and structure of a portal by defining harnesses. By populating harnesses with sections, you can build a modular interface that promotes reuse and maintainability.

  • Sections

    Sections are the building blocks of your user interface. You can populate a section with components, such as fields and controls, to create a functional chunk of user interface that can be reused in different contexts for improved consistency and efficient development.

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. is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us