Skip to main content

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

Migrating artifacts to support multiple customer contexts

Updated on December 20, 2021

This content applies only to On-premises and Client-managed cloud environments

If you want your application to use multiple customer entities, edit any artifacts you created in your implementation layer before the upgrade, and migrate them to one of the child classes of the Data-Decision-Request class.

Pega Customer Decision Hub Update Guide

In Pega Customer Decision Hub 8.5 and newer, you can use the Context Dictionary to define multiple customer entities, the relationships between these entities, and any associated data. You can use additional customer context to build segments and launch campaigns. Using multiple data contexts allows you to better target your marketing efforts at multiple levels. For more information, see the Pega Customer Decision Hub User Guide on the Pega Customer Decision Hub product page.

Legacy artifacts created before the upgrade are still supported in Pega Customer Decision Hub 8.5, but to increase future compatibility and take advantage of the latest functionality improvements, it is recommended that you migrate your customer class, offers, strategies, and any other marketing artifacts to the Data-Decision-Request class.

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