0% found this document useful (0 votes)
57 views5 pages

Airpega 2 Document

PEGA is a business process management tool that allows designing, developing and testing applications without coding. It uses a drag-and-drop interface and contains pre-built functionality for case management, process management and more. Key concepts include rules, rulesets, classes, ports and flows for designing application logic and processes.
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as TXT, PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
57 views5 pages

Airpega 2 Document

PEGA is a business process management tool that allows designing, developing and testing applications without coding. It uses a drag-and-drop interface and contains pre-built functionality for case management, process management and more. Key concepts include rules, rulesets, classes, ports and flows for designing application logic and processes.
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as TXT, PDF, TXT or read online on Scribd
You are on page 1/ 5

What is Pega?

PEGA is a business process management Application (BPM) tool to design, develop and
test web and business applications.
We can create java and web applications with in-built java code inside pega tool
What is Designer Studio?
Designer Studio is a PEGA Portal for designing and developing applications by using
in-built pega tools like
-Case management
-Stage management
-Process management

What is BPM?
BPM is business process management methodology which is a structured approach to
automate and manage process asynchronously.

What is Agile Methodology ?


Agile unlike waterfall, implements incremental and iterative approach to develop a
business process flow.
Agile stands for adapting to changes it technology, incorporating new trends and
developing according to latest trends.
PEGA uses SCRUM methodology.

Advantages of PEGA
1. No Coadding – We don’t need any programing or coding skills to develop an
application. Everything is a Drag & drop feature with in-built java library.
Be clear about the rules and how to use the application to achieve a functionality
2. Drag & Drop – PEGA has in-built tools containing all elements which you can
drag and drop into the user interface to create it.
No need of any prior programming skills. All are pre-defined inside PEGA designer
studio.
3. Plenty of Jobs – PEGA is now incorporated in all top companies with excellent
packages above 6LPA.
There are huge on-site opportunities in PEGA in Australia, USA and Canada
4. Modern, Mobile ready Application- PEGA Development is comparatively easier
than other development languages due to its in-built feature.
All applications developed in PEGA are highly modern, mobile ready and HTML5/CSS3
Ready.

PEGA is in-built java engine, contains most of java’s pre-defined code library. You
can create a UI instantly without any programming skills.

PEGA frontend – Drag & drop & configuration


PEGA backend – java -exports .jar application

PEGA is not a software/It’s company name


PEGA PRPC is software – PEGA Rules process commander
- Everything in PEGA is called a Rule
- Process commander processes the rule to develop a functionality
- This rules are stored in a ruleset named after application
PRPC store rules and rulesets and applies them to a class, similar to java.

RULES & RULESETS


Rule is a basic building block of your application stored in rulesets

What is the difference between Rule and Ruleset?


Rule: Rule is ab basic building block of an application to help develop an
application Methods – Activities Rule Variables – Properties Rule UserInterface –
Section Rule
Ruleset: Ruleset is used to store, organize and manage an application for
deployment aned migration of the rules in them.

Just think as this a cube as Ruleset


And the individual blocks are Rule. Like we have RuleA, RuleB, RuleC,…..
This entire thing cube is Ruleset, it is the collection of Rules
For every application that we create one Ruleset will be created
Along with Ruleset we will also have Version 01-01-01, In PEGA rulesets mainly use
version

RuleA, RuleB, ….. placed in Ruleset…


Modifications in ruleset done in next version. EX: Ruleset 01-01-02

Ruleset has a version and name

Every ruleset starts from a basic version called 01-01-01


01 – Major Version
01 – Minor Version
01 – Patch Version

Security Updates, Patch Fixes, Upgrade Patch Version 01-01-01 to 01-01-02


Minor Changes to Ruleset, Upgrade Minor Version 01-01-01 to 01-02-01
Major Changes to Ruleset, Upgrade Major Version 01-01-01 to 02-01-01

Operators are users in PEGA


Each user is called an operator and has a role and ID assigned. Based on operator
role, the portal will be different.
Administrators – DESIGNER STUDIO (Will do dev & admin)
Developers – DESIGNER STUDIO
Manager – CASEMANAGER

Difference between Pega 5,6,7,8 Versions


Pega 5.X.X
Oldest version, not being used by many of the companies. Outdated, lot of newer
features are added.
Pega 6.X.X
Still being used by many companies. Resembles with latest version features, But not
modern and mobile compatible
Pega 7.X.X
Modern, Flexible, Mobile compatible application development achieved with robust
functionality.
Pega 8.X.X
Dive deeper into the innovative technology of Pega Platform 8.6 and build
resilient, low-code automation everywhere. The new Pega Platform lets you deliver
breakthrough outcomes end-to-end with the power of real-time AI.
-Low-code App Development
-Case Management
-Pega Infinity in the Cloud: Pega or Client managed
-Conversational Channels
-Data Integration
-Decision Management
-Security
-System Administration
-User Experience
-Reporting
-DevOps
https://community.pega.com/knowledgebase/products/whats-new/platform

