Back Forward Summary Views
Completing the Create, Save As or Specialization form
  1. About 
  2. New 
  3. Content 
  4. Drill Down 
  5. Organize 
  6. Format 
  7. Chart 
  1. Parameters 
  2. Pages & Classes 
  3. Join 
  4. HTML 
  5. History 
  6. More... 

NOTE: As a best practice, before creating a new summary view rule, it is strongly recommended that you investigate using a report definition instead. The New form displays a message with information about that alternative.

Records can be created in various ways. You can add a brand new record to your application or copy an existing one. Existing rules can be specialized by creating a copy into a specific ruleset, against a different class or (in some cases) with a set of circumstance definitions. Data instances may be copied but do not support specialization as they are not versioned.

Based on your use case, the Create, Save As or Specialization form is used to create the record. The number of fields and available options vary by record type. Start by familiarizing yourself with the generic layout of these forms and their common fields:

This help topic then identifies the key parts and options that are applicable to the record type you are creating.

Create a summary view rule by selecting Summary View from the Reports category.

Key parts:

A summary view rule has three key parts:

Field

Description

Apply to

Select a class that this summary view rule applies to:

  • 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 items, 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 Apply to class can automatically report on work items in the associated implementation class. To enable this feature, select the Report on Descendant Class Instances option on the Contents tab.

The list of available class names may depend on the ruleset you select. Each class may restrict rules applying to that class to an explicit set of rulesets as specified on the Advanced tab of the class form.

Identifier

Enter a purpose to identify this summary view rule; the purpose must be a valid Java identifier. Begin the Purpose with a letter and use only letters and digits. See How to enter a Java identifier.

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

Owner

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 PRPC system to another.

Rule resolution

When searching for rules of this type, the system:

Time-qualified and circumstance-qualified rule resolution features are not available for this rule type.

Up About Summary View rules