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. 

Creating a new PEGA Application guidance

Creating an Application in PEGA

To create a new Application in PEGA, Go to DCO or Application Express menu > select New Application wizard.

In this wizard you need to provide few details like

Application Properties & Organisation Properties

 You need to provide name of the application and the description and the organisation.

Business Objectives:

Cases Types

Data Objects

Once clicks on create PEGA will build application skeleton along with server (tomcat by defaul) and db(postgresql by default).

By default, it will create 3 operators.

• Admin (Developer Portal)
• Manager
• User

PEGA Installation and Panels Explanation

PEGA Installation:

PEGA Installation is very straight forward. JDK (PEGA was built using Java), Server and DB will comes with the PEGA zip file. You can download get the download of PEGA Personal Edition Software from here . You will get mail with the link to download from PEGA after subscription. Simply follow the wizard and finish the installation. You need to make sure that the existing java in your machine compatibility with the pega version.

There are two editions of PEGA software.

• Personal Edition
• Enterprise Edition

There are very little differences between these two editions. You can configure any server and db in Enterprise Edition but not in Personal Edition.

After installation you need to start and login to the application from the icons will appear on the desktop post installation.

Default Login details:

• Username: Adminstrator@pega.com
• Password:  install

PEGA Tool Explanation:

You can the above image, total screens are divided into 4 panels

• Header Panel
• Explorer Panel
• Work Panel  
• Footer/Toolbar Panel

Header Panel

• Designer Studio: Application settings, deployment tools, data table creation, User Interface gallery, reporting settings, integraraion, services, resources, org settings, security settings, connection wizards, email wizards.
• DCO (Direct Capture of Objectives) – Application Express
• Launch: There are 3 operators/portals by default will provide by PEGA. 
• Admin/Developer
• Manager 
• User
• Create: create will be used to running the application
• Search: To search anything in PEGA
• ChekIn/Checkout: version control in PEGA
• Recent: to see recent opened activities
• Operator: you can see the data related to Operator. 
• Access Group: is tells us that which portal access does the operator has and which roles he has and so on…

Explorer Panel

·         Recent: recent activities

·         Cases: Shows the modules in the application.

·         Data: all the data tables will be display here

·         App Explorer: All the rules creation will be happen from here.

·         Records: It shows the Hierarchy of the apps

·         Private: same like checkIn/checkout

·         Favourite: bookmarked items will be shown here.

Toolbar Panel

·         Tracer:

·         Clipboard:

·         UI Inspector:

·         UI Tree:

·         Performance

·         Alerts

·         Inspector Pref

PEGA Topics For Your Reference

Below are the PEGA concepts that you need to focus to become a good PEGA Developer.

•          Explorer’s in PEGA
•        Introduction to Data Model              

·         Creating Data Tables

·         Types of Properties

·         Creating Properties

·         Change the Appearance of a property

·         Create Embedded Properties ( PEGA 1.6 version)

•          Introduction to User Interface and Form Design
•          Introduction to Process Definition
•          Working on Stages & Processes
•          User Interface

·         Create a section

·         Create a section containing Multiple Layouts

·         Adding a section to a Flow Action

·         Calling another Section in a Section

·         Selecting the layout

·         Creating Flow Action

·         Creating Harness

•          Process Definition

·         Different Shapes used in Flow & their purpose

·         Create main Flow/Process Flow

·         Create a Sub Flow/Screen Flow

·         How to run the flow or creating work object

·         Create Tabbed/Tree navigation Screen Flow

·         Call a Sub Flow from another flow or from Same Flow

·         Design and implement Screen Flow

·         How to select Screen Flow types

•          Advance UI

·         Add Image/Icon/Links

·         Apply Dynamic Fetch

·         Calling Data Page

·         Repeating Layout and Tabbed Layout

·         Conditionally display a section

•          Activities and Methods

·         Explain the purpose of different tabs in Activity

·         Understand purpose of Pages & Classes

·         Different Methods used in Activities

·         How to Call Activity from another activity

·         Different ways to call Activities

•          Validations

·         Types of validations

·         Rule-Edit-Validation

·         Rule-Obj-Validation

·         Constraints

·         Difference between Rule-Edit-Validation and Rule-Object-Validation

·         Difference between ROV & Constraints

•          Decision Rules

·         Decision Table

·         Decision Tree

·         MapValue

·         When

·         Calling Decision Rules in Flow & Activity

·         Calling Decision Rules in Expressions

•          Declarative Rules

·         Declare Expressions

·         Declare Constraints

·         Declare On Change

·         Declare Pages/Data Pages

•          Advanced Activities

·         Create and Activity with a precondition and a Transition

·         Create and Activity to populate a dynamic Select

·         Creating activity for calling Integration

•          Assigning to Work

·         Introduction on Routing

·         To Work List

·         To Work Basket

•          SLA (Service Level Agreements)

·         Define an SLA

·         Assigning SLA to Assignment

•          How to Send a Correspondence (E-mail)
•         Configuring E-mail
•          Work Parties

·         Creating Work-Party

·         Adding Work-Party to Flow

•          Agents
•          Reports
•          Migration/Deployment (Import & Export)
•          Developer Toolbars

·         Clipboard

·         Tracer

·         UI Inspector

·         UI Tree

·         Where Am I

•          Documenting the Application
•          Connecting to External Database Using Connect-SQL
•          Configuring Web Services (SOAP)
•          Integration Connector & Services (SOAP)
•          New Features in PEGA 7
•          Difference between versions
•          PRPC Guardrails
•          Deployment

·         Other frameworks integration with PEGA. Like Case tool…

PEGA PRPC 1.7.6

PEGA 7.1.6

PEGA – Name of the product/application (product of PEGA systems)

PRPC: PEGA Rules Process Commander:

                A platform design/developing and deploying application. Also calls as Build for Change Platform

BPM:

                Business Process Management (Methodology) to manage flows and processing of app. (comes with PEGA software only). It controls how the connections are happening with in the application

We can build any type of application, without coding only by drag & drop and point and click

PEGA PRPC has two Entities:

PEGA rules (Object Oriented Rules)

Process Commander (Storage Area, to store all pre configurations)

PEGA BPM has SIX R’s:

PEGA Architecture:  PEGA has very simple Architecture to understand. Below image will explain the Architecture of PEGA.

Every release of PEGA contains new features or enhancements. Here are some features introduced in PEGA 7 which made our life easy :)