Skip to main content


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

Configuring the data model

Updated on May 30, 2022
Note: Skip this procedure if you configured the data model for your industry when running the Pega Customer Decision Hub setup wizard.

Pega Customer Decision Hub requires a customer class to support the loading of customer data. The recommended way to implement a customer class is through the use of Pega-provided data model (xCAR) accelerators whenever they are available.

Accelerators help organizations go live with their applications in a shorter time and provide guidance on best-in-class Pega practices.
  1. Go to Pega Marketplace and download the data model for your industry.
  2. Install the component by doing the following steps:
    1. In the header of Dev Studio, click ConfigureApplicationDistributionImport.
    2. On the Import Wizard tab, click Choose File, and then select the file that contains your xCAR data model.
      For example, the healthcare xCAR data model file is PegaCDHxCARforHC.zip.
    3. After the file has been successfully imported, in the header of Dev Studio, click the name of your implementation application, and then click Definition.
    4. Click Manage Components.
    5. In the pop-up window, select the xCAR data model component that you imported.
    6. Select Enable, and then click OK.
    7. On the application form for your implementation application, click Save.
    8. In the header of Dev Studio, click ConfigureApplicationStructureRuleset Stack.
    9. Verify that the ruleset corresponding to the imported file is above PegaMarketing_FW:8 in your application stack.
  3. Save the shipped customer class into your implementation ruleset by using the Save as option.
  4. Open the customer class that you saved into your implementation ruleset.
  5. In the Class inheritance section, select the Find by name first (Pattern) check box, and then as the parent class, enter the shipped customer class.
  6. Create the database table rule that maps the class to the customer table.
    Note: To help ensure future compatibility, save the shipped database table into your own implementation ruleset, and then map the class to the new database table.
  7. For any associated data or additional contexts, save the page list properties that are used to link your data together into your implementation ruleset, and then update the page definition of your implementation class.
  8. Define a new association rule to associate your classes.
    Note: If you are adding associated data, you do not need to manually create the association rule. It will be done automatically for you when you add your associated data in Customer Profile Designer, as long as the property that you are associating on is the key of the class.
  9. Update the context dictionary based on your new classes and page list properties.
  10. Define static or stream data associations in the Customer Profile Designer.
  11. If you want to add additional properties, do the following steps:
    1. Add the property to the new implementation class.
    2. Expose the relevant column in the customer table.
    3. Update the External mappings tab of your class definition.
    4. Add the property to relevant records and categories as needed.
For example:

The following video demonstrates how to use the xCAR data model component to configure the customer class while implementing your Pega Customer Decision Hub application:

  • Previous topic Deployment options for storing customer data
  • Next topic Adding associated static data in the Customer Profile Designer

Tags

Pega Customer Decision Hub 8.7 Decision Management

Have a question? Get answers now.

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

Visit the Support Center

Did you find this content helpful?

Yes
No

Want to help us improve this content?
Suggest an edit

We'd prefer it if you saw us at our best.

Pega.com is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us