PEGA - Operators, Class Groups, Classes, Inheritence, Rules, Stages Explanation

      After creating the application in the backend PEGA will provide all the necessary configurations and provides by default 3 Operators.

• Admin: It is used as a Developer portal
• Manager: Business Analyst will use to assign/route the requirement to the Developer.
• User: End user.

As a developer our role will be Admin.

In PEGA we have 3 different Classes

• Work Classes
• Data Classes
• Integration Classes

If you compare these classes with Java classes then you can relate very easily.. Lets see how

Work classes are like POJO classes which holds the data on UI.

Data classes are like DTO classes which holds the columns of Database.

both Work and Data classes are Concrete classes and Integration classes are Abstract classes which don't have any implementations.

Note: Abstract classes are ends with '-'

All these classes are classified into 3 class groups in PEGA.

• Is a Classgroup
• Belongs to Classgroup
• Doesn't belongs to Classgroup

Work Pool type is “is a class group”
All classes are under Work Pool are “belongs to class group”
Data classes are “doesn’t belong to class group”

Note: You can create sub classes only in a class, which is “is a class group”

Inheritance:

In PEGA every class is derived from @baseclass. You can see the hierarchy by right click on class and click on inheritance. There are two types of inheritance in PEGA.

• Pattern Inheritance – System generated inheritance
• Direct Inheritance – user generated Inheritance

Rule: Rule is nothing but a building block. Here a block means some functionality, UI whatever. Which will define the behaviour of that part.

Note: Rule type is a concrete class derived from a base class called Rule-

Ruleset: Rule set is a container of rules. 

All these rules will be created under Application > Class name > Ruleset(nothing but application name) > and based on the rule category. You can see after deploying the application. 

Below are the list of Rule Categories:

Note: These rules will be stored in Ruleset under Class instances.

Case: Case is a Module in terms of application. A unit of work to be done.

PEGA will automatically create concrete classes using the Cases, which you are defined at the time of creating a project in PEGA.

Process: Process is represented as a Flow in PRPC.

Class: class is a container of all the rules in PEGA.