Screen flows

• OK—Proceed.
• Cancel—Cancel the action.

Fields

• Source Job Name

  The name of the source Job for the copy. Display only.

• Use Samples from Template

  Indicates whether to copy samples that have a Primary Analytical Type of Unknown from the source job to create new samples in the new job. Note that Sample Registration Sequence is recalculated for the new job.

• Use Tests from Template

• Indicates whether to copy sample schemes and job schemes from the source job to the new job. If the source job has org-scope, Tests are copied only if the org-scope scheme is enabled for the laboratory, otherwise an error message displays and the new job is not created.

• Job Type

  The type of destination job. The allowable destination job types depend upon the source job type.

  Allowable Source Job Type	Allowable Destination Job Types
  Production—A production job is a collection of samples and their tests submitted from a client, from which a certificate report of results is generated for the client.	Production (default), Internal, Proposal, Template
  Internal—An internal job is a collection of samples and tests registered for internal purposes, for example, analysis of instrument calibration.	Production, Internal (default), Proposal, Template
  Proposal—A proposal job is a collection of proposed samples and tests for a client, so that the client can be given an example of a typical report and invoice if real samples were submitted for testing.	Production, Internal, Proposal (default), Template
  Template—A template job is used to create other jobs and can contain a collection of template samples and their tests that are optionally included when creating a job from it.	Production(default), Internal, Proposal, Template
  Schedule—A schedule job is similar to a template job except that it has a registration frequency, and contains a collection of stream samples and their tests, that may be used interactively to draft a job, update the draft job content, and from that create or update a production job, or that may be used by the batch queue at the scheduled time to create or update a production job with stream samples. A stream sample is a sample of a known product that is taken a particular location in the production process, or a standard sample that is inserted into the analytical stream of samples from the production process.	Schedule (default)

  Note that laboratory batch and draft jobs cannot be used as a source nor destination job type in a job save as process.

  • A laboratory batch job is a collection of samples for common testing, gathered together to save on costs and for time efficiency of preparation and analysis.

  • A draft job is a transient job that is created interactively from a schedule job, upon which its registration details, samples and tests can be modified prior to it being enacted to create samples in a production or internal job.

• Organisation Scope

  Indicates whether this entity is available organisation-wide or laboratory-wide.

  • Checked—The entity is available to users who are logged into any laboratory within the organisation.

  • Unchecked—The entity is only available to users who are logged into the current laboratory.

  This field can be selected only if the source job type is a template job since only template jobs can have org-scope.

  Setting the job's scope upon successful creation via save as depends upon the user's security level for the CCJOB:SAVEAS resource, and upon the value of the CAN_CREATE_ORG_JOB_TEMPLATE application preference. The only possible security level for the resource is full—full.

  A user can have multiple roles, and each role can contain different rights. Any of these role-right combinations may contain the resource. If the resource does not exist across all role-right combinations for the user, then the user has no access to the resource. Otherwise the user's security level for the resource is full—full.

  The selection in this field can determine the visibility for other fields in this form, and the content of various drop-down selection lists.

• Job Name Syntax Code

  The code of the syntax used to generate the job's Job Name. Either Job Name Syntax Code or Job Name must be entered. Where the JOB_NAME_ONLY_FROM_SYNTAX application preference is checked, then the Job Name is disabled and the Job Name Syntax Code is mandatory. A syntax may be selected from the drop-down list that contains active syntaxes in scope with a Syntax Type of Job Name, as configured in the CCSNTX—Syntax application. Click the field hyperlink to display the CCSNTX—Search Syntax screen, select the appropriate value and click Select and Return to populate the field with the selected value.

  Where no Job Name is entered and the syntax is not found or the syntax is found but the syntax cannot generate a code, then an error is raised.

  Where the entered or generated job's Job Name is not unique within scope, then an error is raised.

  Where the entered or generated job's Job Name does not satisfy code validation, then an error is raised.

  Where the CODEVALIDATION_JOBNAME application preference is:

  • Defined and contains a list of visible ASCII characters, then a valid job name only contains characters from this list.

  • Not defined, then a valid job name only contains characters from the 'ABCDEFGHIJKLMNOPQRSTUVWXYZ_0123456789' character set.

• Job Name

  The name of the job. Either Job Name Syntax Code or Job Name must be entered. Where the JOB_NAME_ONLY_FROM_SYNTAX application preference is checked, then the Job Name is disabled and the Job Name Syntax Code is mandatory.

  Where the entered or generated job's Job Name is not unique within scope, then an error is raised.

  Where the entered or generated job's Job Name does not satisfy name validation, that is, if the code contains non-printable characters, then an error is raised.

• Client Code

  The code of the client associated with the job. Only applicable if the Registration Mode is New Job by Client. It is mandatory for a job to be associated with a client. A client may be selected from the drop-down list that contains active clients in scope, as configured in the CCCLNT—Client application. Click the field hyperlink to display the CCCLNT—Search Client screen, select the appropriate value and click Select and Return to populate the field with the selected value.

• Project Code

  The code of the project associated with the job. Only applicable if the Registration Mode is New Job by Client. If the MANDATORY_PROJECT application preference is checked, then it is mandatory for a job to be associated with a project. A project may be selected from the drop-down list that contains active projects for the client, as configured in the CCCLNTPROJ—Client Project application.

• Contact Code

  The code of the contact associated with the job. Only applicable if the Registration Mode is New Job by Client. If the MANDATORY_CONTACT application preference is checked, then it is mandatory for a job to be associated with a contact. A contact may be selected from the drop-down list that contains active contacts for the client, as configured in the CCCLNTCONT—Client Contact application.