PEGA PRPC Basics

 MyknowPega Blogger: PEGA PRPC Basics

Day-1 and 2

Business Process Management

Business Process Management is the organizational activity that incorporates:

·         Planning

·         Designing

·         Building

·         Operating

·         Maintaining

and improving the business processes and their enabling capabilities forever and for everyone. Business processes are capabilities, as important as facilities, people, and technology. Like other assets, they must be managed from inception to retirement.

Process Commander supports Simply Smart Business Process Management through rules covering flows, assignments, routing, decisions, and automated processing.

Business Rules Engine

A business rules engine is a software component that allows business rules to be recorded in a non-procedural, non-programming form, and uses advanced software techniques to compute the consequences and results of rules.

Organization- Process Commander 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.

Worklist -A worklist is an element of the ProcessWork workspace home page. It lists open, outstanding (not complete) assignments waiting for a user to perform them.

The worklist display shows all assignments for user on the current Process Commander system, whether that user works on a single application or multiple applications hosted in one system.

Workbasket- A workbasket is a common pool of open assignments that are not associated with particular user.

RuleSet- Each RuleSet defines a major subset of rules in the PegaRULES database, because every instance of every rule type references or "belongs to" a RuleSet.

In other words ruleset is a collection of rules.

Ruleset version-version rule is referenced with a special syntax consisting of a RuleSet Name value, a colon, and three two-digit values, known as the major version, minor version, and patch version, in the format

eg. RuleSetName:NN-NN-NN, where the NN values can be from 01 to 99

Major version-The major version number of a RuleSet version consists of the first two digits of the complete version number. For the RuleSet version Alberta: 04-01-07, the major version number is 04 and the minor version number is 01.

Minor version-The minor version number of a RuleSet version consists of the middle two digits of the complete version number. For the RuleSet version Alberta: 04-01-07, the major version number is 04 and the minor version number is 01. The final two digits are known as the patch version.

Patch- The patch version number of a RuleSet version consists of the final two digits of the complete version number. For the RuleSet version Alberta: 04-01-07, the patch version number is 07.

Inheritance- Inheritance defines how the PRPC finds a particular rule in a list of classes.Class inheritance searches for rules from a concrete, lower class, up the class hierarchy to find available rules.

There are two types of inheritance- Pattern and directed.

Directed inheritance — Allows you to name a parent class, choosing a name that's not related to the name of this class. There can be only one directed inheritance it is mandatory to have directed inheritance.

Pattern inheritance — The system determines the name of the parent class is based on an initial portion or substring of the name of the class. Segments of the name are delimited by a dash (-) character

If both pattern and directed inheritance are specified in class rule then pattern inheritance takes precedence.

Day-3

Division

A division is an instance of the Data-Admin-OrgDivision class and is the middle level of the three-level organizational hierarchy available in all applications. Divisions are below the organization level (Data-Admin-Organization class) and above the organization unit level (Data-Admin-OrgUnit class).

Divisions are referenced in Organization Units and in Operator ID instances.

The organizational structure affects:

• Management reporting and statistics
• Each user's RuleSet list assembled during log in

Unit

An organization unit is an instance of the Data-Admin-OrgUnit class. Organization units form the bottom level of a standard three-level organizational hierarchy available in every Process Commander application. The middle level consists of divisions (instances of the class Data-Admin-OrgDivision) and the top level is the Organization level (Data-Admin-Organization class).

The organizational structure affects:

• Management reporting and statistics visible from the Monitor Activity workspace
• Users' RuleSet list, assembled as they log in

Work group

A work group is an instance of the Data-Admin-WorkGroup class. A work group can identify a user who is a supervisor, and a set of workers and workbaskets that report to that supervisor.

For the supervisor of a work group, the My Group area of the Process Work space provides quick access to the worklists and workbaskets associated with the group. Work groups are a primary unit of summarization in standard management reports on the Monitor Activity workspace.

An Operator ID data instance (Data-Admin-Operator-ID class) usually identifies a work group to which a user belongs. If left blank, that operator can enter work objects but not access a worklist or workbaskets.

Class group

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

A class group instance causes the system to store the instances corresponding to two or more concrete classes that share a common key format in a single database table. The name of the class group is a prefix of the names of the member classes.

Class groups are commonly used to cause the system to store instances of similar or related work object concrete classes together in one relational database table

