The class identifies the scope of the rule. You specify the class of a rule in the Apply to field. The class you select determines how extensively you can use the rule — within one case type, or across case types.
A class organizes rules within an application. The position of a class within the class hierarchy determines the reusability of the rules in that class.
The ruleset is the container for the rule. The ruleset identifies, stores, and manages the set of rules that define an application or a major portion of an application.
A class is a container for rules and it represents the applicability of a rule, which we often refer to as the scope of the rule. A class defines capabilities, rules such as Properties, Flows, and Sections, that are available to the class and its subordinate classes.
Could you please clarify, as per the above statement present in the mentioned module of SAE 2, Can we call a Class -- A container for rules.
As you stated, Ruleset is a container for rules in your answer, Can we call both Class and Ruleset -- container for rules.
It seems to be silly for me too. But, Please Clarify.
@Karthik, as per my understanding class is not a container of rules only the ruleset is the container of the rules. I would suggest you to raise this conflict with the documentation team for further clarification about this explanation.
As per my understanding, a class may contain rules from different ruleset but a ruleset contains rules from the same ruleset. It doesn't hold the rules from other rulesets but a class can contain all the rules which are defined in that scope irrespective of different ruleset. From this perspective, a class can be called as a container of rules.
Adding to my colleague information, the standard definitions which pega has provided as follows:
A class groups a collection of rules or other objects. Each class defines capabilities (rules that include properties, activities, and HTML forms) that are available to other, subordinate classes, or to instances of the class. Classes are organized into a hierarchy, where the system searches the class hierarchy from the current class upwards when looking for a rule to apply.
A ruleset identifies, stores, and manages the set of rules that define an application or a major portion of an application. A ruleset contains rule instances, which are divided into ruleset versions to support version management. A ruleset is identified in the system by the ruleset name.
As per the above definitions, i feel that ruleset is used to support the versioning of the set of the rules of an application.
First of all forget for a minute what you have learned about class and Ruleset.
we have different kind of data and we are classifying them by using data types like integer, text, data etc. These data types are pega inbuilt. They all are single data type definitions. What about if user want to define his own data type?
So simply for understanding purpose we can say that a class is a user defined data type. In pega data is divided in to so many types in short Work Type, Rule Type, Data Type and and related instances are called as "is a rule", "is a WO", "is a data instance".
because of pega flexible implementations we can perform more operations on each instance by creating rules under the related class or parent classes.
primary use of class is reusability, scalability.
Creates for identify, store, and manage the set of rules and uses for development, deployment and reusability.
Pega terms are "A ruleset is a container or an organizational construct used to identify, store, and manage a set of rules. The primary function of a ruleset is to group rules together for distribution. "