Skip to main content

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

Out-of-the-box user interface capabilities

Updated on February 7, 2022

Pega provides a variety of readily available tools for you to design a comprehensive and functional user interface for your application.

You can create effective interfaces for your application with out-of-the-box elements from the following categories:

Structural components

The following elements govern the structure of forms, pages, and entire portals:

Design templates
Design templates are reusable sections with predefined elements that you can use to build your interface. You can apply design templates to sections to promote consistency, and to ensure that all sections are up-to-date when you alter the template. Design templates cover many user interface scenarios, and require minimal effort during upgrades.
Sample design pattern options
Sample design patterns, including single column options and multiple column options with varying size ratios

For more information, see Design templates.

Layouts form the structure of your interface by being containers for other components, such as fields and buttons. In Dev Studio, you can use layouts to build your own design templates and other custom UI elements. This solution offers more flexibility, but requires more maintenance and development effort during migration to Cosmos React UI.
Sample inline grid layout
Sample inline grid layout that captures personal information, such as name or address

For more information, see Layouts.

Presentational components

The following components govern the appearance and style of your interface:

Skins are rules that help you define the style of your interface and the presentation of your content. You can determine the typography, borders, backgrounds, placement, and appearance of UI elements. Skins separate content from its presentation, so that you can reuse your configurations and keep user interface design consistent throughout your application.
Sample skin with action area settings
Sample skin with action area settings, such as border and background settings

For more information, see Skins.

Cascading Style Sheet (CSS) helper classes
CSS helper classes are predefined classes that help you make minor changes in the format of layouts. For example, you can change the borders, margins, or padding.

For more information, see CSS helper classes.

Behavioral components (Action sets)

Action sets can help you create a dynamic UI in which certain elements appear only under certain conditions. For example, when the user selects their marital status as married, a new section is displayed that collects information about the partner. Action sets consist of the following elements:

User activity that triggers actions. For example, selecting a check box.
System response to an event. For example, displaying a new section.
Conditions (optional)
Restrictions that apply to combinations of events and actions. For example, hovering over a field and displaying a message if the field is empty.
A sample configuration of an action (showing a smart tip) for an event (hover)
The When field in the Condition section is set to empty.

For more information, see Using business logic to drive user experience.

Actionable elements (Controls)

Controls introduce interaction to your interface with such elements as buttons, links, and fields, through which users initiate certain events, such as displaying a screen, saving their work, or advancing a work item.

Sample available picker controls
Sample available picker controls, such as autocomplete, checkbox or dropdown

For more information, see Controls.


UI components in Pega Platform support assistive technologies for a more inclusive approach to users with disabilities. Accessibility features take advantage of ARIA roles that provide additional information about your application to assistive technologies such as screen readers.

For more information, see Building an accessible UI.


Localization helps you broaden your pool of application users by setting the product in an understandable context. You can also use a wizard to automate localization processes, for example, the preparation of translation packages.

For more information, see Localizing your application.

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