PEGA Tutorials >>

BPM: Which provides the ability to have end-to-end (requirements-to-reporting) visibility and control over all parts of multi stepped transaction (work flow) steps (tasks) that spans multiple applications and people in one or more organizations.

Traditional Application development : -         (UI, Logic, Data)

BPM Application Development : -      (UI, Logic, Data, Process or Work flow)

Process: Unit of work, can be completed either acceptance or rejection.

Java – Eclipse

.Net – Visual Studio

BPM – BPM Suite, is an environment, have to follow some business rules

Business Rule: Aimed to influence the behavior of the system, resides in business rule data base.

BRE: Business Rules Engine (BRE) is a program, which drives the business rules from business rule db to Application.

BPM Suite Methodologies:

1.      Workflow Architecture

2.      Business Rules

3.      Business Rules Database

4.      Business Rules Engine

BPM                                                    PEGA

Workflow (Process)                                         Process

Business Rules                                                 PEGA Rules

BRD (Business Rules Database)                     Rule base

BRE (Business Rules Engine)                         Process Commander

PRPC Architecture:

Java Compiler

XML Data structure -> converted to BLOB for secure transactions

Web services (SOAP, REST, and MQ)

Rule base – Oracle, Postgre SQL, My SQL <Any DB> - Internal DB, External DB - <Any DB>

PEGA:

PEGA System   ->         Allen Treffler (Chess Champion)

PEGASUS - Horse with Wings (In chess Knight Symbol)

Sectors PRPC

·         Insurance

·         Banking & Finance

·         Healthcare

·         Oil & Gas

·         Automobiles – Ford, Benze, John Deer

·         Entertainment – Disney

·         Telecom – Nokia, Vodafone

·         Travel

Reasons to Choose:

·         Back Operations mainly

·         For Business processing

Advantages of using Pega Application

·         Development

o   Java: UI, Logic, SQL – UI Resource, Java Resource, SQL Resource

o   PEGA: Automated – Form based programming model (HTML5)

·         Processing (Speed up your business)

o   Java Logic: Compiled -> Running -> Cache

o   PEGA: Predefined & Precompiled rules – Cache Tables

§  Maintaining perfect rules cache

§  We just need to pass parameters

·         Error Free: as we are using precompiled, predefined rules

·         Licensed – not there in end user world

·         Maintenance is easy (6.3 - > 7.x ) – 7.0.0 -> fixing the bugs and making as next version

·         Application Creation (UI, Logic, DB)

·         Integration

o   SOAP Service

o   Connect SOAP

o   File Listeners

o   External Database

o   Agents & Batch Processing

o   Email Integration

o   REST

·         Exception Handling

·         Development

·         Trouble Shooting

·         Change Requests

·         Debugging

Class is a unit under which our business elements will be grouped together i.e. attributes and business logic

Predefined Classes or OOTB (Out Of The Box) Classes

·         In PRPC’s class hierarchy it has 13 topmost predefined classes available

·         Out of which the following 3 are most important

o   @baseclass: This is top most class in Pega. i.e. Parent class of all other classes

o   Work- : This class contains reusable components, using these components we can create Work. If we want to run our business we must have to reuse components from     this class  Work- class or any of its child classes

o   Data- : To work with database, we need to reuse the components from this class

·         All the predefined classes are reusable classes. In other words all these are abstract classes

Types of Classes in PEGA

There 2 different classes available.

1.      Abstract

2.      Concrete

Abstract Class:

·         Abstract classes are meant for reusability

·         We can only create the components under these classes, but we cannot run the business

·         PEGA 6 version, when we create an abstract class, its class name must end with ”–“ symbol. From Pega 7 onwards this has been removed.

·         Abstract class cannot be instantiated i.e. we cannot create work objects under abstract classes

Concrete Class: Concrete classes can be instantiated i.e. we can run the business under concrete classes. Concrete class name must not end with “-“ symbol

If class B is inherited from class A, class B can use the components of class A

·         Here Class B is said to be child class and class A is said to be parent class

·         In Pega we can achieve the reusability by means of inheritance

·         There are 2 types of Inheritance available in Pega

1.      Direct Inheritance

2.      Pattern Inheritance

·         Direct Inheritance:

o   In direct inheritance a class can only one direct parent

o   Direct parent of class can be selected under the dropdown “Parent Class Directed” in the class rule form

o   Direct inheritance is mandatory

·         Pattern Inheritance:

o   Pattern inheritance on a class can be applied by selecting the option “Find by name first pattern” in the class rule form.

o   It is optional

o   If the class A-B-C is applied with pattern inheritance, B is pattern parent of class C.

Online Pega training in India, Canada, US, UK and Australia. Mail to ramanpegatrainer@gmail.com