To successfully load customer data, a customer class must be configured.

The customer class represents the customer entity in Pega Customer Decision Hub for Financial Services. The base customer class is PegaMarketingFS-Data-Customer, which is backed by the ExternalMKTData table in the outbound marketing schema. Pega Customer Decision Hub for Financial Services utilizes the external mappings defined on the customer class to load up customer data.

• Creating your customer class

  To support loading customer data, create a customer class that extends the base customer class and has as its only key the property that you identified in Defining the customer class. The default customer class key is CustomerID.

• Mapping a customer class to a database table

  After creating and configuring the class rule for your customer, create a database table instance to map your customer class to a database entity (table or view) in the marketing schema by completing the following steps.

• Optional: Creating a class key property for an extended customer class

  By default, the key of the customer class is the CustomerID property that is used to store customer IDs. If your extended customer class uses a different class key, for example, CIFNBR, then you must create two copies of the CustomerID property and rename them to the same name as your custom class key.

• Adding associated customer entities

  Pega Customer Decision Hub for Financial Services supports associating the customer class with other entities. For example, each customer record can have associated purchase data information. After creating the customer class, create and configure any associated entities.

• Setting the context for your customer class

  Use the Context Dictionary to review or update the default contexts, configure a different primary context, or add an additional customer context.

• Extending and updating the CustomerSearchResultGrid section

  After creating a custom customer class, you must extend the rules that are related to list segments. This is necessary so that your application can use customer data from your extended customer class.