This topic summarizes many new 6.2 reporting features. For an introduction to Report Browser and reporting features, see Reporting in 6.2 - Nine tutorial videos and

Webinar Archive: PegaRULES Process Commender 6.2 Reporting (September 13, 2011)

• Report scheduling and subscriptions — From the Report Browser, managers can schedule future execution of a report definition, with the output (as PDF or Excel files) sent by email, on a one-time or recurring basis.  Each time the report runs, email is sent to designated users. These users may be explicitly listed, or the scheduled report may be marked as subscribable, in which case users can subscribe and unsubscribe themselves to scheduled reports of interest.  Options include choice of output (Excel or PDF file), inclusion of the results file or a link to the results file in the generated email notifications, and error handling. Execution occurs in the background. See How to schedule reports and subscribe to scheduled reports.
• Runtime presentation of filter criteria — Optionally the report filter criteria can be presented at runtime in a display controlled by a section rule. Such sections can include instructions to the report user, more familiar labels , and an attractive layout compared to the default presentation of filter criteria.
• Reports can include data from external tables as well as data from tables in the Process Commander database.
• Optionally, report output can present the contents of a row using a section rule, providing flexibility in layout and labeling of fields. Other enhancements bring report definition rules closer to parity with features available in summary view rules.

• The Business Intelligence Exchange V2.4 (BIX) provides improved logging and error analysis. BIX allows you to extract data from your Process Commander applications into a format for easy upload into a data warehouse or other corporate database.
• New Report Definition options— These functional enhancements are new options on the rule form:
  • A Count Distinct aggregate function.
  • Frameworks support —The Report on Descendent Class Instances checkbox allows a report definition rule defined in a framework class to include, at runtime, work items that belong to an implementation class.
  • SmartInfo support.
  • Ability to suppress the display of duplicate rows.
  • Nested SQL functions - Within the Function Builder, the input parameter to a function can itself be a function, allowing users to define nested expressions.
  • The Export to PDF and Export to Excel outputs include all rows for paged reports.
  • Group headings — For list-type reports with one or more sorted columns, allows the values in one or more of the sorted columns to be displayed as a group band above each set of detail rows, conserving space on the report and providing a more attractive layout.
• Top and Bottom Ranked results — Report output can display only those rows which are ranked as the top N, or the bottom N, where N is an integer value on the Design tab and "top ranked" and "bottom ranked" are a property value (such as pxUrgencyWork in this example) or the output of an expression.
  The ranking can be evaluated across all rows, or across rows in each group of values in the sorted columns of the report. For example, your report can include only the oldest 10 open assignments for each operator.
• Reporting on external classes — When specifying columns for a report, the autocomplete list of choices includes the property names from an external class. This information is obtained from the External Mapping tab of the Class rule.
• Subscriptions to scheduled reports — Managers can subscribe to receive report outputs (by email) that have been scheduled by other managers and marked by them as subscribable.
• Subreports — A report definition rule can reference column values from the results of other report definition rules. This allows report definitions to automatically generate SQL containing constructs such as advanced SELECTs, EXISTS() and NOT EXISTS(), and HAVING clauses , but without requiring developers to configure such hand-crafted SQL. See When and how to use sub-reports in Report Definition reports.
• Reporting on framework work — As with list view reports, the Report on Descendent Classes option allows a report definition rule that applies to a framework class to report on work items that belong to a child subclass (an implementation class).
• Custom formatting of list-type report results using sections — The rows of list-type reports can be formatted using section rules created by the developer.   The section rule can replace the default tabular-style display of the row with one in which values are shown on multiple rows, and can present values using controls such as checkboxes and icons. 
• Enhanced formatting of filter criteria — Report display of filter criteria can be formatted by a section rule or can use a text caption to label criteria on the Design tab. Your application can present descriptions in language that is familiar to the user community.
• Completeness of PDF and Excel outputs — When a report from a report definition rule is exported to Excel or converted to PDF format, the paging settings (on the User Interactions tab) are ignored. The output includes rows from all pages.
• Report landing pages — Four landing pages provide access to report rules, reporting features and report status.