Delete reference data record (Soft-Delete) without physically removing record from the table in PFFS

Delete reference data record (Soft-Delete) without physically removing record from the table in PFFS

Description	Deleting a record without physically removing it from the table
Version as of	8.6
Application	Pega Foundation for Financial Services
Capability/Industry Area	Financial Services

Soft-Delete functionality in Pega Foundation for Financial Services (PFFS)

Soft-Delete represents functionality to omit data from being displayed or processed without physically deleting records from tables. Table record can be marked as Active or Inactive, allowing functionality to determine which records to retrieve. Since data is not physically deleted, customer has extra safety net that Soft-Delete can always be reversed by simply changing the status of the record from Inactive to Active.

Tables

Pega Foundation for Financial Services (PFFS) implemented Soft-Delete functionality on several reference data tables:

FSF_REF_COUNTRY (Country codes, names and risk)

FSF_REF_SECTOR  (Industry sector codes and descriptions)

FSF_REF_EXCHANGE (International exchange codes and names)

FSF_REF_REGULATOR (International regulator codes and names)

FSF_REF_INDUSTRY (Industry codes and descriptions)

FSF_REF_SUBINDUSTRY (Subindustry codes and descriptions)

FSF_REF_INDUSTRYGROUP (Industry group codes and descriptions)

FSF_RELCODE (Related party codes and descriptions)

Each table, listed above, has been extended with status column representing if record is Active or Inactive. Default status value is ‘Active’ or NULL represents active record.

Possible values for status column are Active, Inactive, and NULL. Values are not case sensitive.

View of FSF_REF_EXCHANGE table with status column values set to ‘Active’ for each record.

Class Structure

Represents corresponding data and integration classes for each reference data table listed above. Additional information on data integration can be found in PFFS Implementation Guide on Pega Foundation for Financial Services Community site.

Data Class	Integration Class
PegaFS-Data-Country	PegaFS-Int-FSF_REF_COUNTRY
PegaFS-Data-Sector	PegaFS-Int-FSF_REF_SECTOR
PegaFS-Data-Exchange	PegaFS-Int-FSF_REF_EXCHANGE
PegaFS-Data-Regulator	PegaFS-Int-FSF_REF_REGULATOR
PegaFS-Data-Industry	PegaFS-Int-FSF_REF_INDUSTRY
PegaFS-Data-SubIndustry	PegaFS-Int-FSF_REF_SUBINDUSTRY
PegaFS-Data-IndustryGroup	PegaFS-Int-FSF_REF_INDUSTRYGROUP
PegaFS-Data-RelCode	PegaFS-Int-FSF_REF_RELCODE

Soft-Delete logic

Data pages returning a list in each corresponding data class have been altered to return only active records or all records based on the new parameter value.

Note: New parameter is a system (Pega platform) value -1 or NULL passed via section.

This logic is illustrated by example in data class for Exchanges: PegaFS-Data-Exchange. Data page D_ExchangeSummary

Data page conditions to handle NegativeOneReadOnly parameter:

If CheckNegativeOneReadOnly is true (-1 value is passed), then only active records are returned by GetExchange report definition and otherwise GetExchange report definition returns all records.

If NegativeOneReadOnly parameter is -1 then ‘InActive’ is passed for Status parameter to be used in the report definition condition to return only active records. Report will return all records that are NOT Inactive. This condition will return records marked as Active or NULL.

The default passes string ‘NotNegativeOne’ in the Status parameter to return all records. Since the possible values in status column are Active, Inactive, and NULL then report condition status is NOT ‘NotNegativeOne’ will return all records.

Report definition GetExchange contains conditions for passed parameters, Note the condition for status column:

Implementation in Financial Services (FS) applications

Soft-Delete functionality implementation in Client Lifecycle Management (CLM)/Know Your Customer (KYC) Financial Services (FS) application consists of having duplicate sections: one for displaying read only, active records and another for editing data, displaying all Active and Inactive records. System parameter (-1) is passed to the data pages to trigger report definition for active records, otherwise all records are retrieved.

End result and use case

In Dev Studio, Configure -> Financial Services -> Reference Data will open a landing page to manage country records. Each record can be set to Active or Inactive status. Inactive records will be excluded from any processing/selection logic.

An instance of a data type that is stored for your application. For example, customer records include data specific to each customer, such as the name, email, phone number, and so on. You can manually create data records or import a set of existing data records in Data Designer. Use the Data Type Explorer to view the list of supported data types in your application.

A business solution that automates workflows in your organization. Multiple, unrelated applications can be hosted in the same system. You create an application by running the New Application wizard.

A collective term that describes a rule instance or a data instance. For example, a customer record would include data specific to a given customer, such as name, telephone number, and customer account number.

(Deprecated) A configuration of panels (areas) in a harness that support a composite portal. Existing panel sets continue to function. As a best practice, upgrade panel sets to screen layouts.

A data storage that is superseded by the local data storage feature. Click Convert for each data table that is displayed on the Data Tables landing page to convert it to the new format.

The rules that define the behavior of your application. You can create classes to gather rules related to a specific object in your application. For example, in a recruitment application, you can create a class that contains rules that define the flow of the recruitment process. Classes can contain other classes, hence a class that contains another class is called a parent class, while a class that is contained by another class is called a child class. A child class can reuse, or inherit, any of the rules that are defined for its parent class, which helps to build your application faster and more efficiently.

The building blocks of your user interface, sections can use design templates for their structure and contain such interactive UI elements as fields, buttons, lists, and so on. A section creates a functional chunk of a user interface, and can be reused throughout your application for improved consistency and efficient development.

For example, your application may need to display user data as a list of ID cards. You can create a section for the contents of a card, and then reuse that section so that the design of every card is consistent.

A permanent, unique identifier for a class that includes certain key parts, and the creation date and time of a single instance for rules and some classes. A handle is sometimes known as an internal key. The pzInsKey property holds the handle value for an object. The pzInsKey property is undefined until you save the object.

Actual work that is performed by application users and automations that consists of a sequence of tasks and leads to an intended business goal. An example of a case is a process of hiring a particular job candidate, where an HR worker collects necessary documents, a hiring manager conducts a job interview, and an application sends an automated email with onboarding information after the candidate is approved. To create a case, you first build a template of your business process that is a case type, and then apply the template in multiple cases, for example, to review applications from many candidates.

A single source of information that presents categorized content, such as tabs or tools. You can access information on a landing page with focus on a single category that you want to select. A number of landing pages can be accessed right at the launch of your application. For example, on the Application Quality landing page, you can view the health of your current application and identify improvements to make before you deploy an application.