day2- pega training

7/25/2019 Day2- PEGA Training

1/14

RuleSet, AccessGroup & Operator- Day2

By Vishnu Jaiswal


2/14

Confidential 2! Syntel, "nc#

2

A$enda


3/14


%

Or$aniation

Or$aniation'Organization is on top of the organization hierarchy. It is an instance of Data-Admin-

Organization.

By Default PRPC is shipped ith and Organization called Pega.com.

Si$nificance of addin$ rulesets at Or$aniation' !e can add one or more rulesets to organization for pro"iding access to all the users #elonging to

that organization to the specified ruleset. Assume an application li$e %lea"e application& hich needs to #e accessed #y all the employees

of organization' then e can add lea"e application(s rulesets at Organization le"el.

Si$nificance of addin$ top le(el class at Or$aniation'

!e can optionally specify a top le"el class hen an organization is created.

It does not ha"e much significance e)cept it is used as default top le"el class hen the users

#elonging to the organization uses application accelerator to create an application


4/14


)

*i(ision & +nit

*i(ision* Di"isions is at a second le"el in the organization hierarchy right after the Organization. It is

an instance of the class Data-Admin-OrgDi"ision

!hile you are creating a ne di"ision' you ha"e to specify +,andatory to hich organization it

#elongs.

Si$nificance of addin$ rulesets at *i(ision'

!e can add one or more rulesets to di"ision for pro"iding access to all the users #elonging to that

di"ision.

Assume an application li$e %oan application& of a #an$ hich needs to #e accessed only #y the

employees of oans di"ision' then perhaps e may li$e to add oan application(s rulesets at oandi"ision le"el' so that other di"isions in the same organization can not ha"e access the ruleset

+nit'/nit is at a third le"el in the organization hierarchy right after the di"ision. It is an instance of the

class Data-Admin-Org/nit.

!hile you are creating a ne unit' you ha"e to specify +,andatory to hich organization and di"ision it

#elongs.


5/14


Or$aniational -ierarchy'

Or$aniation

At the top le"el' thisidentifies the company

entity.

+nit

At the ne)t le"el' this

identifies the most specific

le"el at hich organization

information is recorded

*i(ision

At the second le"el' this identifies thehighest-le"el entities of the company.

0or e)ample' you might use the

structure of your company1s senior

management team as a starting place

for di"ision-le"el entities.

Process Commander supports a three-le"el organizational hierarchy consisting of organizations at

the top le"el' di"isions at a second le"el' and organization units as a third le"el. ach user

+Operator ID instance is associated ith an organization' di"ision' and unit.


6/14


.

Basic Or$aniational -ierarchy Structure

Process Commander applications group organizational data hierarchically' using nested le"els oforganization' di"ision' and unit. 3he folloing structure shos a sample organizational hierarchy ith oneorganization' to di"isions' and three units.

)ample* 3he a#o"e 4ierarchy shos an e)tended organizational hierarchy. 3he Chennai' ,um#ai and

Pune di"isions each ha"e I3 and Admin units5 each I3 unit' in turn' has 4ealthCare and Ban$ing or$

groups. All or$ group managers are afforded additional pri"ileges #y #elonging to the ,anagers access

group.


7/14


/

Operator "*

An Operator ID defines a user1s name' passord' access group' organizational setting' calendar' and

other "alues.

3he operator ID references an access group that contains the Rule6et "ersions' roles' portal layouts'and applications a"aila#le to users.

3he operator ID defines hat a user is capa#le of doing' not hat the user is alloed to do. 3hree

instances are created automatically hen Process Commander is installed*

PegaR/6 Administrator 7Default administrator created at installation

Batch Processing 7Default #atch re8uestor created at installation

)ternal /ser 7Default user for e)ternal applications

An Operator ID data instance is sometimes called a profile. 3o "ie your Operator ID instance' clic$ the

lin$ containing your name in the De"eloper portal na"igation panel.

Operator ID instances are normally stored in the PegaR/6 data#ase as ros of the pr operators

ta#le

Operators are created through instances of Data-Admin-Operator-ID class

Important entries hile creating the operators are

Organization + ,andatory Di"ision + ,andatory

/nit + ,andatory

!or$group + ,andatory

Access 9roup + ,andatory

Allo Rule Chec$ Out + Chec$ #o) + Optional


8/14


0

1or Groups & Access Groups

!hen users log in ith an operator ID' their organizational affiliations grant them appropriate Rule6et

access. 3he ID also identifies to additional affiliations* or$ group and access group

1or Groups' /sers and the or$ they do are tied to or$ groups' hich fall #elo units in an

e)tended organizational hierarchy. /sers or$ing on a common set of items generally #elong to a

single or$ group.

Access Groups' /sers1 application permissions' portal layout' and accessi#le or$ are controlled #y

