In pega, everything is called as rules/records

Rule Category - Rule Type - Rule:

• DataModel - Property - Age

Benefit of rules in pega:

The main benefit of using rules in pega is basically called as modularity.

• Modularity provides Versioning, Delegation, Reuse

1. Reuse: Creating a rule allows to reuse them in different places depending on the context or the scope in which it is placed.

2. Delegation:

The rule which are frequently changing, those rules are delegated to the clients directly for modification. eg: if we have a decision rule for discount change, only that rule can be delegated.

1. Versioning :

Major version - used when ever there is a substantial release in the application ( over all architecture ) Minor version - used when ever there is a interim release in the application ( small enhacements ) Patch version - used to fix the small bug or other issues in the rule.

• There are many types of ruleset available : Application Rs, Organization Rs, Branch RS, Personal RS, Production RS etc. Since there are so many ruleset and there are so many rules inside each ruleset , how pega will search the rule from the correct ruleset ?

Checkout:

After the rule is locked, we need a situation where we modify the rules. in this case, developer or operator who is working on the rule should have the previlige to check out the rule. note : in the operator profile , under security tab, we can find "allow rule check out option" also in the Ruleset window, under security tab, we can find "use checkout option"