Frameworks and Layers (Classes) [For Reusability]

 

FRAMEWORK

µ  The terms Framework & Implementation will come in 2 places i.e. 1) Application level 2) Class level.

In general – Framework contains most reusable functionalities (Flow, UI …) & Implementation contains most specific functionalities (LR Flow, Home Loan details screen …)

Ø  Framework application:

·         Framework applications are generalized reusable tailor made applications that contains common functionalities to be re-used across Implementation applications

Ex: Call Center applications, Dispute applications, Loan Lending applications …

Loan Application (Loan related common features for every Country, there is one Frame Work layer)

·         Used to leverage (capabilities) its functionalities by Implementation applications across

·         Frame work makes our life easy. We will write the Generic code here which can be reused (by save as) at our need at any time.

·         The kinds of rules most often encountered here are: Case types / Flows / Flow actions / Sections / Programs …

·         Used (called) as Built on application for multiple implementation applications.

·         Framework (Reusable work-related business rules)            – Process standards

à The classes belong to this are called Framework classes

·         Framework types:

1.      Standard or Solution Frameworks (mainly for Banking, Insurance, Health Care...):

Pre-defined industry specific applications which are readymade

ð  CPM framework: Stands for Customer Process Manager which is pre-defined framework application to support customer care processing on IVR (interactive voice response)

Ex: CPM for Insurance, Health Care, Telecom …

ð  Smart Dispute framework: Banking related disputes

ð  Smart Investigate framework : for any Banking related project

2.      Custom Frameworks: User-defined specific applications

ð  LendFW framework : for any Banking related Lending applications

ð  HRMSFW framework : for any Human Resource related applications

Ø  Implementation application:

·         Implementation applications are specialized applications that contains just specific business functionalities which has zero reuse

Ex: Call Center for HSBC, Dispute application for HSBC, Loan Lending application (iLend) for India …

·         We leverage the functionalities of its Built-on FW application here

·         Usually the landed application after sign-in are said to be Implementation application

CPM framework

[Customer Process Manager Solution framework]

Business applications that support front-office interactions with customers, whether face-to-face across a desk, by phone, by email, Web chat, or other means, are known as customer process management applications.

To support customer service representatives, such applications typically are interconnected with phone switches and interactive voice response (IVR) equipment.

Pegasystems' Customer Process Manager solution framework (CPM) and related products support customer process management in banks, insurance, healthcare, and other markets, using PegaCALL software to interface with telephone equipment. CPM provides a comprehensive process-oriented (rather than data oriented) approach to customer service and customer relationship management (CPM), supporting inbound telephone calls and other channels.

Workers using a CPM system are often called Customer Service Representatives, or CSRs.

LAYERS (CLASSES)

Ø  Enterprise Class Structure (ECS) is the backbone of reuse in our application and is generated by App Express wizard

Ø  ECS has 4 Layers In general: [to develop robust PRPC application]

·         Enterprise level layer (Organizational Reuse Layer)                    – Corporate standards

à Mostly Customer related rules are defined here

à The classes belong to this layer are called Enterprise (Org) classes

à Higher level common features are kept here like Customer details such as Name, Address, PAN etc. for Bank Loan project for 150 countries (Bank level common features)

à The kinds of rules most often encountered here are:

w  Security (for example, LDAP access, how users are granted rights, etc…)

w  Corporate Logos and Skins

w  Corporate wide data models (for example, Customer, Insured, etc…)

w  Some Integration Points (Note that these should only be placed here if they are used organization wide. Access to a customer database is a good example of a potential organization wide integration. However a list of automotive repair centers would not be a good idea as it is most likely only applicable to a single line of business and would not be used organization wide.)

·         Division level layer (Division Reuse Layer)                                     – Line of business standards

à Mostly Integration related rules are defined here

à The classes belong to this layer are called Division classes

à Division layer will have implementation application for the Framework

à The kinds of rules most often encountered here are:

w  Division wide data models (like the vehicle example)

w  Division wide letterheads, signature lines, office locations, telephone numbers, etc…

·         Framework (Reusable work-related business rules)          – Process standards

à The classes belong to this are called Framework classes

F The rules most often defined here are: Case types / Flows / Flow actions / Sections

à Framework applications are generalized reusable tailor made applications that contains common functionalities re-used across Implementation applications

·         Implementation level layer (Non-Reusable layer) Or Application Layer            – Specific

à The classes belong to this layer are called Implementation classes

à It is an Implementation of a Framework in a particular division

à Ex: Home Loan Application, Vehicle Loan Application....

F Example:

If an insurance company wanted to standardize its Policy Administration across multiple business lines, they could create a generic Policy Administration application in the Framework layer. This generic application could be used as the basis for Policy Administration applications that the customer’s commercial property, personal property and personal automobile business lines

à The kinds of rules most often encountered here are:

w  Class groups / SLAs / Routers

        

Ø  Most enterprise applications are built in 2 layers (classes):

·         Framework (Reusable layer) class

·         Implementation (Non-Reusable layer) class

Ø  Framework vs. Implementation classes:

·         Implementation class (also called Implementation layer): Is a class that belongs to a RuleSet that is one of your application Rulesets

F Typically, work items belong only to implementation classes (work types), never to framework classes

·         Framework class (re-used FW layer): Is a class that belongs to a RuleSet that is not one of your Application Rule Sets

Ø  Frame work is installed (deployed) on PRPC. So Framework class (like base class) is inherited directly from '@baseclass' and then our class structure (like sub class to this Framework) is inherited from this Framework.

·         Main advantage is reusability

·         It should be on the top of Pega

·         Most of the times Harnesses are defined at Framework level

·         Because of the Framework is already defined, It has some naming convention which we have to use

Ø  Design class structure: 2^nd Guardrail: Establish a Robust Foundation

Class structure is an integral part of every Pega application. Designing a scalable, extensible (extended) enterprise class structures from the beginning of your project will help avoid costly re-factoring. The reusability requirements drive the selection of your class hierarchy design.

·         Designing the class structure in such a way that Maximizing reuse of OOTB classes, OOTB properties and other OOTB rules drive your development faster and minimal effort

Ø  Purpose of 4 Layers of ECS:

Ø  Below is the ECS (Enterprise Class Structure) generated by App Express wizard: