Establish Constellation as your UI framework with one click simplicity

User Experience
1

1.png

This option is available in Infinity 25 on the Application Definition of traditional UI based application. When one clicks this it creates a new application with Constellation and the traditional UI applications as the built on applications.

I am on Infinity 23/24, can I create a new application with similar built on applications structure and will it give me the same behaviour as this, i.e., a blended UI application (traditional UI blended with Constellation)?

Thanks

Atanu

2

@Atanu Sen

Yes you can, read some more here: Pegasystems Documentation

For implementation, follow the information in these links:

Blending Traditional UI and Constellation | Pega Academy?

3

@Atanu Sen Yes, you can. Earlier Infinity version needed you to add the traditional ui case one at time. This new wizard makes it really easy to create the constellation app that blends the traditional ui cases by taking all the cases in one go - thus giving you a quick start in the constellation app. you can create insights, dashboards and landing pages in the modern constellation portal, and plan the incremental modernization of each blended traditional case

4

@SrinivasKakani - Do we have/create a list of Pega’s Strategic Apps (FW) that have migrated to Constellation and for the ones that have not, the roadmap?

If a Pega application is built on a Pega FW and that Pega FW has not been migrated to Constellation, that application also cannot be migrated to Constellation? correct?

5

@Atanu Sen -

Your understanding is correct. We do have constellation implementations of multiple strategic applications. Migrating an existing client application to the newer technology needs an individual assessment. Broadly, apps built on the platform can leverage the market place tooling / blueprint to analyse and move to constellation; you have a path to bring Pega Customer Service based apps using process fabric to make both modern and traditional implementations to coexist; Pega Sales automation based apps can use the SA constellation version that replaces the traditional UI version as the base to migrate. Yet other strategic apps, like Smart dispute, or accelerators like AIM have brand new constellation implementations. Client apps would benefit by truly modernising their implementation and leveraging these new capabilities instead of considering just a move of technology. Blueprint is a great tool in this regard. And further analysis tools are coming to the marketplace soon. Let me check on the list of migrated strategic apps.

6

@SrinivasKakani Thank you.

7

@Atanu_Sen @RonaldDeLignie @RonaldDeLignie Say we have one Constellation based frame work layer . One traditional Implementation application-Theme cosmos based ( customer facing) is built on top of this Constellation Framework layer . I need to reuse , few Constellation based landing pages , from this traditional Implementation application . If we update our Traditional implementation application with Blended ui setting ( application tab ->Use Constellation UI to render landing pages ) and necessary DSS changes -->will it be possible to achieve ?

8

Yes, personally, this is my most preferred approach to adopting Constellation. It’s low risk and slowly introduces Constellation into the app.

I’ve had success with this at a few clients, but Platform and CS, reusing Constellation landing pages like Explore Data and Dashboards (plus a couple of others).

9

Thanks @MarcCheong for the Update .

@SrinivasKakani @RonaldDeLignie @Atanu_Sen @MarcCheong

In our case , we have a Legacy Framework layer ( Built on Theme Cosmos) , which act as a built on to few Customer facing Traditional Implementation application .

Now , Client is having vison to modernize this Legacy Framework layer .

We are exploring different options on this .

Option 1( Full Migration with Co -existence) : -

  • Use OOTB Modernization tool for doing full migration in Legacy Framework layer and create a new Constellation framework layer , which will be built on Legacy Framework layer .
  • Pick one of the Implementation traditional application , update its stack to point to the newly created Constellation Framework . Update this Traditional ,Implementation application to have Blended UI flavour (application tab ->Use Constellation UI to render landing pages ) and use the reusable asset from Constellation Framework layer .
  • Later -Migrate this Traditional Implementation application as well to Constellation .

Option 2( Full Migration ) :-

  • Use OOTB Modernization tool for doing full migration in Legacy Framework layer and create a new Constellation framework layer , which will be built on Legacy Framework layer .
  • Use OOTB Modernization tool for doing full migration in Implementation application and create a new Constellation Implementation application , which will be built on the Traditional Implementation application .
  • Update the stack of new , Constellation Implementation , to use Constellation Framework application .

How ever , we would like to know few clarifications from this Expert Panel on the below :-

  • Say from the existing Traditional application , user is clicking some Local actions -which internally start a case type from Constellation Framework layer . Whether , this use case is going to be supported as part of Co-Existence ?
  • Say from the existing Traditional application , user is clicking some Local actions -which internally start a Flow action from Constellation Framework layer . Whether , this use case is going to be supported as part of Co-Existence ?

Apart from Option 1 , and Option 2 -do we have any other plans for this overall requirement ?