PARCreport Summary and Overview

This information is specific to the latest release of PARCview:

7.2.x

PARCReports are SQL-based reports that can be viewed from PARCview or generated and emailed by PARCTask. PARCReport Designer is used to build the PARCReport.

PARCReport Designer can be accessed from the Displays tab in PARCview. The designer will allow you to create a PARCReport display which can be viewed in PARCView.

PARCSecurity Permissions

PARCReport has two related security permissions.

Launch Report Designer: Grants access to the PARCReport Designer application.

PARCReport configuration: Enables users to enter Designer mode in PARCReport displays.

Configuration

PARCReports are configured primarily from the PARCReport Designer.

Creating a PARCReport will have two primary configuration steps. The first step is to select the source of data, the fields that will be included in the report, and create a query to return these fields from the data source. The second step is to create the layout, style, and title for the report from the fields that are returned.

Ad-hoc parameter configuration can be added to a PARCReport to change which data is retrieved by the PARCReport.

Log Files

PARCMessage is a build in error monitoring software. It creates an ongoing log of errors generated from PARCView on the specific computer where PARCMessage is running.

PARCReport errors will be stored in the PARCView folder on the client where the report is being generated: ...\Capstone\PARCview\LogFiles

Required Server Applications

PARCReport does not require any server application but is usually run by PARCTask to automate report generation.