Optimizing the access to customer data
The amount of data required for a party differs when the party is onboarded as a customer versus and added as a related party.
When party is added as a related party, only limited data is enough to perform different assessments (for example, a risk, KYC significant flag, AML CDD profile, and so on). In these situations, retrieving the complete customer data from the System of Record (SoR) introduces an unnecessary performance overhead that, when working with a high number of related parties or with slow integration points, might have an impact on user experience.
The Pega Client Lifecycle Management for Financial Services comes configured by default to use the same integration point in both situations. This configuration facilitates the implementation of the application by reducing the number of integrations with the SoR. However, if your organization wants to optimize the access to the SoR, it can use a new integration to perform a light retrieval of customer data.
Extension points to invoke to the new integration
| Rule name | Rule type | Usage |
|---|---|---|
| D_GetCustomerBasicDetails | Data page | Use to get basic details of the customer from the SoR. |
| D_GetPrimaryContactDetails | Data page | Use to get basic details of primary contact from system of record. |
To simulate this configuration and demonstrate the benefits of implementing a new integration point, the application comes with a dynamic system setting to enable the direct access to the sample tables of the application. The setting is used in the two data pages listed in the table above. To activate the configuration, modify RPNewGeneration/UseQuickDBAccessForCustomerData by setting value to true to enable direct access to sample tables. The default value is false.
Previous topic Configuring completion logic Next topic Optimizing the construction of related parties network