Pega (PegaRULES
Process Commander)
BRE(BusinessRuleEngine)
Business Rules Engine (BRE) is a
software system that manages business rules, it separates the business rules
from the application code.
BPM (Business Process Management System
Business Process Management
System (BPMS) is a software system which allows for the direct execution of
business processes.
Removes the costly and time
intensive development of process specific software
Allows the full business process
to be defined
Can invoke external services to
perform business operations
Can send messages to human
workers requesting they perform certain tasks
Can call a Business Rules Engine
to make automated decisions
Provides a process driven User
Interface
Pega Rules Business Rules Engine
ContentMiddleAd
Separates business logic from
your mission-critical applications and enables your enterprise to capture,
manage and execute your business policies and practices
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.
§ 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 decision-making.
§ Resolving — Through
automated processing and automated support of users, completing the work and
updating downstream systems promptly.
Organization Model
PRPC
supports a three-level organizational hierarchy consisting of organizations at
the top level, divisions at a second level, and organization units as a third
level. Each user (Operator ID instance) is associated with an organization,
division, and unit.
ContentMiddleAd
Category
The Data-Admin-Organization class contains organization data instances. Organization data
instances are part of the Organization category.
Create a new organization data
instance by selecting
Organization from the Organization category.
The diagram presents the current
structure as a three-level tree: organization, division, and organization units
in your current organization (as displayed in your operator profile). To
display all organizations in your system.
The Data-Admin-OrgDivision
class contains division data instances. They are part of the Organization
category.
The Data-Admin-OrgUnit
class contains organization unit data instances. They are part of the
Organization category.
Select 
> Organization
And Security > Organization > Organization Chart to see the organizations in your
system.
> Organization
And Security > Organization > Organization Chart to see the organizations in your
system.
Operator ID
An
Operator ID data instance provides a user identifier (ID), a password and other
facts and preferences. This data instance also locates a user within an
organization structure, and identifies appropriate access roles and other
characteristics.
An
Operator ID data instance is sometimes called a profile. To view your
Operator ID instance, click the link containing your name in the Designer
Studio navigation panel.
Access Group:
An access group is associated with a user through the Operator
ID data instance. The access group determines:
- Their portal layout
- Which work pools are available
- The types of work items they
can enter
- Which RuleSets appear at the
top of their RuleSet list
- Which access roles and
privileges they hold
- Details of rule caching for
performance
RuleSet:
Create a RuleSet to identify,
store, and manage the set of rules that define an application or a major
portion of an application. Generally, you may need five to eight RuleSets per
application. Typically, these are created as you use the Application
Accelerator; you do not need to create them with the RuleSet form.
Ruleset Version:
A RuleSet version rule identifies a three-level version number
for a RuleSet. Use the New dialog to create a RuleSet and Version 01-01-01 in
one step. (XX-YY-ZZ)->XX-MAJOR,YY-MINOR,ZZ-PATCH
Although RuleSet and RuleSet Version are two distinct rule
types, they are maintained in a single RuleSet form. Use the Versions tab on this form to:
- Lock the version to prohibit
changes to rule instances.
- Record a start date for the
version.
- Identify dependencies between
this RuleSet version and other versions.
- Review, add, delete, or update
versions to an existing RuleSet.
Use application rules to define
an ordered set of RuleSets and versions that together identify the parts of a
PRPC application. In addition, application rules relate the application's
objectives, specifications, and actors to objects created as part of the Direct
Capture of Objectives tools and wizards.
Class
Always while designing the class structure, the best practice is
we should apply class level ‘sense’ according to the business hierarchical
structure of the organization.
Organization ---
Division --- Unit levels can be
transformed to Top level class --- Divisional level --- Class group level with
respect to PRPC. Each class group level will be a unit / application where in
different process can be initiated.
ContentMiddleAd
Class Group:
A Class group is an
instance of the Data-Admin-DB-ClassGroup. A class group instance causes the
system to store the instances corresponding to two or more concrete classes
that have 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.
While creating the
class group we need to specify the key for the group. Generally it is pyID.
Two type's of class's
1)Abstract
Abstract Classes can contain any
rule type
Cannot contain instances
Great for reuse
The name of a
abstract class must end with a dash (-).
2)Concrete
Concrete
classes hold persistent objects, known as instances
Names must not
end with a dash (-)
Names should define the type of
work being performed.
Top level classes
are always abstract and inherit from the @baseclass.
Top level class is
an abstract class that has the ultimate base class @baseclass as parent but
is not one of the standard base classes.
@baseclass is
called as the ultimate base class.
Understand the difference between pattern and directed
inheritance
- Pattern inheritance
causes
a class to inherit rules from classes that match the prefix of the class
name. Uses prefix segments that are followed by a hyphen.
- Directed inheritance is explicitly specified by the
developer. It allows a class to inherit from a class not related to its name. A
base level class always has directed inheritance from @baseclass .
- A
class can use both types of inheritance at the same time. It can have only
one pattern parent and one directed parent. Must always have a directed
parent.
- PRPC uses an algorithm to
determine inheritance Known as the Rule Resolution algorithm.
- For Determining Inheritance
Pattern inheritance is used first, If the algorithm fails to
- find any rules using pattern
inheritance, it starts again using directed inheritance
- While
creating the class, mentioning the direct inheritance is inevitable. Pattern
inheritance is optional. If pattern inheritance is mentioned by checking
in the check box, Pattern inheritance takes the precedence.
Work-Object-
–
A work object
is the primary unit of work completion in an application, and the primary
collection of data that a flow operates on.
–
As an application is
used, work objects are created, updated, and eventually closed (resolved).
–
Every work object has
a unique ID (property pyID), an urgency value, and a status (property
pyStatusWork).
A work object ID is the permanent, external identifier of a work
object, the value of property Work-.pyID.
Flows
- Represent
business processes
- Identify
who works on a work object and in what sequence
- Route
work to external systems for processing
- Identify
what decisions and processing happen automatically
Tasks
Connectors
Each with parameters and values
Flows can be configured to create work objects or can be added
to an existing work object
Flows must be built at the appropriate level within a class
structure to support reuse
You can leverage a common
process from a number of different specialized work objects, by calling the starting flow, which then calls
the “common process” sub-flow
- A
flow rule that contains no assignments, and so can execute from start to
end without human input, is known
as a straight-through process.
- A
flow rule that consists only of assignments or decisions and meets other
criteria is
known as a screen flow
(UI Customization- tabbed, Tree, Perform type).
- A
flow that creates a new work object is called a starter flow.
- A
flow that is called by another flow is known as a subflow, the calling flow is called
- parent
flow.
FlowAction
ContentMiddleAd
A flow action is a
choice available to users as an interim or final disposition of an assignment
they are processing.
Flow actions
Control how users
interact with work object forms to complete assignments
Can associate flow actions with connectors (arrows) and with
assignment tasks
Can associate a likelihood value.
Connector Flow actions
Identifies
possible path from assignment
Moving a work object to
the next part of the flow
Examples: Approve, Reject
local Flow actions
Describe actions that can
be taken during assignment processing Can change the state of the work object,
Does not move it along in the flow
Example:
- Attach
a file to a work object
- Send
a piece of optional correspondence
Section:
Section Rules define the form content, consisting the discrete
section that you include in the harness.
Section rules are referenced in harness rules, and may also be
referenced in other section rules.
A section rule defines the appearance and contents of one
horizontal portion of a work object form.
Harness
Harness Rules define the form structure and the layout,
specifying the sections that include in the harnesses and other elements to be
added.
Harness rule basically assembles all required sections, streams
and fragments.
No comments:
Post a Comment