Maintaining Job Stakeholders

• Maintaining Job Stakeholders
  • Overview
    • Job Stakeholder Scope
  • Process
    • Maintaining Report Stakeholders for a Job
      • Active State
      • Report Stakeholder Identification and Report Grouping
      • Report Stakeholder Target Audience
      • Scope Type
      • Report Template
      • Report File Output
      • Locale

Overview

A job stakeholder is a client or user who is interested in the job's analytical results. A job stakeholder can be the submitting client, or another client with a vested interest in the job, or a user in the laboratory.

A report request of type certificate can be created for each job stakeholder. Each job stakeholder is associated with a client-project-contact where the project and contact are optional, or with a laboratory user.

When a report request for a certificate report is created for a job, the job stakeholder's client becomes the report request's client, and the rest of the details in the job stakeholder is used to create a report entity within the report request. Also, all reportable samples, for all reportable schemes and analytes, are added to the report request. Certificate reports are then generated from the report request.

Job Stakeholder Scope

Job stakeholders are scoped by their parent job. A job can contain multiple job stakeholders. Each job stakeholder can contain separate tests to report different components of the job.

Process

Maintaining Report Stakeholders for a Job

Job report stakeholders are used to create report requests (non-paperwork and labels) for a job. The report stakeholders are defined in the CCREGN—Job application and used to create report requests in the CCRPTR—Report Request application.

The system can be configured to create job stakeholders automatically when the job is created. Refer to Conditions for Auto-creation of a Job Stakeholder.

Upon maintaining job stakeholders.

Upon maintaining job stakeholders:

• The event is audited. Refer to Reviewing Operational Data Audits.

Maintain job stakeholders

Active State

A report stakeholder's Is Active indicates whether the report stakeholder can be used to create a report request.

Report Stakeholder Identification and Report Grouping

A report stakeholder's Name, Description and Category Code indicate the purpose of the report stakeholder.

A report request with one report is created for each job stakeholder, except where the job stakeholder is linked to a Category Code, in which case, all job stakeholders with the same Category Code are placed into the same report request as separate report request reports.

Job stakeholders with the same Category Code must have the same Client Code, Contact Code and User Code. This does not apply if the Category Code is empty.

Report Stakeholder Target Audience

A report stakeholder must either have a Client Code and optional Contact Code for external reporting, or a User Code for internal reporting.

Scope Type

A job stakeholder's Scope Type is set to one of the following uses:

• Report—The target report is a certificate report.
• Other—The target report is a non-certificate report.

Report Template

A job stakeholder's Report Template Code defines the template used to generate the primary target report.

If the file name is not unique, that is, a file already exists in the report repository with the same name (check this by Maintaining Reports in the Report Repository), then there can be issues downloading the file that you think you have created.

A default report template can be specified for individual clients, cost centres or the laboratory. This prevents the need to select a report template each time a job stakeholder is created. A job stakeholder's Report Template Code defaults to the client's Report Template if it is defined, otherwise to the cost centre's Report Template if it is defined, otherwise to the laboratory's Report Template if it is defined, in this order.

Refer to Maintaining Clients to configure a report template for a client.

Refer to Maintaining Cost Centres to configure a report template for a cost centre.

Refer to Maintaining Laboratories to configure a default report template for a laboratory.

Report File Output

A job stakeholder's File Name or File Name Syntax Code defines the explicit name, or syntax used to generate the name, of the output file. These details are passed to the report request when it is created from the job stakeholder. A default suffix is only applied to those reports where no extension is specified by the report request.

Locale

A report stakeholder's Language defines the language in which text is pulled out of they system for the report.

A default language is applied to job stakeholders where the DEFAULT_REPORT_LANGUAGE application preference is defined and contains a Language. Where this preference is not defined or contains an invalid language, then the job stakeholder's Language Code defaults to EN_AU (Australian English).