Choosing a UI version
Cosmos React reduces time to value and offers a new paradigm for application authoring that eliminates the need for deep Pega knowledge and front-end expertise. The goal of Cosmos React is to offer common patterns for case management applications out-of-the-box.
You can extend Cosmos React for advanced use cases to build something new, but it is important to verify that Cosmos React offers the business outcomes and capabilities that your application needs.
Best practices overview
Review the following table to select the right UI for your application.
Recommendation | 8.5 | 8.6 | 8.7 |
New applications | Use Theme Cosmos | Use Theme Cosmos | Evaluate Cosmos React |
Existing applications | No UI changes | No UI changes | No UI changes |
Integrations with websites (no professional front-end developer help) | Use mashup | Use mashup | Evaluate web embeds in Cosmos React |
Integrations with websites (with professional front-end developer help) | Evaluate starter packs or DX API directly | Evaluate SDKs or DX API directly | Evaluate SDKs |
Guidelines for new applications
- For new applications that you build from scratch, review the feature limitations
in Cosmos React. If your application requires features that
Cosmos React does not support, use Theme Cosmos.
For more information, see Feature limitations in Cosmos React.
- For new applications that you build on top of existing applications that do not use Theme Cosmos, keep the original UI. For example, Pega Customer Service uses Theme UI-Kit. If you build a new application that is based on the Pega Customer Service application, it must also use Theme UI-Kit.
Guidelines for existing applications
- Keep existing applications built with section rules and Theme UI-Kit on their current UI.
- Keep existing Theme Cosmos applications that use a section-based
UI on their current UI. Consider upgrading to the latest version of the Cosmos
theme ruleset (Theme-Cosmos) in the application definition.
For more information, see Updating Theme Cosmos in your application.
- To shorten future migrations, consider preparing for migration now by checking
existing applications for compliance with the App Studio
delivery approach. Use the App Studio Compliance landing page
to identify non-compliant UI elements in your application, and then plan
development time to address identified issues.
For more information, see App Studio development and Reviewing user interface components.
Previous topic UI version comparison Next topic Feature limitations in Cosmos React