Skip to main content


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

Optimizing the construction of related parties network

Updated on January 13, 2022

The construction of the related parties network is a demanding process that requires multiple accesses to the database. The system needs to retrieve all related parties from its internal database tables and then enrich each of the results with data from the SoR.

Pega Client Lifecycle Management for Financial Services Implementation Guide

If your organization manages a high number of parties or uses a slow integration point with the SoR, the process might have a significant impact on user experience in the three points where the logic is used: case creation, manage related parties action, and network visualizer. Some organizations optimize this process and use specific integration points to retrieve all the data in a single access.

Extension points to invoke to integration points

Rule nameRule typeUsage

LoadRelationshipNetwork

StructureRecursiveQuickDB

Data transform

Use to retrieve a full list of related parties with minimum data (for example, name, CIF, and so on).

Use current implementation of the rule for reference.

To simulate this configuration and demonstrate the benefits of implementing a new integration point, the application comes with a dynamic system setting to enable direct access to the sample tables of the application. If you want to activate this configuration, modify RPNewGeneration/UseQuickDBAccessForRelNetFetching by setting value to true to enable direct access to sample tables. The default value is false.

  • Previous topic Optimizing the access to customer data
  • Next topic Adding related parties from third-party data providers

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