Skip to main content
LinkedIn
Copied!

Table of Contents

Adopting the Pega Cosmos design system

Version:

Only available versions of this content are shown in the dropdown

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.

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.

    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.

Did you find this content helpful?

Have a question? Get answers now.

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

Ready to crush complexity?

Experience the benefits of Pega Community when you log in.

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

Pega Community has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice
Contact us