RDB Methods:
Use Connect SQL rules and RDB methods only with an external database. Do not use Connect SQL rules or RDB methods for the PegaRULES database(s). Because not all properties in the PegaRULES databases are distinct database columns, use the Obj-Open and Obj-Save methods, not the RDB- methods, with the PegaRULES database to prevent loss of data.
Obj Methods:
At runtime, five methods (Obj-Browse, Obj-Filter, Obj-List, Obj-List-View, and RDB-List), list view rules, and summary view rules use a page of the class Code-Pega-List
Code-Pega-List class as a source of search criteria and to hold the output. Typically, such pages are named Results, pyQueryResultPage, or pyViewLookupList. Search results (which support rows of report output) are stored as pages in the pxResults() property, a Page List.
Work Type
Work Item
Work Pool
Work Group
Work List
Work Basket
Work Party
Work – base class
Every application requires at least one concrete class derived from the Work- base class.
Ruleset validation is being performed each and whenever a rule is saved. It ensures that referenced rules are accessible on the target system when the ruleset is advanced.
Ruleset validation doesn't influence rule resolution at the run time however it is applied at design time.
Activity-End method?
Use the Activity-End method to cause the system to End the current activity and all calling activities.
Pega Rule Circumstance
A circumstance is an optional qualification available for all rules. Using a circumstance allows our application to support multiple variants of a rule. For example, variations of an ordinary rule instance can be created for different customer status levels or for different geographic locations.
Rule Availability:
How to change Rule
Availability?
To
change the availability setting of a rule, click the Availability toolbar
button ().
We
may need to check out the rule first. A dialog box appears.
Select
one of five Availability values
Yes, No,/Draft Mode, Blocked, Final, Withdrawn.