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.


Updated on April 5, 2022

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.

Sections are instances of the Rule-HTML-Section class and define how an area of a user interface looks. You can display a section in a harness, another section, or a paragraph rule.

Sections use templates that organize content into separate regions. Each region can contain properties, labels, controls, and other sections. You can create a custom template specifically for your application, or choose from several out-of-the-box templates that cover most UI scenarios.

For example, your application may need to display user data as a list of ID cards. To create a section that is the basis of a card, you can apply the list item template to the section, and populate it with references to properties that store user data. You can then include the section in a repeating layout, and the application uses it as a model for all user ID cards in that layout. Because the system sources all cards from the same section, they share the visual design and the type of data that they display. However, the content of each card is different because the data is independent of the user interface design.

  • Creating sections

    Use sections to build a modular user interface that promotes reusability and design consistency. By populating your sections with content, you can create a functional chunk of interface that has a specific purpose, and can be used in many contexts.

  • Sections - Completing the Create or Save As form

    Records can be created in various ways. You can add a new record to your application or copy an existing one. You can specialize existing rules by creating a copy in a specific ruleset, against a different class or (in some cases) with a set of circumstance definitions. You can copy data instances but they do not support specialization because the

  • Adding a role to an access group

    You can assign access roles to an access group so that users who belong to the access group have a consistent set of functions available to them.

  • Configuring advanced settings for access groups

    You can define settings for an access group that are related to authentication, security, connectivity, and accessibility for users and other requestors who reference the access group.

  • Sections Completing the Parameter tab

    Optional. Identify parameters for this section.

  • Declare Trigger form - Completing the Pages & Classes tab

    Use this tab to list the clipboard pages referenced by name in the Triggers tab. See How to Complete a Pages & Classes tab for basic instructions.

  • List View form - Understanding the HTML tab

    HTML tab on the List View form

  • More about Sections

    Pega Platform resolves a reference in a harness to a section during stream processing, by evaluating the<pega: include > JSP tags (or include directives).

  • Viewing generated Java code of Access When rules
  • About HTML Fragment rules

    Use HTML fragment rules to define universally available HTML parts, such as style sheets and scripts, including JavaScript files. During stream processing, a JavaServer Pages (JSP) tag can insert this text into other HTML rule instances.

  • Keystores

    A keystore is a file that contains keys and certificates that you use for encryption, authentication, and serving content over HTTPS. In Pega Platform, you create a keystore data instance that points to a keystore file.

  • About HTML rules

    Use an HTML rule to describe how the system is to assemble, through stream processing, portions of HTML displays in your application.

  • Keystores

    A keystore is a file that contains keys and certificates that you use for encryption, authentication, and serving content over HTTPS. In Pega Platform, you create a keystore data instance that points to a keystore file.

  • Unit testing a Service SOAP rule

    Services start their processing in response to a request from an external application. Before you add the external application to your testing process, use the Simulate SOAP Service Execution feature to verify that the service processes data appropriately. When using this feature, you manually provide some representative data to process. You specify a test page for the rule to use, provide sample data as the input, run the rule, and examine the results to see if they are what you expect.

  • Learning about design templates

    Design templates are reusable patterns that provide form and function for your user interface. Each template includes predefined areas to which you can add application content. By applying design templates to UI sections, you achieve consistency across your application, shorten development time, and reduce maintenance efforts.

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