Migrating artifacts to support multiple customer contexts
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.
In Pega Customer Decision Hub 8.6 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.6, 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.
Previous topic Verifying the Pega Customer Decision Hub application