Skip to main content


Table layout structure

Suggest edit Updated on April 11, 2020

Tables are flexible user interface components that help you present large amounts of information in a clear and consistent way. Because tables can be quickly customized and expanded, they provide a reliable basis for users to view or compare information.

For example, tables in a price comparison application can help users quickly identify the best offer.

Regular Table layouts automatically source data from a property, report definition, or data page, and display it like a spreadsheet, in aligned columns and rows. Hierarchical table layouts additionally support expandable rows, which you can populate with hierarchical data, like in a navigational tree.

A table layout consists of the following areas:

Layout area
The framework that contains the action and repeating areas. You can define the header format, header type, and the overall width of the layout area.
Repeating area
Between the action areas, the system displays information that is dynamically created from the data source. The first row in the repeating area holds the column headers representing the data source fields. Subsequent rows display the requested data.

Non-optimized tables also have action areas, in which you can place actionable elements, such as Add Item or Delete. You can also place action buttons in a repeating row to provide quick access to actions that do not require further user input, such as Flag for Review.

  • Creating a hierarchical table layout

    Help users access and compare nested data with a Hierarchical table layout. Hierarchical table layouts support expandable rows, which can provide you with a more compact view of your data.

  • grid

    Help users access and compare data with table layouts. Use tables in your applications as a flexible basis for users to process large amounts of information. For example, tables in a price comparison application can help users efficiently identify the best offer.

  • Accessing the UI Gallery

    Explore sample, guardrail-compliant design patterns that have been built by using the various features and layouts of Pega Platform.

Did you find this content helpful? YesNo

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

Close Deprecation Notice
Contact us