Skip to main content

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

Adding related parties from third-party data providers

Updated on February 16, 2021

Pega Client Lifecycle Management for Financial Services uses third-party components to enrich customer data. These components include MarkIt, Equifax (including eID Verifier), AVOX, Work-Check, and SWIFT KYC. Out of these components MarkIt and SWIFT KYC provide related party information to enrich the related party data category of an onboarding case. By default, the system maps back the data provided by components in the format that the onboarding case requires.

While the preconfigured logic for enriching the component provided related party data typically covers most regular cases, there might be some situations where the Relationship Manager might need to enrich with more data or enrich from a different component that is not part of the Pega Client Lifecycle Management for Financial Services product. The following rules can be configured to modify both default mapping behavior and add custom mappings.

Rule nameRule typeUsage
MapRelPartyFromThirdParty_ExtData transformUse the data transform to execute any additional logic while mapping related party data from a third-party component to the onboarding case.
  • Previous topic Optimizing the construction of related parties network
  • Next topic Customizing the relationship visualizer

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. is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us