Summary Views
|
Create a summary view rule by selecting
Summary View
from the
Reports
category.
A summary view rule has three key parts:
Field |
Description |
Applies To |
Select a class that this summary view rule applies to:
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. GRP-924 (You can create both kinds of work classes with the 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. C-356 |
View Purpose |
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. In contrast to most rule names, you cannot use a dash (hyphen) in this key part. B-2663 and KARAF 3/21/06 |
Owner |
By convention, enter the keyword 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. |
For general information about the New form, see Completing the new rule dialog box. For general information on the Save As form, see How to enter rule keys using Save As.
FFTT When searching for summary view rules, the system:
Time-qualified and circumstance-qualified rule resolution features are not available for summary view rules.