You are on page 1of 6

10/30/2017 Basics: Architecture ,Guardials, Inheritance, Methodology,classes 6'Rs

Basics: Architecture ,Guardials, Inheritance, Methodology,classes 6'Rs


1. What are the different layers in Architecture?
A robust class structure is the foundation of reuse throughout our application. The PRPC recommended class
structure design pattern offers flexibility in our design and provides for more levels of reuse.
There are 4 distinct layers in the PRPC best practice class structure design pattern:
1. PRPC Shared Product: The PRPC Shared Product represents the out-of-the-box Process Commander
classes such as Work-, Work-Object-, Work-Folder-, Work-Cover-, and Data-
2. Enterprise Shared Product Layer: The Enterprise Shared Product Layer is a library of extensions to
the PRPC base functionality. You should always include this layer. It is rare, but this layer may be omitted
in some very small one-off applications.
3. Generalized Application Layer: The Generalized Application Layer represents a generic base application
to use as a framework for application instances. Here we will define most of the rules for our base
application.
4. Organizational and Specialized Application Layer: The Organizational and Specialized Application
Layer represents an organizational application instance. Here we will be implementing the generic
application.

The class structure provides the first and most important layer of reuse and specialization in PRPC due to its
precedents in the rule resolution algorithm.
The class structure provides us with a hierarchy in which rules can be placed. The higher a rule is in the
hierarchy, the more potential reuse there is. However, a rule can only reference other rules at the same
level in the hierarchy or higher. For example, a rule X at class A- cannot call Rule Y defined at A-B if no rule Y
exists at A-.
The key to a good class structure is that there are enough layers and classes to hold the most fundamental levels
of reuse but not too many that it becomes cumbersome to navigate and unclear as to the intent.
Shared RuleSets provide a grouping mechanism for sharing both class resolved and non-class resolved rules. For
example Rule HTML properties and utility functions are non-class resolved. RuleSets are key to reusability as
they are the mechanism by which shared rules are moved to different rule bases and/or environments.

2. How many guardrails are there and explain?


Dynamic Views theme. Theme images by borchee. Powered by Blogger.
http://pegaguide.blogspot.in/2016/04/basics-architecture-guardials.html 1/6
10/30/2017 Basics: Architecture ,Guardials, Inheritance, Methodology,classes 6'Rs

There are 10 guardrails in the prpc application. They are


1) Adopt an Iterative Approach: Define a project initial scope by documenting 5 concrete scenarios up front and
evaluate them at the end to calibrate business benefits. Here It goes iteratively up and down in the Pega
methodology
.
Here comes Pega methodology

Scenario1: BVA Business Value Assignment: Defines success factors and expected ROI.
Scenario2: Conception: Discover detailed business requirements and solutions.
Scenario3: Elaboration: Design solutions tailored to the business requirements.
Scenario4: Constructions: Build the application to meet the requirements.
Scenario5: Transition: Validate the application for appropriate implementation of business process.
Deploy the application ,training, and help desk for final production support.

2) Establish a Robust Foundation: Design Class structure with recommended class pattern i.e it should be
understandable, easy to extend and utilize standard work and data classes appropriately.
3) Do Nothing is hard: Use out of box functionality as much as possible in Initial project release such as avoiding
custom html screens, buttons( simply to avoid custom in every aspect)
4) Limit custom Java: Avoid Java Steps in Activities.
5) Build For Change: Identify and define 10-100 Specific rules that business users own and will maintain.
6) Design Intent-driven process: Application Control Structure consist of flows, declarative rules and calling
activity as needed
7) Create easy to read flows: Flow must fit on one page and max of only 15 smart shapes, if exceeds then go for
creating subflows.
8) Monitor Performance Regularly: Must evaluate and tune application performance at least weekly using
Performance Analyzer (PAL) to check rule and activity efficiency.
9) Calculate And Edit Declaratively, Not Procedurally: Whenever the value of the property is calculated or
validated, we must use declarative rules wherever required.( use declare expression instead of property set
method.
10) Keep Security Object oriented too: Security design must be rule based and role-driven based on who should
have acces to each type of work.

3. Many Process Commander applications provide business process management and automation
through six functional capabilities, informally known as the Six R's:

Receiving Accepting and capturing the essential data describing work from multiple sources in multiple media
and formats, from keyboards, scanners, and external systems.
Dynamic Views theme. Theme images by borchee. Powered by Blogger.
http://pegaguide.blogspot.in/2016/04/basics-architecture-guardials.html 2/6
10/30/2017 Basics: Architecture ,Guardials, Inheritance, Methodology,classes 6'Rs

Routing Using characteristics of the work and knowledge about the workforce to make intelligent matches and
assignments.
Reporting Providing real-time visibility of work in progress, work completed, productivity, bottlenecks, and
quality.
Responding Communicating status, requests for information, and progress to the work originator and to other
people involved in the work, by e-mail, fax, written mail, and other means.
Researching Accessing external systems and databases through connectors to support analysis and
decisionmaking.
Resolving Through automated processing and automated support of users, completing the work and updating
downstream systems promptly.

4. What are the Inheritance types?


Process Commander provides two kinds of class inheritance, known as directed inheritance and pattern
inheritance.
Pattern inheritance, an optional feature we can set up for a class in the Rule-Obj-Class rule, affects the first steps
in the rule resolution algorithm. This approach is sometimes called "dual" inheritance.
During rule resolution, pattern inheritance causes a class to inherit rules first from classes that match a prefix of the
class name.
Directed inheritance Allows us to name a parent class, choosing a name that's not related to the name of this
class

