Maintaining Reports for a Report Request

• Maintaining Reports for a Report Request
  • Overview
  • Creating Reports for a Report Request
  • Creating Report Request Reports automatically for a Job

Overview

A report report request produces one reportable result set of data comprising the jobs, samples and tests.

This reportable result set is used to generate as many different report outputs as are required, based on the defined report request's reports.

The destined type of output, the naming of the output, the report language and the distribution can differ from report to report.

Creating Reports for a Report Request

Report requests are created and updated using the CCPRTR—Report Request application, and a report request's reports are contained within the Reports tab. As many report request reports may be created, as required, and the Generate Report flow creates all reports defined for the report request. Each report request's Client Code is inherited from the reporting stakeholder's Client Code.

When a report is added to a report request, a Report Template Code and Language must be selected. If no template is assigned to the report request report, then no reports are generated for it. Refer to Maintaining Report Templates. The language default to the client's Locale, if one is defined, otherwise it is set to the language referenced in the DEFAULT_REPORT_LANGUAGE application preference.

A report request report's Filename Syntax Code is inherited from the report template. Alternatively, a File Name can be entered, which takes precedence over one generated from syntax. During report generation, the generated report's Report Filename is derived using the report template's Output File Name Syntax. Refer to Configure a Syntax to Generate Report File Names.

A generated report's Name and Description are inherited from the report request report's Report Name and Report Description and are used to find the report in the report repository.

A report request report's Email, Printer, Print Copies and Copy to Folder (to the folder denoted by the client's contact) details are used to distribute the generated reports. A report request report's Printer is inherited from the report template's Device Code, if one is defined, otherwise it is set to the device referenced in the CERTIFICATE_DEFAULT_DEVICE application preference setting, and if this preference is empty or inactive, then the printer is left empty. When a report request report is updated manually and the report template is not changed, then clearing of the report request report's Printer leaves the field empty upon submit.

If a report request has a Report Type of Certificate, when a report is added to the report request, then the report request report's Email defaults to true, Print Copies defaults to 0, and Copy to Folder defaults to true.

If a report request has a Report Type anything other than Certificate, when a report is added to the report request, then the report request report's Email defaults to false, Print Copies defaults to 0, and Copy to Folder defaults to false.

The process to distribute report documents by email, print or copying to folders is discussed further in Distributing Certificate Reports.

Creating Report Request Reports automatically for a Job

Where one or more rows returned from a search in the CCRPTR—Search Report Requests application are selected, when the Create Report Request grid flow is selected, then a report request with a Report Type of Certificate is generated for each related job's reporting stakeholders, as defined in the Reporting tab for each job. Each report request has one report created in it with the report request report's Report Template Code, File Syntax Code and Language inherited from the report template linked from the respective reporting stakeholder's Report Template Code.