Question
American Express
US
Last activity: 24 Mar 2025 10:44 EDT
Mixing up Traditional(Theme-Cosmos) and Constellation UI together in 24.1(onwards) application
We want to create a new application. This application will reuse some part of an old application (let's say we will take a product extract and will deploy to the new constellation application) which is built on Theme-cosmos, and all new developments should be done using constellation architecture.
From day 1, we don't want to migrate Theme-Cosmos UIs to Constellation, but will do it gradually. In the mean time to continue our development and want to have both the flavors in our application.
I have found this article - https://academy.pega.com/challenge/blending-traditional-ui-and-constellation/v2, which is related to this topic. Trying to find out if there are any other recommendation from product team on this?
***Edited by Moderator Ellen to add Capability tags***
Updated: 24 Mar 2025 10:39 EDT
Pegasystems Inc.
IN
You can refer to this article - Constellation adoption strategies playbook for the different adoption strategies recommended by product team. Based on your requirements and complexity , you can choose the path.
American Express
US
@Aditi Mehta Thanks for the response. A follow up question would be, can a case type created in constellation, reuse few UIs, rules extracted from a traditional/cosmos application, and also new UIs can be built in constellation? The example I found in PDN talks about extending a Case type as a whole into constellation app, can we do it per rule basis?