Is there any best practice approach to follow when we need to merge existing pre-Pega7 skin styles for an application with the new Pega7 skin. I did not find much info on the topic during my search, but from what I gather, the best practice is to leverage the OOTB Pega7 supplied skin and make changes in it to suit the app needs. Is there a quick way to do the merging - like directly using pre-upgrade css files etc. directly in the skin rule - rather than manually reviewing and making changes to formats etc. which will be a high effort task?
**Moderation Team has archived post**
This post has been archived for educational purposes. Contents and links will no longer be updated. If you have the same/similar question, please write a new post.
yes, we need to leverage the styles from the earlier skin rule - not sure whether this was generated using branding wizard. Customer's pega version is 6.2Sp2. It is a Compliance level-2 upgrade with complete UI responsiveness. Yes, layouts and controls are being updated. Basically, customer wants to retain the look and feel for the majority of components even after achieving a level-2 upgrade.
To answer this question "Is there any technical reason why I cannot leverage the existing CSS for compliance Level 2 upgrades ?"
The earlier skins (V 4 / 5 / 6) were not confirming with CSS Level 3 ( basically they lack cross-browser compatibility). Pega7 uses CSS Level 3 skins only ( to achieve cross-browser compatibility). So the skins from the earlier versions cannot be reused in Pega7.
To answer this question "Post Pega7 upgrade my customer is still insisting on Pega6 look and feel. How can I achieve this ?"
Pega7 has few OOTB skins that look and feel like Pega6.2 and you could build your custom skin by leveraging them.
For example we could customize EndUser62 and build a new skin on top of it. Don't get carried away by the name, its one of the OOTB Pega7 skins which makes your application look and feel like V6.2 also this skin uses "formats / mixins" just like any other Pega7 skin.