Skip to main content


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

Prioritizing information in tables

Updated on December 13, 2022
Applicable to Hybrid mode applications

Ensure that important information is always displayed by specifying which columns have the top priority.

Depending on the width and number of columns, and the screen resolution, the application interface might hide some columns to save space. You can define which columns are the most important in a table to ensure that they are always visible to users.

Before you begin: Add a table to your application by defining a data relationship list in a step. For more information, see Creating fields for capturing data.
  1. In the navigation pane of App Studio, click Case types, and then click the case type that you want to open.
  2. In the work area, open a case by clicking Save and run.
  3. In the open case, navigate to the view with the data relationship list that you want to edit.
  4. In the view with the data relationship list, click Configure this view.
  5. In the configuration panel on the right, hover over the data relationship list that you want to edit, and then click Modify this list.
  6. In the Columns list, arrange the order in which the columns are displayed by dragging the field names.
    The item on the top of the list is automatically given primary importance.
  7. Save the setting by closing the configuration panel.
  8. Optional: To preview the table on a mobile device, in the navigation panel, click the mobile preview options.
    In the mobile preview, the primary column is displayed as a header above other data relationship items.

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