Connecting FS products to a System of Record

From PegaWiki
Connecting FS Products to a System of Record / This is the approved revision of this page, as well as being the most recent.
Jump to navigation Jump to search

Connecting FS products to a System of Record

Description How to connect Financial Services Products to a System of Record
Version as of 8.5
Application Pega Foundation for Financial Services
Capability/Industry Area Financial Services



Connecting FS Products to a System of Record[edit]

Financial Services (FS) products can be created using Product designer for Financial Services (PDFS), or manually. Users of FS products run the following FS applications:

  • Pega Marketing for Financial Services (PMFS) - Ingests FS products from PDFS application and creates marketing offers that can be executed.
  • Sales Automation for Financial Services (SAFS) - FS Products are used in the creation of Opportunities.
  • Client Lifecycle Management for Financial Services (CLM) - FS Products are used in product selection of onboarding process.
  • Pega Know Your Customer (KYC) - FS Products are used to perform extra risk due diligence where appropriate.

Before Connecting to Another System of Record[edit]

Pega Foundation for Financial Services (PFFS) requires Operating and Product structures to be set up before creating/adding products. This is essential in the product selection process for FS applications.

Configuring the operating structure[edit]

  1. In Dev Studio, click Configure > Financial Service > Operating Structure
  2. Set up the operating structure as shown in the sample below:

FS Org Chart.png

Configuring the product structure[edit]

  1. In Dev Studio, click Configure > Financial Service > Product Structure
  2. Set up the product structure as shown in the sample below:

FS Product Structure.png

  • Operating Structure and Product Structure items created or edited in the UX are saved in the Pega system PR_DATA_ADMIN table.
  • UPFS is the financial institution abbreviation representing the Operating (Organization) Structure.
  • UPFSPD is the abbreviation that represents the Product Structure.
  • The path listed in the PYORGUNIT column will be matched with data in PFFS tables to determine products availability in product selection.

Note: The format of the PYORGUNIT data shown below needs to match the data path in the system of record for the product selection process to work:

Data Admin Table.png

PFFS Data Storage and Structure for Products[edit]

Pega Foundation for Financial Services (PFFS) hosts and manages products in terms of data structure and storage.

Storage:

Product data and availability is stored in the following PFFS tables:

  • FSF_PRODUCTMATRIX
  • FSF_PMINCLUSIONXREF
  • FSF_PMEXCLUSIONXREF

The FSF_PRODUCTMATRIX table contains basic information records on products, services and product bundles. Each product record belongs to a product category and a line of business. Columns in the table are defined as name/value pairs. (for example, PM_VAR[No]_NAME/PM_VAR[No]_VALUE). The columns that need to be populated are PM_PRODUCTNAME, PM_PRODUCTID, PM_VAR1_NAME/PM_VAR1_VALUE for Line of Business, and PM_VAR2_NAME/PM_VAR2_VALUE for Product Category.

Sample products in the FSF_PRODUCTMATRIX table[edit]

Product Matrix FS.png

FSF_PMINCLUSIONXREF is a cross reference table that contains line of business indicating that all product records for the given line of business are allowed.

Sample product lines of business, operating structure paths in pi_inclusionpath, and product structure paths in the pi_marketsegmentpath columns:

PM Incluclusion Table.png

The FSF_PMEXCLUSIONXREF table contains records that block specific product ids or all products belonging to a product category from being allowed.

Sample operating structure paths in the pe_exclusionpath column.

PM Exclusion Table.png

Logic to determine availability retrieves a list of product records from PRODUCT MATRIX for specified lined of business (INCLUSION), and omits from that list products or all products of a specified product category (EXCLUSION).

INCLUSION – EXCLUSION = List of available products from PRODUCT MATRIX.

FSF_PRODUCTMATRIX is populated either by using the PDFS application or manually by using SQL. Data in FSF_PMINCLUSIONXREF and FSF_PMEXCLUSIONXREF can only be populated using SQL.

