Flows:

• Browse—Return to the frmClient form.
• Close—Close this form.
• Save—Save form updates.
• Save as—Save the current entity as a new entity.
• Delete—Delete the current entity.
• Unlink—Unlink the job. Applicable only where a job link exists including the current job.
• Report—Generate a report from the job.

Form:

General tab:

• Client code—The code of the client who owns the job. The client code cannot be updated after creation.
• Project code—The code of the client's project associated with the job. The project code cannot be updated after creation.
• Client order no—The client order number, typically used to link a job with a client's submission, usually included by the client on the sample request sheet or notice that accompanies the samples.
• Client contact code—The contact within the client's organisation who originated the sample analysis request.
• Registered—The date-time of job registration into CCLAS.
• Registered by—The staff member who registered the job.
• Received—The date-time the job was received by the laboratory. At job registration, the received date-time defaults to the registered date-time, but may be updated via VBScript.
• Required—The date-time at which the job report is due, calculated by default using the client's priority.
• Priority—The priority is used to determine the relative priority of jobs from the client, compared to the priority of other registered jobs, to schedule sample analysis in the laboratory. 1=high, 99=low. Defaults to the client's Priority. The PriorityUnitGLOBAL setting defines the priority units.
• Product code—The code of the product associated with the job's samples, selected from the PRODUCT table.
• Cost code—The code of the cost centre associated with the job.
• Tax type—The method of calculating tax for the job:
  • NIL—No tax.
  • SCH— Tax rates are taken from the tax codes linked to each scheme.
  • CLI— Tax rates are taken from the tax codes linked to the client.
• Notes file—DOC, TXT or HTM file containing general notes about the job.
• Quote code—The code of the quote associated with the job, applied when the job is invoiced.
• Notes—Miscellaneous notes for the job, typically for inclusion on work summaries and job sheets to warn analysts of special requirements.
• Report template—The report template file used to create certificate reports for the job.
• Template job—Indicates whether the job is a template job, allowing separation of template from production jobs when using criteria to filter jobs on display in browser lists.
• Miscellaneous details—Miscellaneous details pertaining to the job.
• Last activated—The date on which the job was activated.
• Invoice client code—The code of the client that is the recipient of the job's invoice. The invoiced client may differ from the job's client, and can be from any laboratory defined in the system.
• Report client—The code of the client that is the default recipient of the job's certificate report. The report client may differ from the job's client, and can be from any laboratory defined in the system.

Clients tab:

• Client tab flows:
  • —
  • —
  • —
• Client tab form:
  • Type—The type of stakeholder client, defaults to REP only.
  • Client code—The code of the stakeholder client.
  • Contact code—The code of the contact within the stakeholder client.
  • Template file—The template file used to generate the report for the client.
  • Scheme codes—List of schemes from the job to include in the client's report.
  • Client grid—List of stakeholder clients for the job.

User fields tab:

• Script form—Script form to enter custom details for the sample.

Samples tab:

• Sample idents sub-tab:
  • Sub-tab flows:
    • Auto Idents—Generate automatic sample idents
    • —Add the sample idents to the Sample idents grid.
    • —Erase the sample idents from the Sample idents grid.
    • —Calculate the sum total of sample idents in the Sample idents grid.
  • Sample idents grid—The sample idents for the job
  • Ident type—The type of sample ident template entry.
  • Template—The format the sample ident takes, comprising fixed text and wildcards. Where wildcards are required to position the numerical fill, then up to two contiguous groups of wildcard characters are recognised. Any subsequent use of wildcard characters are taken as literal, and have no special function. The "#" wildcard type represents right-justified, padded with leading zeros. The "&" wildcard type represents right-justified, padded with leading blanks. Wildcard types must not be mixed.
  • From—The value from which to start the numerical fill for the first wildcard sequence.
  • To—The value up to which to end the numerical fill for the first wildcard sequence.
  • Step—The step used to obtain the next number in the numerical fill for the first wildcard sequence.
  • From2—The value from which to start the numerical fill for the second wildcard sequence.
  • To2—The value up to which to end the numerical fill for the second wildcard sequence.
  • Step2—The step used to obtain the next number in the numerical fill for the second wildcard sequence.
  • Block—The block of text filled into substitute "!" wildcard character, with each line of text defining one fill-cycle, so that the first line of text is inserted where the "!" wildcard character is, then the numerical portion is filled according to the defined From, To and Step, then the second line of text is inserted where the "!" wildcard character is, then the numerical portion is filled, etc.
• External idents sub-tab:
  • Same flows and fields as for the Sample idents sub-tab, except no auto-entry.
• Descriptions sub-tab:
  • Same flows and fields as for the Sample idents sub-tab, except no auto-entry.
• Product codes sub-tab:
  • Same flows and fields as for the Sample idents sub-tab, except no auto-entry.
• Grid/Sample info sub-tab:
  • Sub-tab flows:
    • Open—
    • Save—
    • Delete—
    • Scheme—
    • Multi-Scheme—
    • Mode—
    • View—
    • Fields—
    • Status—
  • Sub-tab fields:
    • Sample grid—

Schemes tab - for the combined scheme-analyte selection mode.

• Schemes tab flows:
  • Save—Save the schemes and analytes under the job.
  • Up—Move the current scheme up in relative order of job schemes under the Folder Items panel.
  • Down—Move the current scheme down in relative order of job schemes under the Folder Items panel.
  • Refresh—Load the original schemes and analytes covered by the job.
  • Add all—Toggle the adding of all analytes, or the adding of no analytes, and allowing deselection/selection of analytes after schemes are added, to the job.
  • Add procedure—Add the missing schemes and analytes from selected procedures to the job.
  • Grid—View the sample grid.
  • Update scheme—Update result records for the job scheme.
  • Update analyte—Update result records for the job scheme analyte.
• Scheme tab form:
  • Folder items—Child details for the price group schemes:
    • Selected
    • Available
  • List view—List of entities associated with the current selected node.

Schemes tab - for the default scheme-analyte selection mode:

• Schemes tab flows:
  • Add——Add a scheme to the end of job schemes and open the frmJobSchemeAdd form.
  • Open—Open the frmJobSchemeEditANA form.
  • Insert—Insert a scheme above the currently selected scheme and open the frmProcRegSchemeAdd form.
  • Move—Mode the scheme.
  • Delete—Delete the scheme from the job.
• Scheme tab form:
  • Scheme grid—List of schemes and analytes in the job.

Conc records tab

• Conc records tab flows:
  • Create record(s)
• Conc record tab fields:
  • All samples
  • Include QC
  • Update
  • User defined
  • Single sample
  • Sample type
  • Scheme code
  • Sam[ple ident
  • External ident
  • Description
  • Product code