Associate static data, such as database tables, with profile contexts. For example,
you can associate an investment portfolio table with the Account context. You can then use the
data source to build engagement policies and as predictors in adaptive models.
Caution: The relationship with associated entities can be
one-to-one or one-to-many. Pega Customer Decision Hub does not support many-to-many
relationships.
Note: Organizations in the financial services, healthcare, or insurance
industries can use the Customer Profile Designer accelerator component to
speed up MLP implementation, and as an example for building additional Customer Profile
Designer summaries. However, the component is not required for Customer Profile Designer to
work, and you can also complete the steps below without installing the accelerator.
Before you begin: In Dev Studio, create a Database Table data set for the associated entity.
Add the data set that you created to profile data sources:
In the navigation pane of the Pega Customer Decision Hub interaction portal,
click DataProfile Data Sources.
Click AddData set.
In the Add data set window, select the data set, and then
click Add.
In the navigation pane of the Pega Customer Decision Hub portal, click DataProfile Designer.
In the upper-right corner of the Profile Designer landing page, click
Edit.
Identify the context with which you want to associate the data set, for example,
Account.
In the lower-left corner of the context section, click Add associated
data, hover on Data set, and then select the data set
from the list.
Tip: A single data source can only be associated with a single profile
context. You cannot associate the same data source with multiple contexts.
If the data source has multiple keys, in the Data source key
list, select the data source key that maps to the context key.
Caution: The context key is the parent class key of the
context entity, for example, CustomerID. For the mapping, select
the same key from the associated data source keys.
For example: If the context key is CustomerID, select
CustomerID from the data source keys, as in the following
figure:
The mapping creates the association rule and corresponding page or page-list property
in the context entity.
Click Add.
Click Save.
Result: The data set is now associated with the context:
You can review the updated context in the Context Dictionary. To view the Context
Dictionary, go to App Studio, and then in the navigation pane, click SettingsContext Dictionary. The data set that you associated with the context is now listed in that
context's section:
What to do next: For a property on an associated entity to be available as
criteria in a segment, it must be added to the External Mappings of the appropriate context
class.
Previous topic
Using accelerators to configure the customer class
Next topic
Adding stream data aggregates in the Customer Profile Designer