Class Structure and Rules[edit]

Integration Class: PegaFS-Data-ProductMatrixInclusionXref

Report Definition:

  • GetLOBByLocation takes Organizational structure path of operator and matches with inclusion path.

Integration Class: PegaFS-Data-ProductMatrixExclusionXref

Report Definitions:

  • GetExclusionsByProductId takes Organizational structure path of operator and searches for type: product to return list of product ids.
  • GetExclusionsByPMVar2Value takes Organizational structure path of operator and searches type: product category to return list of product categories.

Integration Class: PegaFS-Int-FSF_PRODUCTMATRIX

Report Definitions:

  • FilterProductsByID
  • GetAllowedProductsByLOB
  • GetAllowedProductsByLocation
  • GetDepositProductsByType
  • GetExclusionsByProductId
  • GetExclusionByVar2Value where Var2 is product category.
  • GetProductFromProductMatrix
  • LOBList
  • ProductCategoryList
  • ProductMatrixSummary
  • ProductMatrixSummary_Short returns fewer columns than version above.

Data Class: PegaFS-Data-ProductMatrix

Data Pages:

  • D_AllowedProductByLocation retrieves available products. Invokes the activity GetAllowedProductsByLocation.
  • D_AvailableLOB retrieves available lines of businesses from inclusion.
  • D_AvailableProductCategory retrieves list of product categories not listed in exclusion.
  • D_GetAllowedProductsByLocation retrieves list of products by location.
  • D_GetProductFromProductMatrix
  • D_LOBList retrieves lines of business.
  • D_ProductApplicationsByType
  • D_ProductCategoryList
  • D_ProductMatrixSummary returns a list of all products and bundles with details.
  • D_ProductOpenById lookup that returns a single complete record from Product Matrix.

Activity:

GetAllowedProductsByLocation applies formulas based on input parameters:

  •  INCLUSION – EXCLUSION = AVAILABLE LIST OF PRODUCTS.
  •  INCLUSION = AVAILABLE LIST OF PRODUCTS (when products are not excluded).

Connecting to Another Data Source[edit]

When choosing to connect to another data source for FS products, the implementer must consider the following changes to the classes and rules listed above.

Data Sources[edit]

  • Another table(s)
    • New table(s) will be imported into Pega via a wizard with integration classes and properties representing columns created automatically as a result.
    • Every report definition listed above will be replaced with new report definitions hosted by newly created integration classes.
    • Data classes can be re-used with overrides to data pages and mapping data transforms in the implementation layer.
    • Every data page listed above will be overridden in the implementation layer to point to new report definitions.
    • Data transforms responsible for mapping are carry specific naming convention: OPENMAP for mapping retrieved data and SAVEMAP for mapping data back from class to data source. They can be overridden at the implementation layer with mappings for additional properties.
    • GetAllowedProductsByLocation activity will be overridden in the implementation layer to use new report definitions for product selection logic.       
  • Re-using existing tables
    • ETL job(s) can be setup to synchronize data between FS product tables and  other system of record (data sources) platform.
    • Existing integration and data classes can be extended with additional properties to be mapped and columns  to be retrieved.
    • Report definitions can be overridden at implementation layer to return new integration class properties (table columns).
    • Data transforms responsible for mapping are carry specific naming convention: OPENMAP for mapping retrieved data and SAVEMAP for mapping data back from class to data source. They can be overridden at the implementation layer with mappings for additional properties.
  • Service calls
    • Integration class with connector rules will be created for authentication and using exposed service methods.
    • Data classes can be re-used with overrides to data pages and mapping data transforms in the implementation layer.
    • Every data page listed above will be overridden in the implementation layer to point to connector rules.
    • Data transforms responsible for mapping are carry specific naming convention: OPENMAP for mapping retrieved data and SAVEMAP for mapping data back from class to data source. They can be overridden at the implementation layer with mappings for additional properties.

References[edit]

Data and Integration: Data Pages

Integrating Data

Integration Service Connectors