Map the extended data to the Pega classes
After identifying the additional data required by your data model, the additional data needs to be created and mapped to the customer data class.
|Primary role||Senior System Architect|
|Secondary role||Senior Decisioning Architect|
In this task, we are doing a number of steps:
- Create a customer class
- Inherit the shipped customer class
- Add new properties to the properties
- Specify the added customer properties on the External Mapping tab
- Map the customer class to the database table
- Expose the new added properties
- Save your database table rule
- Verify your columns and property mappings
If you have not already, create a customer class and inherit the shipped customer classes as described in detail in the Pega Marketing Implementation Guide for Financial Services.
The Customer table needs to be defined in the ExternalMKTData database and its properties need to be mapped to exposed columns for performance and reporting reasons. An example of the database admin table instance for our new Customer class (here called: MyCo-Data-Customer) is shown here:
Note: You can use the shipped customer table pmfs_customer instead of creating a new one. If you decide to do so, map your database table rule to the table pmfs_customer.
Once this is done, add all the additional properties that are needed in your customer class based on the delta identified in the Task-040501: Perform data mapping workshop.
After all your properties to the customer class, expose all newly added fields through the Pega Database utilities. This is in the navigation options Configure > System > Database.
If you are using Customer Decision Hub for outbound marketing, specifically the segmentation feature, you will need to update the external mapping tab of your customer class with the properties and corresponding exposed database columns.
See example below. By default, any exposed properties through the Pega database utilities are created as columns with the exact same name. For databases that are case sensitive such as DB2, be extra careful when doing this mapping and ensure that your capitalization is correct for your column names.
After making database changes, open your database table rule that maps to the database you have changed and resave it. This is a mandatory mandatory operation that updates the database table structure in Pega.
Validate your column mappings by opening your class, then click Test connection button. If some of your columns are not mapped, you should see the warning “Class <class name> is mapped to external data table <table name> in database <database name>, but the column <column name> does not have the corresponding Rule-Obj-Property <column name>”.
Follow the same set of steps if you need to add any associated data entities.
Additionally, if you have associated data entities in your Data Model, you will need to create the appropriate Page or Page List property in the parent class. E.g. if the relationship between Customer class and Account class is one-to-many, then this property type must be Page List:
Once the Data is mapped, you will have the following rules created for each subject in your extended Data Model:
- Database table
- Page lists