How to know/get the Complete List of Rules of Type in an Application
How can we get the Complete List of Rules of Type in an Application, like Complete list of Connect-SQL rules, Activities, sections etc.
Accepted Solution
LTI Mindtree
CA
Hi Raj,
In the Data-Rule-Summary class you can create a report definition that returns a count for every rule type in the system.
This class contains the following properties that are essential for rule reports:
pzInsKey — key of the rule instance. This property is useful for joining other classes as we might
do with Rule History reports.
pyClass — the class of the rule type. For example, Rule-Obj-Property is for property rules.
pyClassName — the Apply To class of the rule. This could be, for example, the work class of a
purchase request application.
pyRuleSet and pyRuleSetVersion — the ruleset and ruleset version.
pyRuleName — a unique identifier used by the system; for example, CountOfLineItems.
pyLabel — a short description of the rule. For example, the label for the property named
CountOfLineItems — could be Number of Items to Purchase.
pyRuleAvailable — the availability of a rule.
pxUpdateDateTime, pxUpdateOperator, and pxUpdateOpName — the most recent update
information.
Hi Raj,
In the Data-Rule-Summary class you can create a report definition that returns a count for every rule type in the system.
This class contains the following properties that are essential for rule reports:
pzInsKey — key of the rule instance. This property is useful for joining other classes as we might
do with Rule History reports.
pyClass — the class of the rule type. For example, Rule-Obj-Property is for property rules.
pyClassName — the Apply To class of the rule. This could be, for example, the work class of a
purchase request application.
pyRuleSet and pyRuleSetVersion — the ruleset and ruleset version.
pyRuleName — a unique identifier used by the system; for example, CountOfLineItems.
pyLabel — a short description of the rule. For example, the label for the property named
CountOfLineItems — could be Number of Items to Purchase.
pyRuleAvailable — the availability of a rule.
pxUpdateDateTime, pxUpdateOperator, and pxUpdateOpName — the most recent update
information.
You can join other classes with the rule classes in order to provide more granular information. Some of the classes that are most commonly joined with the rule classes are:
History-Rule instances represent rule updates.
Data-Rule-Locking instances represent locks, or checkouts, of each rule.
Index-Warning for rule warnings, like the performance warning that’s given if a non-optimized
property is used in a report.
Index-CustomFields for custom fields defined for rules – a feature specifically designed to aid rule
reporting
For more details you can read Rule reporting topic.
Pegasystems Inc.
IN
Hi,
I want to take the all latest unique records of a rule type from a ruleset to excel . Not viewing through pages in Records explorer.
Pegasystems Inc.
IN
Pegasystems Inc.
US
I checked the Find Rules landing page on my system and was able to see the breakdown of rules. I chose the 'Find By Ruleset, Version, Rule Type' and selected my application ruleset. I did have to refresh after initially opening the landing page but that may be because my system is slow right now due to limited resources on that machine. Do you see any results when using the landing page?
Accepted Solution
LTI Mindtree
CA
Hi Raj,
In the Data-Rule-Summary class you can create a report definition that returns a count for every rule type in the system.
This class contains the following properties that are essential for rule reports:
pzInsKey — key of the rule instance. This property is useful for joining other classes as we might
do with Rule History reports.
pyClass — the class of the rule type. For example, Rule-Obj-Property is for property rules.
pyClassName — the Apply To class of the rule. This could be, for example, the work class of a
purchase request application.
pyRuleSet and pyRuleSetVersion — the ruleset and ruleset version.
pyRuleName — a unique identifier used by the system; for example, CountOfLineItems.
pyLabel — a short description of the rule. For example, the label for the property named
CountOfLineItems — could be Number of Items to Purchase.
pyRuleAvailable — the availability of a rule.
pxUpdateDateTime, pxUpdateOperator, and pxUpdateOpName — the most recent update
information.
Hi Raj,
In the Data-Rule-Summary class you can create a report definition that returns a count for every rule type in the system.
This class contains the following properties that are essential for rule reports:
pzInsKey — key of the rule instance. This property is useful for joining other classes as we might
do with Rule History reports.
pyClass — the class of the rule type. For example, Rule-Obj-Property is for property rules.
pyClassName — the Apply To class of the rule. This could be, for example, the work class of a
purchase request application.
pyRuleSet and pyRuleSetVersion — the ruleset and ruleset version.
pyRuleName — a unique identifier used by the system; for example, CountOfLineItems.
pyLabel — a short description of the rule. For example, the label for the property named
CountOfLineItems — could be Number of Items to Purchase.
pyRuleAvailable — the availability of a rule.
pxUpdateDateTime, pxUpdateOperator, and pxUpdateOpName — the most recent update
information.
You can join other classes with the rule classes in order to provide more granular information. Some of the classes that are most commonly joined with the rule classes are:
History-Rule instances represent rule updates.
Data-Rule-Locking instances represent locks, or checkouts, of each rule.
Index-Warning for rule warnings, like the performance warning that’s given if a non-optimized
property is used in a report.
Index-CustomFields for custom fields defined for rules – a feature specifically designed to aid rule
reporting
For more details you can read Rule reporting topic.
Pegasystems Inc.
IN
Thanks Akshay for the reply and explanation.
I am able to run the report and get the rules, but
- Class “Data-Rule-Summary” is mapped to table rules.pr4_rule_vw table and not to pr4_rule table. Is it fine to get the records from pr4_rule_vw table? And could see that class “Rule-” is connected to pr4_rule table. I was unable to find the class “Rule-“ and also unable to run the report for the “Rule-” class. Do you have any idea why the class “Rule-” is hidden and unable to run the report is it because of “Rule-” class is abstract?
- Can we filter the report with highest RulesetVersion or UpdateDateTime? since I want only one record for each rule of highest ruleset version.
As curiosity to know asking this, how do you know that Data-Rule-Summary class is mapped to rules table ?
LTI Mindtree
CA
Yes, it's fine to get records from Class “Data-Rule-Summary”. As per Pega engine architecture rules are stored in this table as well. Refer report present under this class to get more idea. OOTB reports such as pxGuardrailDetailByApp which shows warning in the application are present in the same class.
You can write custom filter logic as per your requirements.