How To Create And Update A Rule In PEGA || Rule Resolution In PEGA || Rule Check Out And Checkin In PEGA

Introduction

Hello Guys,in this post you can learn about the following concepts,please feel free to comment or contact me in case of any information required
I.How To Create a Rule in PEGA
2.How To Update a Rule in PEGA
3.Rule Check Out,Checkin & Private Edit in Pega

How To Create a Rule in PEGA

When we create a rule in Pega, the new record form asks you to provide 4 pieces of information, this information is used to identify the rule uniquely within your application. The information that you have to provide to create a rule in Pega is

1.Rule Type

2.Identifier

3.Class

4.RuleSet

1.Rule Type

The Rule Type determines the type of behvaiour models by the rule.Each rule models a specific type od behaviour,such as automated decisions,UI design or data storage.

2.Identifier

The Identifier identifies the purpose of the rule.For example,to model the process for approving insurense claims, you use a identifier allows you use a identifier as Claims APprovel.

3.Class

The Class identifies the scope of the rule. You specify the class of rule in the APpply to Fields. The class you select determines the extent of how you can use the rule within one case type or across cases types.

4.RuleSet

The RuleSet is the container for the rule .The Ruleset identifies,stores and manages the set of rules that define an application or major portion of an application

Rule Resolution In PEGA

The combination of rule type ,name,class and ruleset allows pega to provide an unique identity for each rule.This combination allows an application to call the correct rule during case procssing through a process called Rule Resolution.While Rule Resolution,pega determines the appropriate rule to run when a application calls a rule.

After you complete the New Record form, click Create and open to configure the rule behavior.

How To Update a Rule in PEGA

The system architects often secure rulesets to prevent unauthorized changes to rules. When you edit the rules in secured ruleset, you either check out the rule or perform a private edit.

Rule Check Out & Check In

The check out feature is used to manage changes to rules when multiple developers work on an application. The feature allows the system architect to update a rule while preventing updated by other architects. Rule check-out creates a copy of rule in a rule set that is only visible to you, called a Personal Ruleset. After the update a rule and test the changes, you check in the rule. This updates the application ruleset with a new version of the rule.

Checking Out A Rule

Checking out a rule creates a copy of the original rule in your personal ruleset and prevents other system architects from checking the rule out until you check in your changes. On the rule form header, click Check out to check out the rule.

In Dev Studio header,click on Checkouts icon to view list of rules that ypu have checked out so for.

Checking In A Rule

When you finish editing the rule, click save to save your changes and checkout rule. This commits the updated rule to your personal ruleset. After you save the rule, you can test your changes.wHEN You can check out a rule, the rule header updates with three new buttons as Checkin, Discard and Save.

Private Edit A Rule

A Private Edit provides a non-exclusive check out of the rule.This allows other system architects to edit the rule at the same time. Private edits are useful for quick debugging without interrupting development by other team members. This option is not available in App studio.

It is the best practice to lock older versions of a ruleset in order to prevent changes. For rules in a locked ruleset, a lock icon is displayed on the rule form. To update a rule in a locked ruleset version, save the rule to an unlocked ruleset version, then check out the rule if necessary.