Hi, There is no specific document created for customer master profile implementation in CLM.
At a high level, Customer Master Profile’ data entity, represented by class ‘PegaFS-Data-Party-MasterProfile’, is a very important entity in the Customer-centric data model. It is a specialization of data entity ‘Party’, so it shares it complete data model and behaviour.
It represents the local copy of the actual Customer. This copy is intended to keep in the system a local copy of the driving Customer data. As the complete Customer related data will reside in the Financial Institution systems of record, likely to be external to the application, the systems needs to rely on a local copy of the driving data in order to function without depending completely on those external systems of record. Driving data is understood to be which directly drives the Financial Services Customer journeys, like that related to customer risk profiling, compliance elements (KYC profile information), jurisdictional elements, product related, relevant related parties, etc.
By default the PegaFS-Data-Party-MasterProfile class is directly mapped with the database table ‘pegadata.pc_work_masterprofile’. The class PegaFS-Data-Party-MasterProfile counts in his inheritance with some work related classes, so it allows to make use of some work-derived functionality, like history audit track, relationship with other work objects (acting as a Folder, establishing a 1 to many relationship with other work objects where the customer is involved), etc. Additionally it allows storing some of the driving customer data mentioned as a whole within a BLOB data base table column. All the data within the BLOB is not exposed in the table by default.