Skip to main content

         This documentation site is for previous versions. Visit our new documentation site for current releases.      

Data objects in Pega Customer Decision Hub for Financial Services

Updated on August 27, 2020

The Pega Customer Decision Hub for Financial Services application includes an extensible data model which consists of seven main data objects.

To better understand the application data model, see the following definitions of each data object:

The Customer data object is the main data object that contains the customer data such as home address, email address, and phone number. The data object also includes a summary of assets and liabilities.
The Accounts data object contains a flattened list of all customer banking accounts. The data object includes the following accounts data types: Deposit Accounts, Loan Accounts, Investment Accounts, and Credit Card Accounts. Accounts define the details of all customer-owned accounts such as balances, description, account status, and important account dates.
Behavioral Data
The Behavioral Data data object contains data collected during a real-time banking activity. The banking activity is conducted by a customer through any digital channel, for example, a web page or a mobile app. Behavioral data stores customer actions, such as the customer viewing their account balance or visiting a mortgage page.
Note: For performance and data volume reasons, Pega recommends that you configure behavioral data as Decision Data Store-only. For more information, see Deployment options for storing customer data.
The Prospect data object defines the prospect data model. In the CRM scenario, prospects are saved into the customer data model and identified with the flag IsProspect.
The Opportunity data object defines the details related to a Sales Automation opportunity such as opportunity owner, Sales Automation product type, or status of an opportunity.
Note: This data object is available only if your implementation application includes the PegaMarketingFS-CRM ruleset.
The Lead data object defines the lead related details such as email, phone number, and stage.
Note: This data object is available only if your implementation application includes the PegaMarketingFS-CRM ruleset.
Credit Card Transactions
The Credit Card Transactions data object defines the transaction details that include amount, currency, merchant category code, description, important transaction dates, and merchant locations of credit card account transactions.
  • Data object relationships

    The five main data types are interrelated through defined associations in the context dictionary.

  • Rule types used

    The application data objects are implemented through data set rules. Data sets represent a data object and can be logical, physical, or both.

Have a question? Get answers now.

Visit the Support Center to ask questions, engage in discussions, share ideas, and help others.

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best. is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us