Discussion
Pegasystems Inc.
US
Last activity: 11 Feb 2021 11:56 EST
What questions do you have about the Cosmos design system?
Hi everyone, I work on content strategy for the Product Experience Design at Pega. I'm curious about your thoughts on the Cosmos design system.
- Have you heard of the Cosmos design system?
- What questions do you have about it?
- What do you wish you understood better about the Cosmos design system?
- Are there any points of confusion about the Cosmos design system?
I'm gathering information to identify common themes around areas that we need to clarify, and your answers will help us develop the right type of content.
Infosys Ltd
IN
We tried building some apps using Cosmos in Pega 8.5.2, Widget such as "Attachment" at the right top side, does not get refresh after assignment submission.
Is this expected ? because we have to every time click on refresh button to see if attachment/correspondance got attached to case.
Thanks in advance
Updated: 2 Feb 2021 16:14 EST
CIBC
CA
@RitaReznikova Hi , We are upgrading from Pega 7.2 to 8.5 in cloud and decided to make the cosmos ready by developing on Theme-Cosmos Kit.
But our application is built on PegaAccounting:8 and Pegarequirements:8 which are built on UI Kit.
So what is the recommendation?
1. Do you have PegaAccounting and Pegarequirements application versions built on Theme-Cosmos Application that we can leverage them?
2. Do we have to wait to consume the Theme-Cosmos?
Application Stack:
1.MyApplication
2. PegaFSIF:8 builit on PegaAccounting:8 and PegaRequirements:8 --> UIKIT:15.01-->Pegarules:8
Pegasystems Inc.
US
@Venu gopala krishna Not all Pega Applications have been upgraded to use Theme-Cosmos - For your configuration PegaAccounting and PegaRequirements, you should continue to use UI-Kit
Coforge DPA private limited
AU
Hi @RitaReznikova ,
I would like to know what are the different challenges we can get while upgrading application from UI-kit to Cosmos Theme.
We are about to upgrade to 8.5 and this will be a great help.
Thanks.
Updated: 5 Feb 2021 15:11 EST
Pegasystems Inc.
US
@MadhusudanS9253 thanks for your response. To clarify, you'd like to know more about (1) what to expect during the upgrade process to Cosmos from UI-Kit, or are you looking for information about (2) specific types of problems that you can encounter during the transition, and how to solve for them?
We will be planning some content about upgrade best practices in the future.
Pegasystems Inc.
US
@MadhusudanS9253 For existing applications built what UI-Kit, adopting Cosmos is development effort, not an upgrade.
Similar to the way Google Material design has component implementations in multiple frameworks including Angular and React, Cosmos has an implementation in our current rules-based Infinity architecture (Theme-Cosmos) and is also being implemented in our upcoming React-based front-end. Which implementation of Cosmos to migrate to depends.
Brand new applications in 8.4 and 8.5 most certainly should be built with Theme Cosmos. The Cosmos design system is our UI/UX strategic direction.
If your existing application is simple (few case types; few rule overrides from UI-Kit; few section rules not based on design templates; minimal skin format overrides and custom skin formats; minimal custom CSS) and App Studio compliant, then you may decide to migrate the app from UI-Kit to Cosmos Theme. See this migration guide. (To understand what you need to do to become App Studio compliant, see the Application > Quality > "App Studio compliance" landing page in Dev Studio)
@MadhusudanS9253 For existing applications built what UI-Kit, adopting Cosmos is development effort, not an upgrade.
Similar to the way Google Material design has component implementations in multiple frameworks including Angular and React, Cosmos has an implementation in our current rules-based Infinity architecture (Theme-Cosmos) and is also being implemented in our upcoming React-based front-end. Which implementation of Cosmos to migrate to depends.
Brand new applications in 8.4 and 8.5 most certainly should be built with Theme Cosmos. The Cosmos design system is our UI/UX strategic direction.
If your existing application is simple (few case types; few rule overrides from UI-Kit; few section rules not based on design templates; minimal skin format overrides and custom skin formats; minimal custom CSS) and App Studio compliant, then you may decide to migrate the app from UI-Kit to Cosmos Theme. See this migration guide. (To understand what you need to do to become App Studio compliant, see the Application > Quality > "App Studio compliance" landing page in Dev Studio)
For an existing application that is complex then I recommend holding off and adopting the upcoming React-based implementation of Cosmos; that way you make a single migration from UI-Kit to the React-based version of Cosmos. To prepare for that, the best strategy is to start with converting traditional section rules to use OOTB design templates (or custom design template if your app has a unique repeatable pattern) and becoming App Studio compliant.
As the React-based implementation matures, we'll offer additional guidance on migration.