Using an Enrichment or Screening MarketPlace Component

From PegaWiki
This is the approved revision of this page, as well as being the most recent.
Jump to navigation Jump to search

Description Explores a unified approach to creating and extending integrations for Financial Services applications.
Version as of 8.x
Application Pega Foundation for Financial Services
Capability/Industry Area Financial Services

Usage of enrichment or screening Marketplace component[edit]

Pega Foundation for Financial Services (PFFS) provides a single, unified approach for creating and extending integrations to a list of financial information providers that all Financial Services (FS) applications can access.

Enriching customer and company data from financial information providers enables financial services organizations many benefits including: operational efficiencies, more efficiently managing credit decisions, verifying identity, increasing fraud awareness, providing more targeted and personalized cross-sell and upsell strategies, and optimizing collections treatments.

It is likely that you’ll want to use several providers to automate customer journeys depending on the location, type of client, sort of data required, and agreements in place. Also, you’ll want to take advantage of new services and information as providers make them available.

Supported Enrichment and Screening Data Providers (components):

  • Avox
  • IHS MarkIt
  • Dun & Bradstreet
  • Equifax
  • Refinitiv’s World Check One
  • eIdentification

Note: The data structure in PFFS is extendable to support additional data providers as they are added.

Before you begin[edit]

Downloading component from Pega Marketplace (formerly known as Pega Exchange):

In the Enabled components section of the application rule, click on Manage components button.

Manage components.png

If the desired component (Example:  Avox) is already present on your system, check the Enabled box. Otherwise click on BROWSE APPS & COMPONENTS button to proceed to PEGA EXCHANGE (PEGA MARKETPLACE).

Component screen.png

Search for desired component.


Implementation in PFFS[edit]

PegaFS-Data-ExtProvider- Is a centralized class for making component calls and mapping returned data back into the Financial Services data structure.

Specialized child classes  have been dedicated to handling enrichment and screening and output mapping.

Class: PegaFS-Data-ExtProvider-BusService-eEnrichment

Description:  Class for retrieving  search results and entity details for party enrichment.

Data Pages: Unified data pages for searching and entity details, selects applicable provider based on input, executes specialized data page for the provider to perform service call and handles output including errors.

D_Trigger_SearchEntity unified data page for searching with example call to Avox data provider.

Trigger Search Entity.png

D_Trigger_EntityDetails data page for entity details with example call to Avox provider.

Entity Details.png

Class: PegaFS-Data-ExtProvider-BusService-eScreening

Description: Class for retrieving  search results and entity details for party screening.

Data Page:  D_Trigger_eScreening is a unified data page for retrieving  entity screening details, selects applicable provider based on input, executes specialized data page for the provider to perform service call and handles output including errors.

Note: World Check One is the only screening provider currently enabled.

Class: PegaFS-Data-ExtProvider-BusService-Client

Description: Mapping returned data from enrichment and screening data page calls.

Data Transforms: Contains specialized data transforms dedicated to mapping response data from each data provider. Can be extended/overridden at consuming application layer to include additional properties.

Note: Additional child classes were created for distinct functionality for specific providers.

Use case examples[edit]

Enrichment reports for organizations: Search and details case in PFFS.

Search screen:

EEnrichment Search.png

Party details screen:

Entity .png


Pega Marketplace