2-Applicaiton, Types of Applications-1
2-Applicaiton, Types of Applications-1
2-Applicaiton, Types of Applications-1
Application is Set of Functionalities, which will be developed by using any technology. Application
achieves business Goals.
For example : We can take any online store, purchase centre website, this is an online store
application which has set of business functionalities like account creation, Product catalogue, Item
Search, Cart, Check out, payment gateway, purchase summary. All these are different functionalities.
Consider an Insurance Application where “Core Insurance” as a Framework and TWO different lines
of business “Vehicle “ & “Health” insurance. These two are two different implementation
applications.
As an initial setup, we create Core Insurance FW application, then , on top of this insurance
application, we will be creating Vehicle and Health implementation applciations.
Frame Work Application is meant for Maintaining the common Functionalities which can be re used
across different Implementation applications.
Implementation Application Will have Specific Functionalities related to the specific lines of
business.
Let’s look at above picture. The Functionalities like ‘Customer Details’, ‘Address Details’, ‘A Generic
Email Integration Business Logic’ & ‘Payment Gateway’ screen. All these functionalities, we may
need commonly accessible for “Vehicle’ & ‘Health’ insurance implementation applications. So that
why we have to place them into ‘Framework application’.
Where as, If we wish to create the forms to collect the details like “Vehicle Details” , then this is
specifically related to ‘Vehicle Insurance’ and a form to collect the customer health coverages, then
this is specifically related to ‘ Health Insurance’ . This type of screen are specific to one line of
business. So we create these two functionalities in the specific implementation applciations.
1. Re-Usability of features
2. Easy to maintain
3. Easy to extend the business processes.
4. Financial - Profit by selling the product
Summary :
As a best practice, when we create our application make sure it has both Framework and
Implementations.
https://www.youtube.com/watch?v=GCgfTgg0qx0
Done…
Pega Rules Process Commander
When we are working with PRPC, it’s good to know the basic terminology.
PRPC is application Development environment provided (by Pega Systems) to develop Business
Process Management Applications, using it’s ready made functionalities.
Business Applications can be developed without the need of coding (UI HTML, Business Logic , DB
Queries).
PRPC environment contains set of common business functionalities as OOTB rules. Some example
functionalities are “SendEmailNotification”, “UpdateCaseStatus”, “CommitWithErrorHandling” etc…
Operator ID: - The login ID or User Name which we use to login to PRPC environment to access it’s
applications.
Operator :- Is the person or user who login to PRPC to access it’s application.
On top left we can see Application: Pega Platform (The name of application is PegaRules).
When we use credentials [email protected], PRPC takes the Operator to a Built-In Appclaiton
“PegaRules”.
This Pegarules application is the one which holds all the readymade functionalities provided by pega.
As a note, remember, the application that we create must be created on top of Pega rules
application.
Done.
Now, let’s see how to create a new framework and implementation applciations.
The application which we are going to create, is going to have below structure.
Where as, we create implementation application on top of the above Framework application.
Done.