Question
Ruleset types
Please address the below query regarding Ruleset types.
1. What is the difference between shared/component and standard ruleset. I understand that, component ruleset is used to achieve encapsulation, to group related rules. The same can be achieved in standard ruleset also. Why do we separately have Shared/Component ruleset?
Accepted Solution
Hi,
Hi,
The Feature of Shared RuleSets, which distinguishes them from RuleSets “used in more than one application,” is the fact that Shared and Component RuleSets will sort to the bottom of an application RuleSet List – only the Process Commander RuleSets are lower in the list. (See Example below.) This means that the rules in a Shared RuleSet cannot depend upon functionality from any other RuleSets except for Process Commander RuleSets – including other Shared or Component RuleSets (since they may be listed in a different order in different application rule definitions).
If you have functionality in a RuleSet which is included in several applications, and you think this RuleSet should be designated as type Shared, look at where that RuleSet is in the current application RuleSet List. If this RuleSet contains classes, or if it depends upon other RuleSets which are lower in the list, then it cannot be marked as type Shared, even if you consider this a “shared” RuleSet. This RuleSet must be defined as type Standard, and listed under the Application RuleSets section of the application rule.
You can refer below articles
https://docs-previous.pega.com/when-create-shared-rulesets
https://docs-previous.pega.com/how-create-component
https://collaborate.pega.com/question/component-ruleset-why-how-when
Thank You
Hi Naveen,
You can go through the pega documentation for these three types of rulesets as follows:
Hope this might give you the broader picture about these rulesets.
Regards
Mahesh
Accepted Solution
Hi,
Hi,
The Feature of Shared RuleSets, which distinguishes them from RuleSets “used in more than one application,” is the fact that Shared and Component RuleSets will sort to the bottom of an application RuleSet List – only the Process Commander RuleSets are lower in the list. (See Example below.) This means that the rules in a Shared RuleSet cannot depend upon functionality from any other RuleSets except for Process Commander RuleSets – including other Shared or Component RuleSets (since they may be listed in a different order in different application rule definitions).
If you have functionality in a RuleSet which is included in several applications, and you think this RuleSet should be designated as type Shared, look at where that RuleSet is in the current application RuleSet List. If this RuleSet contains classes, or if it depends upon other RuleSets which are lower in the list, then it cannot be marked as type Shared, even if you consider this a “shared” RuleSet. This RuleSet must be defined as type Standard, and listed under the Application RuleSets section of the application rule.
You can refer below articles
https://docs-previous.pega.com/when-create-shared-rulesets
https://docs-previous.pega.com/how-create-component
https://collaborate.pega.com/question/component-ruleset-why-how-when
Thank You