Summary Views
Completing the New or Save As form

Field

Description

Select Summary View from the Reports category.

Enter a class for this summary view rule. Choose:

• A concrete class to report only on instances of that class, stored as rows in a database table.
• An abstract class that is parent of concrete classes, to define a rule that at runtime can report on instances of a single class derived from the abstract class. The activity referenced in the Content tab must accept, as an input parameter, a concrete class equal to or derived from the class you enter here.
• A concrete class that corresponds to a view of the PegaRULES database, to report on the rows of that view.

If you are creating a summary view rule to report on work objects, choose carefully whether you want to save the rule in an implementation class and RuleSet, or in a framework class and RuleSet. At runtime, summary view rules with a framework class as the Applies To class can automatically report on work objects in the associated implementation class. (You can create both kinds of work classes with the Enterprise Application Accelerator.) To enable this feature, select the Report on Descendant Class Instances option on the Contents tab.

The classes you can enter here may depend on the RuleSet you select. On the Restrictions tab of the Class form, a class rule may limit rules applying to that class to belong to one of an explicit list of RuleSets.

Identify this summary view rule with a purpose that is a valid identifier. Begin the Purpose with a letter and use only letters and digits.

In contrast to most rule names, you cannot use a dash (hyphen) in this key part.

By convention, enter the keyword ALL as the initial owner of this summary view rule. Using the  Customize   button, authorized users can later create personal copies from the ALL rule.

The Owner value of a personal summary view rule is an Operator ID name. Such personal rules are not typically moved from one Process Commander system to another.