Featured post

GetNextWork functionality in pega

What is GetNextWork in pega? Pega provided a functionality to get the most urgent assignment(task) for user to work on. This is configured o...

Pega Ruleset

What is the order in which Rule set list is constructed?
Requestor, Organization, Division, Access Group is the order in which this list is constructed.
In access group, Application rule set list is in bottom and Production Rule set is on top of it. It follows Top-down approach.
 What is RuleSet?
A RuleSet name is an instance of the Rule-RuleSet-Name rule type. 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. A RuleSet name is a major aspect in:

·         Access control

·         Grouping interrelated rules

·         Managing the rules

·         Moving applications — sets of rules — from one Process Commander system to another.

Process Commander itself consists of six standard RuleSets:
·         Pega-AppDefinition — Standard rules supporting Direct Capture of Objectives features

·         Pega-ProCom — Standard rules that support business process management (BPM) applications

·         Pega-IntSvcs — Standard rules that support integration

·         Pega-WB — Standard rules that support the portal infrastructure

·         Pega-RULES — Standard rules that support business rules engine and rule resolution

·         CheckInCandidates — Optional. Empty, used by rule check-in processing. Version 01-01-01 is not locked.

 Any application developer who can checked out rules has a private RuleSet.

The system creates each private ruleset automatically named to match the developer’s operator ID value.

We create one ruleset per application.

Rule set names are part of SysAdmin category.

 What is ruleset versioning? Explain Major, minor and patch?

A RuleSet version is an instance of the Rule-RuleSet-Version rule type. The version number in the form AA-AA-AA, defines six digits in three groups that characterize the evolution and development of a rule instance, and of the application it belongs with. The three segments are known as the major version, minor version, and patch version.

For eg. LoanAdmin:01-02-03

Here, 01: major version

02: minor version

03: patch version

Major : for entirely new functionalities or major releases, the first two digits of the version is incremented.

Minor : for enhancements, middle two digits are incremented.

Patch : for bug fixes, last two digits are incremented.

 Rule resolution algorithm uses version numbers to find the most appropriate single rule instances to execute in a specific situation.

 Few rules are non-versioned

Application, class, RuleSet. Ruleset version, Access deny, Library.

 Explain about RuleSet types and the priority given in Rule Resolution?

Application RuleSet is a RuleSet that appears in any of the following form fields:

·         On the General tab of the application rule referenced in the access group for a requestor (when the current work pool is part of this application)

·         (Recursively) On the General tab of a ‘parent’ application rule, if they Include Parent check box on the General tab of a ‘child’ application is checked.

·         In the Local Customization field on the Settings tab of the access group

 Production RuleSet is a RuleSet that has the Type field set to Standard (on the Category tab of the RuleSet form) and that typically has at least one open (not secured) RuleSet Version.
Production RuleSets are listed on the General tab of an application rule and on the Layout tab of the Access Group form.

The application RuleSet does not include rules in RuleSets listed in the Production RuleSets array of the Access tab.

 During rule resolution, the system:

·         First priority given to Production Rulesets. First, search the rules in Rulesets available in Production RuleSet.

·         Next Searches the rules in the Rulesets listed in application Rulesets. First using the topmost RuleSet name and version on the list, then the next, and so on. Override RuleSet versions (the top layer are searched first; the Pega-RULES RuleSet is searched last)

·         Ignores any rule instances that match a RuleSet on the list but contain versions higher than the version on the list.

No comments:

Post a comment