Loading your data to the customer analytics data store
Populate your customer data into the marketing repository by using the batch ETL process, file dump, or file injection.
Pega provides data flows that demonstrate how to import data from a relational database record into the Decision Data Store (DDS). These data flows are provided only to pull data from other Pega tables.
Start by identifying the data objects that are required by your use cases. At a minimum, the Customer data object must be loaded. Extend the data flows listed below that corresponds to the data object required for your decisioning. Create your own where necessary.
Data flow Data object Usage DF_GetCustomerData Customer Copies and saves customer information into the Customer Decision
Data Store. DF_GetCreditCardAccountsData Credit Card Accounts Copies and saves credit card account information into the
CreditCardAccountsDecision Data Store. DF_GetDepositAccountsData Deposit Accounts Copies and saves deposit account information into the
DepositAccountsDecision Data Store. DF_GetInvestmentAccountsData Investment Accounts Copies and saves investment account information into the
InvestmentAccountsDecision Data Store. DF_GetLoanAccountsData Loan Accounts Copies and saves loan account information into the
LoanAccountsDecision Data Store. DF_GetAccountDetails Account Calls DF_GetCreditCardAccountsData, DF_GetDepositAccountsData,
DF_GetInvestmentAccountsData, and DF_GetLoanAccountsData and merges
and flattens all the account details into one table. DF_GetSAFSC2ORelationships Organization Copies and saves the Sales Automation contact to organization
details into the table CRMFS_CUSTOMER. DF_GetSAFSO2CRelationships Organization Copies and saves the Sales Automation Opportunity details into
the table CRMFS_CUSTOMER. DF_GetSalesOpportunityData Opportunity Copies and saves the Sales Automation Opportunity details into
the table PMFS_OPPORTUNITY_REPOSITORY. This is meant to be used for
segmentation only. DF_GetSalesLeadData Lead Copies and saves the Sales Automation Opportunity details into
the table PMFS_LEAD_REPOSITORY. This is meant to be used for
segmentation only.
In order to pull the records from the source tables, class definition rules need to be created and mapped to each relevant database table. A report definition is then needed to pull the records. For example, in DF_GetCustomerData, the Pega Foundation for Financial Services database tables FSF_SAMPLE_CUST, FSF_SAMPLE_CUST_ADDRESS and FSF_SAMPLE_CUST_COMMS are mapped to through the respective class definitions and pulled from the referenced report definitions. The records of these three tables are merged in the compose shape based on a common key.
Create a class for each of their source database table and define properties that map to the columns in those tables relevant to their intended decisioning logic. Create a report definition to pull those properties and then create or update the existing data flows to do the actual storing.
Use an agent to run these data flows to load the values into the DDS. This way, it can be scheduled as a reoccurring process. Pega Customer Decision Hub for Financial Services provides the agent PegaCDHFS that runs the activity StoreCustomerRecordsinDDS as a reference. By default, this functionality is disabled.
To enable the functionality:
- Open the agent rule PegaCDHFS and select the Enable check box.
- Restart your system.
- Check that the agent schedule rule for PegaCDHFS has been updated to include an enabled StoreCustomerRecordsinDDS.
You can also trigger the activity StoreCustomerRecordsInDDS to refresh the data in your xCAR. Customers should keep in mind that they should update and extend this activity to suit their implementation data model.
A similar agent-run activity exists for the CRM-specific data with the activity StoreContactsInDDS.
Previous topic Data model details Next topic Loading your data from the customer analytics data store