Hi All,
We were planning to implement Theme cosmos for our existing application(Our application has more than 21k rules).
2.What is the benefits of using Theme cosmos in our existing application.
3.When I’m trying to create the section rule, the view is getting created with same name(Is this an ASIS behavior or a new change)
Thanks,
Aishwarya
I hope the below article helps :
Also Theme Cosmos architecture makes the application run on the Single Page Application model where the platform tends to only reload the required elements when needed this overall enhances the performance and the application load time.
Also with Theme Cosmos you will be to incorporate the Url Mapping and would be able to create hybrid apps where you can utilize the landing pages from Constellation architecture.
please find below answers for your requirement
1.Identify and document all the UI rules (sections, harnesses, etc.) that will be impacted by the transition
2.the application is responsive and works well on various devices, including desktops, tablets, and smartphones
3.Transitioning to Theme Cosmos in your existing application involves careful planning, rule conversion, and thorough testing. The benefits include a modern, consistent, and responsive UI, which can significantly enhance user experience and application performance. Ensure you understand the changes and leverage Pega’s resources to facilitate a smooth migration.
Please find my inline answers
You have to tweak the section rules and more particularly table layouts to leverage the new features available in Theme Cosmos
2.What is the benefits of using Theme cosmos in our existing application.
Better look and feel. Portals Dashboard and table layouts are enhanced compared to UI Kit application.
3.When I’m trying to create the section rule, the view is getting created with same name(Is this an ASIS behavior or a new change)
Yes, this is expected.