V5 Report wizard customization — How to restrict available DataSource classes

In the DataSource step of the V5 Report Wizard, the user is asked to select a class (or class group) as the source of instances to include in the report.

By default, this step presents one of six lists of classes.

(Classes are listed by name or by Short Description, depending on a user choice in the Start step.)

List Name	reportCategory	Contents
Rules	Rules	All rule types, plus the database view accessed by the Data-Rules-Summary class.
Monitor Assignments	AssignmentMonitoring	Concrete classes derived from the Assign- base class.
Monitor Processes	WorkMonitoring	Work groups and work types available to this user.
Analyze Quality	WorkAnalysis	Work groups and work types available to this user.
Analyze Performance	PerformanceAnalysis	History- classes for the work groups available to this user
Data	Data	Concrete classes derived from the Data- base class.
System	System	Concrete classes derived from the System-. Log, and Index- base classes, plus selected History- classes.

You can customize these lists by overriding a standard activity. For example, you can prevent Report Wizard users from reporting on a specific class of work items, or a specific class of assignments.

Procedure

To control the DataSource display of classes:

1. Open the standard activity Rule-Obj-Report.getClassesForReportWizard. Save this activity in an application RuleSet version, preserving the exact rule name. (All three steps of this sample activity are comments.)
2. Modify your activity as desired. The reportCategory input parameter has one of the seven values listed in the above table. (Report category values are defined by field value rules where the Applies To key part is Rule-Obj-Report-.) Make your activity produce a Code-Pega-List page with embedded pxResults() pages each containing two facts about classes to be listed: pyClassName (the class name) and pyLabel (the Short Description).
3. Your activity can construct a list of classes by executing a list view rule, by explicitly creating the individual pxResults() pages, or any other means.
4. Save the activity. Test.

Note

The customizations described here affect only the Report Wizard experience. They do not alter the contents of a list view or summary view rule created with the Report Wizard.

About the Report wizard