Configuring the Status Application

Forms See also
STATREP—StatRep Form

Generating Job Reports

Overview

After the analytical process is completed, analytical reports, or certificates, are generated for jobs and sent to the client.

This process is pertinent to LIMS and laboratory managers who configure the LIMS, job report templates and reporting sessions in particular.

Process

Configuring Access to the Status Application

Ensure the StatRep.exe file is located in the folder defined by the ExeDirectory GLOBAL setting. Give users, or users with specific roles, access to the application by setting the AccessLevel STATREP program setting.. Once a user has sufficient access rights, they can run the Status application either from the Status Reports node on the CCLAS menu or directly from the CCLAS Exe folder.

To display tips to users upon start up of the Status application, enable the ShowTipOfTheDay STATREP program setting, and enter the tips, with one tip per line, in a file, place the file in a folder under the CCLAS root folder defined by the CCLASRootDirectory GLOBAL setting, then set the TipofTheDayFile STATREP program setting to the folder and file name, for example %CCLASRootDirectory%TIPS\STATREP.TIP.

To maintain the window size and position between closing and launching the Status application, set the Window STATREP program setting.

Configuring Job Status Search

To present the list-view panel with grid lines, enable the MainListViewGrid STATREP program setting.

To filter jobs for a status report based on field criteria:

To filter by client, set the ClientReportLookupColumns STATREP program setting to the columns of CLIENT details on display in the grid when report clients are filtered on the General tab using the F2 function key and a client grid displays, and set the ClientReportLookupField STATREP program setting to the field from the CLIENT table that is returned from the lookup function.

Set the MainListViewColumnn STATREP program setting to specify which columns from the PROFJOB table are presented in the Jobs grid.

Configuring Job Status Reporting

Place all job status report templates in the folder defined by the TemplateDirectorySTATREP program setting.

The DefaultTemplate STATREP program setting defines the default template for job status reports.

The DefaultViewMode STATREP program setting defines the default view mode of report generation. View none means that the job status report is not presented to the user at all, View creating shows the generation as it occurs and presents the report to the user at the end of generation, and View at end shows no generation details and only presents the job status report to the user at the end of generation.

The SummaryBand1BackgroundColour STATREP program setting defines the background colour of the client group in a job summary report spreadsheet generated in Microsoft™ Excel.

The SummaryBand2BackgroundColour STATREP program setting defines the background colour of the client project group in a job summary report spreadsheet generated in Microsoft™ Excel.

The SummaryBand3BackgroundColour STATREP program setting defines the background colour of the job group in a job summary report spreadsheet generated in Microsoft™ Excel.

Enable the SummaryExpandAll STATREP program setting so that job summary report spreadsheets generated in Microsoft™ Excel contain a detailed summary.

The SummaryFixedColumns STATREP program setting defines the number of fixed columns contained in a job summary report spreadsheet generated in Microsoft™ Excel.

Job status report details can be saved to a script for later use. Refer to Configuring Reports.

Customising Job Status Reporting

Where the StatUDF.VBS VBScript file is located in the folder defined by the ConfigDirectory GLOBAL setting and:

  • The PRepUDF1 subroutine exists within the script file, before the job status report is created in Microsoft Excel™, then it is run to perform custom logic.

  • The RepUDF2 subroutine exists within the script file, after the job status report is created in Microsoft Excel™, then it is run to perform custom logic.

  • The BeforeCrystalGenerate subroutine exists within the script file, before the job status report is generated using Crystal Reports™, then it is run to perform custom logic.

  • The DuringCrystalGenerate subroutine exists within the script file, after the clsCrystalReport object is generated but before the Crystal Report™ is actually generated, then it is run to perform custom logic.

  • The AfterCrystalGenerate subroutine exists within the script file, after the job status report is created using Crystal Reports™, then it is run to perform custom logic.