Distributing Certificate Reports

• Distributing Certificate Reports
  • Auditing Report Distribution
  • Configuring Emailing of Reports
  • Configuring Printing of Reports
  • Configuring Copying Reports to a System Folder

Certificate reports certify the results of the testing conducted on samples in a job, and are generally distributed to job stakeholders as they are generated in CCLAS, or post-generation. Stakeholders are typically the clients that have submitted the job, but may also be another client with a vested interest in the job, or a user in the laboratory.

Each certificate report generated from CCLAS is an electronic record that is recorded in the report request associated with a job, the job itself, and the CCLAS report repository. The method of distribution for the generated certificate report is specified in the report request, where a generated report can be emailed, or printed.

Once reports are generated, they need to be distributed to the job stakeholders.

A report request report can be:

• Made active for emailing
• Configured to print reports
• Made active for copying to folders.

Other laboratory operators should be able to generate reports from the report templates and requests configured for the lab, distribute reports and search for reports that are previously generated. The ability to generate and distribute certificate reports at any scope can be specified in the security settings applied to any of the roles in the system.

Report distribution occurs after report generation, or can be triggered manually. The system batch queue is used to perform the actual distribution.

To distribute a certificate report from the CCREPT—Report application, you are required to search for and view certificate reports, and then download them in order to then distribute them to job stakeholders.

To distribute a certificate report from the CCRPTR—Report Request application, you are required to open the report request by performing a search using CCRPTR—Report Request application. You must then select the certificate report to distribute from the grid in the Generated Reports tab, and click the Email Reports button to distribute the report to the job stakeholders.

Reports are printed in the order in which they are listed in the report request reports.

Auditing Report Distribution

An audit event is recorded each time a report is issued.

Configuring Emailing of Reports

By default, report request reports are made active for emailing. Note that emailing proceeds only if email details are configured on the report request.

The report request's email-to addresses defaults to the report request's client contact's email address. The report request's email CC addresses defaults to the additional report methods, where the report method type is email, configured for the report request's client contact. Refer to Maintaining Clients.

The report request's email BCC addresses defaults to the email addresses contained within the EMAIL_BCC application preference.

The report request's default email subject and message text is generated from syntax. Refer to Maintaining Report Syntaxes.

When reports are emailed, the email-from address is the email address contained within the REPORT_FROM_EMAIL_ADDRESS application preference.

Where there are multiple report files to be emailed, the EMAIL_REPORTS_SEPARATELY application preference denotes whether they is sent as one or multiple emails.

Where the reports are sent as one email, the reports are either zipped into one zip file and that zip file attached to the email, or attached to the email as separate files. This is driven by the EMAIL_ZIP_ATTACHMENTS application preference.

Configuring Printing of Reports

Report templates can optionally link to a device (for example, a printer). However, since org-scope report templates can link to org-scope devices only and devices are defined locally, then a laboratory requires a way to assign printers to report request reports without having to create local copies of report templates (just so that they can link to lab-scope devices). Where a report template does not link to a device, the CERTIFICATE_DEFAULT_DEVICE application preference is used to set the default device for a certificate report. This allows a logical and definable lab-scope device to be defined for report printing where there is no global device available for local printing.

Each printer device must be set up as a system device for printing to occur. Refer to Maintaining CCLAS Devices.

Configuring Copying Reports to a System Folder

The folders are those specified in the additional report methods, where the report method type is folder, configured for the report request's client contact. Refer to Maintaining Clients to create reporting methods for a client contact.