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 May 10, 2021

Pega Customer Relationship Management 8.6 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.

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

Pega Sales Automation Implementation Guide

All of the Pega Sales Automation features use the Cosmos design and you can also use Cosmos if you want to integrate with Pega Customer Service even though Pega Customer Service is not Cosmos-based. Pega Sales Automation features will use Cosmos and Pega Customer Service will use UI Kit. It is recommended to use Cosmos because some 8.6 features are built in Cosmos only, for example, Cisco Webex Productivity Tools, or Zoom. To use these features and stay up to date with the latest design and functionality, select PegaSalesAutomationCosmos.8 as the built-on application.

To adopt Cosmos, use the following scenario:

  1. Upgrade your application to 8.6.
  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.
  5. Review the Lead case type in your implementation layer and ensure that the case life cycle includes primary stages.

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. is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us