Sandeep's Blog: Application creation in PRPC

PRPC Tool after installation

Default Credentials Login Id and password

Password: install

In this we can create New Application under the 'PegaRules'

Creates an application in PRPC Tool following this steps

STEP - 1 : Identify and create all the required properties.

STEP - 2 : Design UI by creating ' sections' drag and drop the above created properties on to the

layouts of sections .

STEP - 3 : Create a Flow Action, call the above created sections into this flow actions.

STEP - 4 : Create a flow, call the above created Flow Action into the flow by using an assignment

shape create a Work Object for the above created flow, save the flow and Run it.

PRPC BASICS

CLASS :

Class is a unit under which we define the objects

Types of Classes:

1. Abstract Class

2. Concrete Class

Abstract class:

In abstract class we can create the objects but we can cannot implement our business. i.e we can create the reusable business logic that can be shared by its sub classes (child class)

I.e, Abstract classes meant for re usability and can't be instantiated.

Concrete class:

In concrete class we can create the objects and we can run the business. If we want to run the business concrete class is must and concrete classes can be instantiated.

Understanding inheritance in pega

Inheritance :

Maintain the parent and child relationship between the classes.

EX: If we have two classes ABC and XYZ, If XYZ is inherited from ABC,

Then XYZ is a Child class and ABC is a Parent class.

Child class can utilize all the properties of parent class, but parent class can't utilize the properties of child class.

ABC ( Abstract Class)

| (Inheritance)

ABC - XYZ ( Abstract Class)

| Inheritance)

ABC - XYZ - Work (Concrete class)

Two types of inheritance in PEGA

1. Direct Inheritance 2. Pattern Inheritance

Pattern Inheritance :

This identies the parent class of current class by it's class name i.e For work class "ABC-XYZ-Work" Pattern parent is "ABC-XYZ" for the class "ABC-XYZ" Pattern parent is "ABC".

Direct Inheritance:

Direct Inheritance is the method by which a class is inherits characteristics directly from a specified parent class, regardless of any defined pattern inheritance.

When we create an application in PRPC automatically class group will be created by following this structure

PRPC makes the combination of like this

Org-Div-Unit in order frame your class group

1. Organization is the top level
2. Division is the middle level
3. Unit is the bottom level

Organization :

It is the top most entity for any business, which will have multiple divisions and units under it.

Division:

The purpose of division is to build common functionalities of specifics units which are associated with the respective division.

Unit:

It is the place where actually business processing is done.

For Example :

(Abstract class) PNC [organization] (can be created reusable comp)
(Cust Details)

(Abstract class) PNC-PNCloans [ Division] (Can be created the reusable comp)
(Loan Details) (Insurance Details)
Loan Insurance

Concrete class) PNC-PNCLoans-Work [Unit] (we can run the business i.e concrete class, it is also called implementation class)
Auto Loan Home Loan Personal insurance Auto insurance

In PRPC each concrete class will have a table connector. All the work instances will be store in the table which is connect to this work class(PNC-PNCLoans-work) work class is also called a class group.

Class Group:

Class group is the collection of abstract classes. All the business runs under the class group i.e work object gets created under work object.

When we create a new application it creates given component:

1. Application
2. Operator Id with Default Password 'rules'
3. Classgroup

What we need to create in PRPC application

* One or more Rule set

* One class Model , including a unique top level class

* One or more HTML-based forms, tailored for your work

* One or more Flows

* Multiple Activities

* Multiple Properties, Sections, Flow Action, Decision Tables, Decision Trees based on the business Rules.

What we need to configure :

Organizational Hierarchy

Authorized Users

One or more access group

One or more access roles

PRPC provides the different access group for different Operators.

OPERATOR:

The person who is going to login into PRPC application is called Operator.

Access group:

when login with PRPC, as an operator.Each operator will be associated with an access group.

Access group identifies what application the operator can access.

Portal ------> Developer

Roles--------> The level of access ( Administrator( Save the Instances, Delete the instances, Update the instances and all), manager(He can access only the business Rules) )

Application Design and Development

When we develop a application in PRPC there are two types of layers

1. Framework layer

2. Implementation layer

Frame Work Application:

It is an application where we built common functionality of entire business, those can be reuse different type of business implementation.

Implementation Application:

It is an application where we built specific functionality of specific business process.

EX:
In a Bank

Entire bank is frame work .

Personal Banking, commercial Banking mortgage Banking etc.... Are different implementation, where the actual business process of transaction happens.

Framework and implementation application should be created from same organisation.

RULES:

Rule are building blocks of an application and that influence the application behavior.

EX: Application = building
Rules = Bricks

Pega is s Rule based architecture

RULE SET:

Rule set is a container which holds all the rules. While creating any Rule, we need to make sure to place rule into a rule set. The main purpose of rule set is for deployment and security.

Every rule must be associated with the below three

1. Application

2. Class

3. RuleSet + Version

FLOW ACTION:

It is a process rule, which allows us to perform an action on the assignment, and moves the case from current assignment to next level in the flow.

TWO TYPES OF FLOW ACTION:

1. Connector Flow action:

It is a process rule, which allows us to perform an action on the assignment, and moves the case from current assignment to next level in the flow.

2. Local Action:

It is a process rule, which allows us to perform an action on the assignment, but the case will be still on same assignment even after the action performed.

EX: Pop up forms, Attached documents to case etc.

Local action can be called from:

1. HTML controls like buttons, text inputs etc (Sections)

2. assignment shape.

3.Under design tab of flow.

Local action that we can call on assignment shapes or design tab of flow, can be accessed using the action drop down of work object forms.

Assignment level Local Action:

When we call a local action on assignment shape, it will be available to access on when the case at the specific assignment

Flow wide Local Action :

When we call a local action on under design tab of flow, it will be accessible at all the assignments of that flow.

Sandeep's Blog

Application creation in PRPC