Upgrading Application Built on UI Kit to Theme cosmos or Constellation UI

Currently we are upgrading pega platform from pega 8.x to pega 24. All our application are built on UI Kit.

Based on best practices suggested by Pega Choosing a UI (pega.com) and Constellation UI (pega.com) , there is recommendation to stay/continue on existing UI Architecture (i.e UI kit) when there are small extensions to existing application. Does this recommendation hold good.

If its hold good, how long will UI Kit continued to be supported.

Hi @NaveenR2750,

UIKit 15 is the last stable version that is released from Pega’ end. Till today if we are building an application on Pega Traditional UI we can utilize both Theme Cosmos or UiKit.

In the latest release notes of Pega Infinity 24 we see that Pega has added new accessibility features on the Pega UiKit architecture (Pegasystems Documentation) , this clearly indicates that UiKit is still a recommended Ui framework which can be utilized to build apps.

Hence you can continue the usage of Pega UiKit 15 on you latest upgraded environments.

@NaveenR2750

In your case, it might hold good for now for small extensions. However, please keep in on the following items.

  • If your existing application requires extensive rework, use Constellation.
  • Keep existing applications that require small changes and expansions on their current architecture. Consider using Constellation components in traditional UI for expansion. For applications with Theme Cosmos, upgrade to the latest version of the Cosmos theme Ruleset (Theme-Cosmos) in the Application Definition.
  • 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 any new case types, please make sure to select Standard (using Constellation technology). This will facilitate future migrations as the required artifacts will be generated upon selecting this option.