Work pool

The work pool for a user is the set of all the work objects (open and resolved) of all the Work- classes that a user can enter (in one application).
The system determines which work types (which classes derived from the Work- base class) a user can enter from a list of class groups. These class groups are specified in an access group associated with that user.
A single user can create work objects that belong to different class groups. For example, suppose three applications are defined by RuleSets Alpha, Beta, and Gamma. Assume that each application has one class of work objects, with the class names Work-Alpha, Work-Beta, and Work-Gamma, and that one class group is defined for each application.

·         Tom's access group can let Tom be a user of only the Alpha application. Tom can create, review, and update only Alpha work objects.

·         User Mary is a user of both Beta and Gamma applications and so can create, review, and update both Alpha and Beta work objects.

·         User Fred can access all three applications.

Operator ID

An Operator ID instance is the saved object in the Data-Admin-Operator-ID class that defines a user's name, password, access group, organizational setting, calendar, and other values. Informally, the term Operator ID refers to the key field of that data instance, equivalent to a user name in other software settings.

Application

An application rule defines a set of RuleSet versions to be added as a unit to a user's RuleSet list. An application rule is an instance of the Rule-Application rule type, which is part of the Application Definition category.

Access Group

An access group is an instance of the Data-Admin-Operator-AccessGroup class. Access groups make a set of RuleSet versions available to requestors.

Developers define access groups and associate an access group with each user (each Data-Admin-Operator-ID instance). Typically, multiple users are associated with or belong to one access group.

The access group associated with a user affects access control by determining:

• The portal layout that a user sees first after logging in.
• The application rule for this user.
• Optionally, the access roles available to this user.
• The work pools available to the user

Access Roles

An access role is an instance of the Rule-Access-Role-Name rule type. An access role can be assigned to users (or requestors) to influence their access control. These roles determine what operations they can perform on what classes.

At log in, the system assembles a set of roles for a user based on information in a user's requestor instance, Operator ID instance, and the associated access group instance. Access roles associated with a user are empowering, as they grant capabilities.
Access roles influence which classes a user can view, update, delete, and so on through the Access of Role to Object and Access Deny rule types.

Pega Standard Rulesets

·         Pega-Procomm

·         Pega-IntSrvcs

·         Pega-WB

·         Pega-Rules

Places where rulesets can be mentioned:-

·         Operator ID

·         Division

·         Organization

·         Requestor

Flows govern:

·         How work objects are created

·         How they progress through the system

·         How they become resolved (completed)

·         Flow Requirements

·         A work object is required to run a flow

·         Start and end shapes 

·         Interim shapes (e.g. assignments, decisions, forks, etc.)

Flow Types

}  Starter Flow

Ø  Supports creation of a new work object.

}  Straight-Through Process

Ø  Performed automatically with no human intervention.(No Assignments shapes)

Ø  A flow rule that contains no assignment tasks by definition implements straight through processing.

• Screen Flow

Ø  Presents a user with a series of simple forms that each require input.

}  Subflow

Ø  A flow that is called by another flow.

Assignment Shape

• Assignment is a pause in the flow and it signifies that a person or external system must act on a work object before the flow can progress.
•  Assignments are created by a flow operating on a work object, but they are not themselves part of the work object. Whenever a workobject reaches an assignment, it creates an instance of respective Assign-* class. This instance stores all the assignment pertaining information rather than work object itself.

Identify the standard harnesses and their functions

• New   - For creating new work objects
• Perform – Performing assignments on existing objects
• Confirm – Confirming object resolution
• Review – Reviewing the closed objects
• Reopen - Reopening the closed objects

                                    NewCovered – To open a cover object

}  Section ( Rule-HTML-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. Flow Action also

◦       A section rule defines the appearance and contents of one horizontal portion of a work object form.

}  HTML Property ( Rule-HTML-Section)

◦       Use HTML Property rules to control how properties appear on work object forms, correspondence, and other HTML forms, for both display and for accepting user input.

–   It is not good practice to hardcode the list of field values inside the Rule-HTML-Property, Instead we have to use Rule-Obj-Field value or Table edit of the property.

–   Nine standard HTML Property rules accept input parameters

–   Date

–   DateTime

–   Decimal

–   Integer

–   Percentage

–   PromptSelect

–   Text

–   TextArea

–   Time