PEGA is a platform which provided a systematic approach to build and deploy process-

oriented and rule based solution and applications. Business Process Management,
Customer relationship management, Decision management and case management
solutions are some of the examples where process and rules are integral part of application
development.
What PEGA provides to a developer is a Designer studio which acts as an Integrated
Development Environment (IDE) to build applications. The best part is this Designer studio
is web based so a developer can work and create solutions from anywhere in the world.

PEGA main focus are Processes. If you are planning to learn PEGA or if you are already
working with PEGA tools you should keep this in mind is"Process is King, Queen and
everything in PEGA". Every business solution is process oriented.

Technically PEGA is not a language or database or operating system. What PEGA provides
us is a framework which is process driven; everything that we do in traditional programming
such as designing user interfaces, writing business logic, applications logic, creating
physical and logical mode of databases etc. we do the same thing in PEGA. The difference
lies between PEGA and traditional programming is that in PEGA to build or develop
anything (UI, data access logics, validation rules etc) there are processes and gadgets that
we have to use.

In the heart of PEGA is PRPC server (PegaRULES Process Commander) which provides
the platform and interfaces to business analyst, system analyst and developers to design
and build applications in PEGA. The main focus in PEGA is on automation of works and
program code.

PRPC server is written in Java. To setup PRPC server to function smoothly we need an
Operating System, a Java application server, a database and Java JDK.

PEGA is a BPM tool. BPM stands for Business Process Management. The current version
of PRPC server is v6.2 sp2


What is it that an Organization does? The answer is every organization do some Work to
accomplish their objective or vision or mission. A work in any organization is done by the
people and applications. People create, receive, route, report and resolve work.
In PEGA, Work Type is fundamental unit of work that is process by the people or
applications. Each of the work has their own attribute or set of principle or steps to follow.
To understand it more clearly let us take an example of a Bank. Bank is an organization and
it does some work like providing loan, opening account, doing transaction etc. So, each of
this work is a WorkType from PEGA prospective.
Now for each of the WorkType there are systematic processes that need to be followed. In
case of Loan, a person who wishes to apply for loan has to submit a loan application with
the bank. This Loan application is called WorkItem in PEGA world. So, WorkItem is the
unique instance of work.












This article is next in series of our learning PEGA. In the last two articles we learn what is
PEGA and what are Work Type and Work Items in PEGA. In this post we will learn what are
Business Rules in PEGA? In the traditional programming such as Java, .NET or C++ we
use IF-ELSE-THEN or WHERE or WHILE to evaluate a property or data to make decisions.
In PEGA we achieve it through Business Rules.
Business Rules are set of policies and principles that are applied by an organization to
conduct business. There are set of rules setup by the company to conduct business. For
example: A Bank might setup a rule to give XX amount of loan to people who have an
annual income of $ 100,000 and credit score of > 700.
How to define Business Rule in PRPC?
Just like an Organization defines rules to conduct business PRPC provides functionalities to
define business rule.
Decision tree,
Decision table,
Map value
When
Decision Tree: Decision tree is similar to IF-ELSE-THEN evaluation criteria we have in
traditional programming. We can apply any number of criteria to evaluate the conditions.
The works from Left to Right and Top to bottom. When a particular condition is meet the
evaluation process is stopped. If none of the conditions are meeting a default or other value
is return back to the calling function.

Decision Table: Decision table are similar to our SQL Tables where we apply WHERE
clause to put conditions. We can write more than one condition. The table returns number of
rows that meet the specific criteria.

Map Value: As per PRPC rule book Map Value allows us to look at one or two properties
over any number of conditions to return any number of results. Map values only support two
properties which can be evaluated.
When: Business Rule can be defined using When functionality. When functionality can
evaluate any number of conditions. It works in similar fashion as IF-THEN-ELSE. It returns
either True of false after evaluation.