5. How pattern and directed inheritance works?


Pattern Inheritance works as follows:
Rule resolution always looks first for a rule it needs in the class initially provided,
regardless of the state of this check box. If the box is checked and the rule is not found, it
forms a sequence of candidate classes to search by truncating, from the left, portions of
the class name that consist only of a dash character, or consist only of characters other
than a dash. If no class exists for one of these computed names, rule resolution continues
with the next prefix.
For ex: a search for a rule in the MyBank-LoanOrg-LoanDept class could search through these classes, in the
order indicated:
MyBank-LoanOrg-LoanDept
MyBank-LoanOrg-
MyBank-LoanOrg
MyBank-
Dynamic Views theme. Theme images by borchee. Powered by Blogger.
http://pegaguide.blogspot.in/2016/04/basics-architecture-guardials.html 3/6
10/30/2017 Basics: Architecture ,Guardials, Inheritance, Methodology,classes 6'Rs

MyBank
Directed Inheritance works as follows:
If the pattern search finishes without finding a rule, go back to the original class and use
directed inheritance to find the parent of the original class.

6. What are Pega default classes?


A base class is one of twelve standard abstract classes that are immediately below the top class in the hierarchy.
This top class, known as the ultimate base class, is identified by the symbol @baseclass.
The three base classes of greatest interest to application developers are Data-, Assign- and Work-.
The base classes are:
Assign- Assignment instances, each identifying a step in a workflow that requires human input or
work by an outside organization, person, or system.
Code- Classes that directly reference server program code. Pages belonging to classes derived from
the Code- base class exist only temporarily in memory, and are not saved in the PegaRULES
database.
Data- Parent class of concrete classes containing reference data, including data for system
administration and security.
Embed- Defines the structure of pages embedded within other pages. Pages belonging to classes
derived from the Embed- base class cannot be renamed or directly saved.
History- Append-only instances record the change history of objects in another class.
Index- Secondary access keys defined to provide fast retrieval of other instances.
Link- Instances that record associations between two objects.
Log- Parent of concrete classes containing cumulative logs of important system-wide events.
PegaAccel- Parent of special classes that support the Application Accelerator tool.
Rule- Rule types, for defining applications.
System- Contains operational status information about the entire Process Commander system.
Work- Work objects, covers, and folders.

7. Difference between Work- and Data- classes?


The Work- base class, one of thirteen standard top level abstract classes, is a superclass to all the classes that
define work objects. A work object is the fundamental unit that records processed work in an application.
The Data- base class is an abstract class above various classes that define and contain static data and cumulative
data. For example, the Data-Admin- classes contain information created by your Process Commander
developers defining who can use the application, their privileges and security, and where they belong in the
organization.

8. What are the types of classes?


Dynamic Views theme. Theme images by borchee. Powered by Blogger.
http://pegaguide.blogspot.in/2016/04/basics-architecture-guardials.html 4/6
10/30/2017 Basics: Architecture ,Guardials, Inheritance, Methodology,classes 6'Rs

A class is an instance of the Rule-Obj-Class rule type.


An abstract class is a rule (an instance of the Rule-Obj-Class class) created to support the definition of rules,
including other classes. Such rules can be inherited by subclasses of the abstract class. Rules with a class as a
key part (such as properties, activities, flows, models, and so on) can apply to an abstract class.
A concrete class can have instances stored in the database. An abstract class cannot have any instances.

9. What is a class group and what are its advantages?


A Class Group is an instance of the Data-Admin-DB-ClassGroup class.

Pega (PRPC) Concepts A class group instance causes the system to store the instances corresponding to two or more concrete classes
search
that share a common key format in a single database table. Class groups are commonly used to cause the
system to store instances of similar or related work- concrete classes together in one relational database table.
Classic Flipcard Magazine MosaicClass
Sidebar
GroupsSnapshot
generally mapped
Timeslideto pc_work table. We can use our own table also similar to pc_work for the class
groups All the classes who belong to a class group can inherit all the rulesclared and defined at the class group
All about Class 11 level.

Flow Shapes 3
Posted 1st April 2016 by Raj
Flow Actions 1
1 View comments

Flows 2
Kunal Deshmukh 10 March 2017 at 03:59

Case management: A This was a fantastic Blog. Really loved reading your blog post. It is very interesting to learn and easy to understood.
Thanks for sharing information. I am waitingfor next blog . If some one interested to learn architecture join Architecture
college in Pune.
Basics: Architec 1 Reply

November 9th, 2

November 2nd, 2014

November 1st, 4

November 1st, 2014

October 31st, 2014 Dynamic Views theme. Theme images by borchee. Powered by Blogger.
http://pegaguide.blogspot.in/2016/04/basics-architecture-guardials.html 5/6
10/30/2017 Basics: Architecture ,Guardials, Inheritance, Methodology,classes 6'Rs

October 31st, 2 3
Enter your comment...

October 31st, 2014

October 31st, 2 1 Comment as: Select profile.

Publish Preview

Dynamic Views theme. Theme images by borchee. Powered by Blogger.


http://pegaguide.blogspot.in/2016/04/basics-architecture-guardials.html 6/6