Skip to main content


         This documentation site is for previous versions. Visit our new documentation site for current releases.      
 

Adopting the Pega Cosmos design system

Updated on December 21, 2020

Pega Customer Relationship Management 8.5 includes two Pega Sales Automation applications: one built on UI Kit (PegaSalesAutomation.8) and the other built on the Cosmos design system (PegaSalesAutomationCosmos.8). To use applications built on the Cosmos design system, change the built-on application to PegaSalesAutomationCosmos.8.

For more information about how to change the built-on application, see "Updating your built-on application" in the Pega Customer Service and Pega Sales Automation 8.5 Upgrade Guide on the Pega Sales Automation Product page.

For more information about Cosmos, see Pega Cosmos Design System.

Important:

Use the PegaSalesAutomationCosmos.8 application unless you need any of the following applications or features:

  • Integration with Pega Customer Service and Pega Knowledge Management
  • Market Development Fund (MDF)
  • Close plans
  • Timeline gadget
  • Organization trends

If you need any of the applications or features listed, use the PegaSalesAutomation.8 application, which is based on UI-Kit.

To adopt Cosmos, use the following scenario:

  1. Upgrade your application to version 8.5.

    For more information, see the Pega Sales Automation 8.5 Upgrade Guide on the Pega Sales Automation Product page, Pega Sales Automation for Insurance 8.5 Upgrade Guide on the Pega Sales Automation for Insurance Product page, Pega Sales Automation for Healthcare 8.5 Upgrade Guide on the Pega Sales Automation for Healthcare Product page, or Pega Sales Automation for Financial Services 8.5 Upgrade Guide on the Pega Sales Automation for Financial Services Product page.

  2. Depending on the level of customization, to adjust your application to use Cosmos, follow the suggestions in articles below:

    For any UI-related update that you made, you must first analyze the changes and their impact, and then point to the Cosmos-based application.

  3. Review all the access groups in your implementation layer and ensure that they point to the User Portal portal.
  4. Review all the roles in your implementation layer and modify the inherited role from product layer to point to the Cosmos equivalent.
    For example: The ImplLayer:SalesRep role inheriting from the PegaCRM-SFA:SalesRep role must be modified to inherit from the PegaCRM-SFACosmos:SalesRep role.

Have a question? Get answers now.

Visit the Support Center to ask questions, engage in discussions, share ideas, and help others.

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best.

Pega.com is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us