Professional Documents
Culture Documents
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.
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.
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.
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 1st, 4
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...
Publish Preview