Let’s Review Some Concepts


Rule
A Basic building block for developing an application. Everything is a rule

Ruleset
Ruleset stores rules and manage them during development and migration. Has a
version and name of format Rulesetname: 01-01-01

Classes
Every ruleset has an applied to class. It belongs to either parent or child class
as the same.

Designer Studio
One of the pega portal assigned to an operator to develop applications. Each
operator has a portal assigned to him

Operator
Evert user in PEGA is called an operator. Based on operator’s role, the portal he
uses is different.

Portals
This are work area or user interface for operators to perform particular actions.

DEV STUDIO
Contains - Header toolbar
- Explorer panel
- Developer toolbar
- Work Area

DevStudio -> Categories will display which contain desired functionality


For ex: create any rule on UI, it will be available UI category
Similarly if we want to work on decisioning, it will be available in Decisioning
Category
All this are nothing but the categories which contains hour desired functionality
Pega Platform is the Name of the Application, this name is determined by our access
group
OperatorID is going to called the access group
Access group is going to determine which application this perticulat Operator ID
needs to access

Search Box is to search any rule which are present in the application, suppose if
there is any rule we have just created, just search the rule we have created just
by using search box.
For ex: I have some records, I have go to the Operator ID
Search administrator, type administrator in search box , then it will give all the
search results which is having the word administrator
Information menu is access to the pega article , pega support committee and pega
information etc;
Operator ID we can just changing the emailID , also we can see where your access
groups
With in operator we can see access group
This access group will determine 1)Which Portal is this particular operator needs
to access, 2) which application he needs to access and 3) Which Role he has
Recent Explorer
This is just like recent history, what ever we opened recently will display on the
recent explorer
What ever the recent action that we have done or recent rules that we have opened
and viewed those rules will displayed in the Recent Explorer

Cases Explorer
It will display the different modules which are nothing but case types available in
PEGA in your application

Case Type:
Case types are like the module with in which you can start developing your
Application.
Instead of developing the application in one go we can break down the application
in to several types and each case type can be developed.
Case types are divided in to stages
Stages are again divided in to processes
Processes are again divided in to Steps
With in the Steps we can Configure UI

Every Process it is going to create a Flow in the back end, similarly for every
step that we add to process, it is going to create a flow action in the back end.
Add field to a step and Click on the step Name and click on the configure view,
this is going to add fields to the steps.

What is Flow and Flow Action?


A process add to the case it is going to create a flow rule.
App Explorer we can see Parent Class and Child Class
If we check here we can see flow under Process category
Just to initialize the values pyStartCase will default added

What is Flow?
Flow is nothing but it is just like designing your step. By running a flow we can
able to create a work and we can design the work
Flow will allow you to design the work process

When ever we clicking on Cases Explorer, what ever is being open is Cases Explorer.
So I can switch to Process Designer, Just click on the Icon (Configure process), It
is going open the process and it is display in the form of FLOW.(Click on Open
Process)

A flow is where you can design your processing in Flow Chart Format
A process rule will create a Flow Rule in the Back end.

FLOW ACTIONS
Flow actions are used to perform actions on flows. They can be configured on flows
and usually store the sections.
Actions such as validation, authentication, section
Navigate to Process > Flow action
Flow action rule is automatically created when a step is added to the process

There are 2 types of flow actions


1. Standard flow action – Advance the flow to next flow.
2. Local flow action – Does not advance the flow for ex. Popups, overlays etc.

Flow action should be called within connector properties from assignment shape.
FlowChart Symbols

DATA Types Explorer


Data types are used to temporarily stored or a local data storage, it will allow
you to store your data locally by using data types

APP EXPLORER
It will display your application in the form of classes, The Leaf symbol decides
the name of a class, All the leaf symbols are classes which contains instances. And
your rules will displayed in the form of classes.
If we want to see any rule present in the customer request class, expand Data
Model we can see Property, and if we expand Property we can see pySuggestions is
present under the Class, So the Rules are displayed in the form of Classes with in
the categories. All the rules are applied to the PegaSample. So the Top Class
PegaSample is Parent Class and the another classes are Child Class.

Records Explorer
It is like mini Database. It will display all the list of instances of a particular
Rule. Which will display complete instances of any rule which is available which is
created. What ever we create in Pega it will displayed in Records Explorer.
For Ex: If we click on OperatorID in Records Explorer, it will display all the
OperatorIDs in the all other Applications as well.

Favorites Explorer
It is similar to the BookMarking of your Application. Just we go for any Rule we
just go the website bookmark it like the same way we can book mark any website in
and it going to add to the Favorites.

Developer Tool Bar


Debugging and Exception Handling

Overview of DevStudio

You might also like