Major differences between traditional UI and Theme Cosmos components
Theme Cosmos can support a hybrid architecture where most components retain the classic server-side rendering, but portal authoring components and list views use a React-based library. This approach produces a more efficient and dynamic interface, while leaving most Pega Platform functionalities unchanged.
The hybrid mode promotes ready-to-use low-maintenance solutions for portals and landing pages. Consequently, some classic Pega Platform components might work differently in this environment, or might not be supported. The following table lists some of the changes to the design process.
For more information, see Enabling hybrid mode.
| Component | Change in Theme Cosmos |
| Authoring | You cannot edit Theme Cosmos portals and landing pages in Dev Studio. |
| Custom sections in portals | Custom sections that you insert manually into the portal harness might not work correctly in a Theme Cosmos environment. Best practice is to use the default sections, such as PortalNavigation for navigation, and edit them in the App Studio Channels menu. |
| Editable data pages | The application deletes the pages at the end of a requestor cycle. |
| Full case view | If you use App Studio to build new case types in existing applications, the end-user experience renders the full case view with the Cosmos React implementation of the Cosmos design system. |
| Tables | Theme Cosmos offers enhanced performance for rendering, sorting, filtering, and grouping tabular data. This feature covers tables on landing pages, inside case pages, and tables in the Explore Data page. |
Previous topic Personas Next topic Configuring portals