Suppose there is an existing Application MyApp which is built on 2 Applications, one 1. SmartDisputeIssuersAll which is eventually built on UI-Kit and 2. OrgApp which is built on Theme-Cosmos. Now I want to change this application entirely to Cosmos and don't want to refer UI-Kit screens anymore.
The approach that I have taken is :
I have changed the inheritance path for MyApp Skin. Now it is inheriting CosmosSkin.
Also saved the necessary Harness and Sections from Theme-Cosmos to my Case Type work class, otherwise it was referring to UI-Kit versions of those rules, this way I can see I am getting the cosmos UI properly.
However I saw there are few UI-Kit sections which are getting loaded in some particular instances and I was unable to find any Cosmos versions of those sections in Pega. Is there any documentation how we can completely override UI-Kit with Cosmos? Also kindly suggest if you are aware of any other approach to implement this requirement.
***Edited by Moderator Marissa to update Platform Capability tags****
@RichardMarsot Is there any plan for releasing any SD version which will be built on Cosmos and not UI-Kit? Why I am asking this question is when I am trying to migrate from UI-Kit to Cosmos for an Application which is built on SD, then I can see all the SD specific sections are loading in UI-kit format ( because the whole SD framework is built on UI-Kit) and it doesn't look good. So I am trying to modify all these sections manually, but this is a lot of development effort. Moreover as we are updating on the current SD version so we can face problems while installing new patch versions of SD in future. Can you suggest any other way?
Posted: 1 month ago
Posted: 25 Aug 2021 11:20 EDT
Richard Marsot (RichardMarsot)
Director, Front-end Development