access groups. Access groups may span multiple or$ groups' and typically mirror ProcessCommander :o# functions.

Standard Access Groups* Process Commander pro"ides the folloing standard access groups

;. PegaR/6*Administrators

2. PegaR/6*Agents

. PegaR/6*6ystemArchitects

?. PegaR/6*/nauthenticated

@. PegaR/6*!or$,anagers

. PegaR/6*!or$/sers


9/14


!

1or Groups & Access Groups 3 contd##

1orin$ of Access Groups '

Access groups ma$e a set of Rule6et "ersions

a"aila#le to set of users. ,ultiple users areassociated ith one access group.

Access group represents a person(s :o# function

and alloed actions in a Process Commander

en"ironment.

It controls the applications' or$ portal ta#s'

and groups of or$ +or or$ pools you can

accessAccess groups are assigned to users through

their operator ID records' the di"ision and

organization to hich they #elong' and through

re8uestor definitions.

Process Commander Applications use a

com#ination of operator ID' access group' and

access role to control hat each user can seeand do ithin the system.

!hen users log in ith an operator ID' their

access group determines their application portal

layout and the Rule6ets they can access.


10/14


4

Rules, RuleSets and RuleSet Versions

Rule'

A Rule is a named #usiness o#:ect that defines #eha"ior of part of an application.

It is piece of #usiness logic that encompasses practice' process and system functionsPro"ides #oth practice and process rules.

Practice rule-Business guidelines or policies.

Process rule-Procedural steps that must #e folloed to complete a piece of or$

P9A is a Rule ngine' e"erything is a Rule in P9A. All Rules are stored in distinct #usiness rule

data#ase +Rule #ase.

0or e)ample' a hen condition is a rule that defines a test that returns true or false.

RuleSet'

Rule6et stores a set of rules and related processes of a specific application.

Rule6et pro"ides "ersioning and security to an application.

3here are to parts in a Rule6et* Rule6et ame and Rule6et ersion

ach Rule6et defines a ma:or su#set of rules in the PegaR/6 data#ase' #ecause e"ery instance of

e"ery rule type references or #elongs to a Rule6et.

RuleRule Rule

Rule

Rule

Rule

Rule


11/14Confidential 2! Syntel, "nc#

44

RuleSet

RuleSet'

A Rule6et name is an instance of the Rule-Rule6et-ame rule type. A Rule6et name is created to

identify' store and manage a set of interrelated rules that define an application. "ery rule type instancein the PegaR/6 data#ase E#elongs( to a Rule6et.

A Rule6et name also plays a ma:or role in defining the access control for users in an application and

mo"ing applications from one PRPC system to another.

Base 5R5C RuleSets

6ome #ase Rule6et names are pro"ided ith a PRPC installation.

Pega-ProCom 7 6tandard rules that support #usiness process management +BP, applications

Pega-Int6"cs 7 6tandard rules that support integration

Pega-!B 7 6tandard rules that support the portal infrastructure

Pega-R/6 7 6tandard rules that support #usiness rules engine and rule resolution

3he a#o"e four Rule6ets form the foundation for all PRPC applications. All other Rule6ets created

during application de"elopment to group interrelated rules are E#uilt on top( of these Rule6ets.

In addition' any application de"eloper ho can chec$ out rules has a pri"ate Rule6et hich holds the

temporarily chec$ed out rule. 3he system creates each pri"ate Rule6et automatically' named to match

the de"eloper1s Operator ID "alue.



42

RuleSets Contd##

Guidelines'

6tart the Rule6et name ith a letter and use only letters' digits' and dashes. Choose names that are

short and easy to remem#er.Don1t choose a name that starts ith the four letters Pega' or other "ariations of this te)t ith different

case. 6uch Rule6ets ha"e special capa#ilities and are reser"ed for use #y Pegasystems Inc.

Rule6et names may #e up to ?= characters long' #ut normally are less than 2F characters long.

A Rule6et name must #e uni8ue system-ide

Steps to Create a new RuleSet'6elect Application G e G Rule6etH from the menus to access the e dialog #o).

Alternati"ely' choose Application G e G Rule G 6ysAdmin G Rule6et or use the Application )plorer

right-clic$ menu



4%

RuleSet Version

A Rule6et ersion is an instance of the Rule-Rule6et-ersion rule type.

A Rule6et ersion is referenced ith a special synta) consisting of the Rule6et name' colon' and threeto-digit "alues' $non as the ma:or' minor and the patch "ersion' in the format Rule6etame*--

.

A Rule6et ersion is created to identify' store and manage a set of interrelated su#set of rules of an

e"ol"ing application.

Rule6et ersions ha"e a three-part numeric $ey. 0or )ample* F;-F2-F

day2- pega training

Documents