Registering Jobs from Template Jobs

• Registering Jobs from Template Jobs
  • Overview
  • Process
    • Auto Receiving Jobs

Overview

A template job is used to create registered jobs. Samples and tests can be optionally created in the target registered job using the sample and test definitions in the template job.

Template jobs at organisation level or laboratory level are used to create jobs at laboratory level.

Process

A source template or other job is located using the CCREGN—Job application and saved as a registered job.

Each of the following attributes must be active to be included in a template job or template sample:

• Schemes
• Specifications
• Products
• Clients
• Biofields
• Paperwork templates (such as report and invoice templates).

Upon saving a template or other job as a registered job:

• The job's Job Code is generated.

• The job's Job Name is generated, if required.

• The system validates the Job Code and Job Name (regardless of whether it was entered by the user or generated from syntax), using the CODEVALIDATION_JOBCODE and CODEVALIDATION_JOBNAME application preferences.

• The entire structure in the template job is used to build the target registered job, including the job header containing the client, project, contact, priority, etc. (but not anything date or workflow related), biofields, paperwork and label details, reporting details, invoicing details.

  Where the job is not a template job and samples are included in the copy, for each template sample representing a sample group, the sample group is expanded out to create registered samples in the target registered job, and the entire structure in the template sample is used to build the target registered samples, including sample biofields, tests, sample specifications, sample portions and sample notes.

  Field defaults differ slightly where the source job is a template job versus a production, proposal or internal job.

  The job copy includes job stakeholders, job invoices (excluding those that are credited, cancelled or rejected), job paperwork, job biofields, job notes, samples, sample biofields, tests, sample specifications, sample portions and sample notes.

  Upon copying a sample to create one or more destination samples in the destination job:

  • The sample's Client Sample Name, header details, sample biofields, specifications, notes and tests are inherited from the source sample.

    • Fields copied from a source job to destination production job
    • Fields copied from a source sample to destination production sample
  • Copying sample portions;

    • Portion Code, Portion Type, Active status, Location Code within its Location Hierarchy, Single Capacity Container Type Code, Sample Handling Code, Multiple Capacity Container Type Code, (multiple capacity) Container Name and Notes are copied from the source sample portion to the destination sample portion.

      Note: A sample portion's Scheme Codes are not included in the copy.

    • Checked in On, Checked in By, Started Date and Started By defaults to current system date-time and user, respectively.

    • If the sample handling's Duration is defined, then Due Date defaults to the current system date-time + sample handling's Duration, otherwise Due Date defaults to empty.

    Note: The sample portions for any sample that is linked to a source template sample is impacted by the sample portions on the template sample. Refer to Maintaining Sample Portions during Registration.

  • Copying composite links:

    • Conditions for Defaulting Composite Sample Links from the Source Job
  • Copying priority, received, required, possible and agreed dates:

• The destination sample scheme's Workflow Status defaults from the template sample scheme's Default Workflow Status.

• Conditions for Defaulting Job Cost Centre

• Conditions for Calculating Job and Sample Required On Date
• Clearing the Ready Date for Sample Schemes
• Conditions for Calculating Expiry and Warning Dates
• Conditions for Defaulting Gridding on Sample Scheme Analyte Copy
• Conditions for Defaulting Scheme Links from the Template Sample
• Conditions for Defaulting Precursor Scheme Relationships and Holding Time from the Sample Template
• Conditions for Defaulting Upper Sample Scheme Analytes to Not Analysed

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

• The job is opened for update. Refer to Maintaining Jobs.

Register a job from a template job

Auto Receiving Jobs

If the template job's Auto-receive Job is selected, then the target register job's Sampled On date-time is set to the current system date-time, otherwise it is left empty (and all downstream dates, that is, Required Date, Agreed Date, and Possible Date are left empty also).

The job invoice sample's Use Package Price defaults to checked.

When a job is created, the job's Workflow Status is set to Registered, its analysed date is stamped and analysed by is set to the current user.

• Conditions for Defaulting Job Received Date on Job Copy
• Conditions for Auto-activation of a Job
• Conditions for Auto-activation of Samples