Skip to main content


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

Importing Customer and Account data for decisioning

Updated on June 17, 2021

To make the best, most relevant next-best-action decisions, provide access to the most current and comprehensive data about your customers, their demographics, product holdings, activity, and other information that may be stored in third-party systems.

Populate your customer data into the decisioning repository by using a batch ETL process, file dump, or file injection. For more information, see Ingesting customer data into Pega Customer Decision Hub on Pega Cloud.Note: The Financial Services Customer Analytical Data Model might not include all properties used in this document. You can create additional properties in the implementation layer to support custom requirements.

Importing non-volatile Customer and Account data

Non-volatile Customer and Account data includes context fields that are updated by an ETL job. A batch data flow can be triggered at configured intervals to update XCAR data sources with relevant data from different data stores.

Configure classes for data load by pointing relevant source data set and transform and write into XCAR destination.

Updating volatile Customer and Account data using a real-time data flow

Volatile Customer and Account data are collections status updates coming from a linked Pega Customer Service for Financial Services application, such as Has scheduled payment or Is in collections. You can use REST service which employs existing extended customer analytic record (XCAR) dataset to update data.

For example, a bank sends daily reminders for scheduling payment plans or bill payments to customers who are in collections. The customers' XCAR data is updated every morning through an established ETL process. During the next interaction, relevant next best actions are presented to the customer based on any changes in the status of their associated collection cases.

The steps below outline the necessary configuration by using the Account data set as an example.
  1. Create a REST service that Pega Customer Service for Financial Services can call to update the account data.
    Activity to update account details by using a data set that is called by a REST service
    Activity to update account details by using a data set that is called by a
                rest
                service
  2. Create an activity to write into the Account data set.
  3. When invoking the REST service from Pega Customer Service for Financial Services, provide the mandatory keys to identify the records as part of the payload.
    { "AccountID" : "5989909999990001","AccountNumber" : "5989909999990001","AccountBalance" : "1652.00","CustomerID" : "1365088180","CustomerID" : "1365088180","DaysDelinquent" : "10",}

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.

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

Close Deprecation Notice
Contact us