Scribd
Upload
11 views7 pages

Inheritance in Pega

The document outlines the structure of inheritance in Pega applications, focusing on three main classes: Organization, Application/Division, and Unit/Work classes. It explains how these classes are defined, including their abstract or concrete nature, and the use of the '-' symbol to indicate inheritance relationships. Additionally, it describes two types of inheritance: Pattern inheritance for accessing higher class features and Direct inheritance for accessing Pega Platform features.

Uploaded by

teja
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
11 views7 pages

Inheritance in Pega

The document outlines the structure of inheritance in Pega applications, focusing on three main classes: Organization, Application/Division, and Unit/Work classes. It explains how these classes are defined, including their abstract or concrete nature, and the use of the '-' symbol to indicate inheritance relationships. Additionally, it describes two types of inheritance: Pattern inheritance for accessing higher class features and Direct inheritance for accessing Pega Platform features.

Uploaded by

teja
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 7

Inheritance in Pega

When we create new application, Pega has created below

1. Application
2. Operator ID
3. Organization
4. So many classes.

Out of so many classes we focus on 3 main class classes

1. Organization class
2. Application / Division Class
3. Unit / Work class.

Let’s login to IMPL App


Go to dev studio

The THREE classes loaded are

BAJA-BajajAuto-Work

BAJA : Organization Class

BajajAuto : Application class / Division class

Work : Transaction class / Unit Class / Class Group


Let’s have a look at the class definition to know it’s type.

To know the class details , Right click on class  Definition

Org Class

This is created as Abstract class.

Done.

Division / Application class


Division / application class is also created as “Abstract” class.

Done.

Work /Unit class


Unit/ Work class is been created as Concrete class and also this is marked as “Class Group”.

This is the class where transaction can be initiated, processed and closed.

Done.

The three classes are created as below

1. BAJA
2. BAJA-BAJAJAuto
3. BJAJ-BAJAJAuto-Work
We need an inheritance relation defined between Organization, division and Unit.

This is been done by pega using “-“. The Symbol “-“ defines inheritance relation between the
classes.

This is included in the class name.

Example : A-B , here class B inheriting from Class A.

There are two types of Inheritance in Pega

1. Pattern : This is defined by “-“ in the class name. The purpose of pattern inheritance is to
access the feature of “Higher” classes into “Lower” class with-in application.
2. Direct Inheritance : Inheritance relation defined between two classes of Current and Build
on application. The purpose is to access the features of “Pega Platform” application.

Direct inheritance can be defined in the “class definition” at “Parent Class Directed”.

Right click on Class Group  Definition  Scroll down

The direct parent of Our application Classgroup / Work class is . Pega platform application’s
‘Work-Cover-‘ .

DONE.

You might also like