| Property Name
|
Description
|
| Sample Creation Policy |
Determines the Sample creation logic for creating a Batch.
| Value | Description | | Using Product | Samples are created depending on the Batch Sample
Count and Sample Template column values of the Product used in the
Batch. See the Examples below. | | Using Sampling Plan | Samples are created as defined in the Sampling Plan
that is applied to the Batch. The Sampling Plan is determined by matching
the Product/Supplier combination, i.e., the Product Variant applicable
to the Batch. See the Examples below. | | Using Both | Both of the above are implemented. If you have defined
both a Product Batch Sample Count (with associated Tests and Specifications)
AND a Sampling Plan, Samples will be created based on the Product
and the Sampling Plan. However, any Tests and Specifications defined
for the Product will not be applied to the Samples created by the
Sampling Plan (and vice-versa). See the Examples below. | | None | No Samples are created during Batch creation. |
Examples Assume the following starting conditions: | Product or Sampling Plan | Test Method | Specification | Sample creation rule | Comment | | Product Prod1 | TM1 | Spec1 | Batch Sample Count: 2 ; Template: Finished | Batch Sample Count is mandatory to create Samples,
but Template is not. | | Sampling Plan SP1 | TM2 | Spec2 | Count Rule and Template of the applied Level
(determined by the Level Rule of the Product Variant Rule) | Count Rule determines the number of Samples that will
be created (assume it is 3).
Template is mandatory. |
If "Sample Creation Policy" is set to "Using Product": | Samples | Test Method | Specification | Comment | 2 Samples with Product Prod1.
Assume the SampleIds are S1 and S2. | TM1 | Spec1 | Only 2 Samples will be created, and only TM1 and Spec1
will be associated with those Samples.
Note that TM2 and Spec2 will not be associated with S1 and S2. |
If "Sample Creation Policy" is set to "Using Sampling
Plan": | Samples | Test Method | Specification | Comment | 3 Samples per Sampling Plan SP1.
Assume the SampleIds are S3, S4 and S5. | TM2 | Spec2 | Only 3 Samples will be created, and only TM2 and Spec2
will be associated with those Samples.
Note that TM1 and Spec1 will not be associated with S3, S4 and S5. |
If "Sample Creation Policy" is set to "Using Both": | Samples | Test Method | Specification | Comment | 2 Samples with Product Prod1.
Assume the SampleIds are S1 and S2. | TM1 | Spec1 | 2 Samples will be created, and only TM1 and Spec1
will be associated with S1 and S2. | 3 Samples per Sampling Plan SP1.
Assume the SampleIds are S3, S4 and S5. | TM2 | Spec2 | 3 different Samples will be created, and only TM2
and Spec2 will be associated with S3, S4 and S5. |
Note that Test Methods and Specifications associated with the Product
will never be added to the Samples that are created from a Sampling Plan
(and vice-versa). |
| Add Product Specifications
to Sampling Plan Samples |
Determines whether or not Product Specifications are copied
to Sampling Plan Samples.
| Value | Decription | | Yes | All Specifications associated with the Product are
copied to Samples that are created using a Sampling Plan. | | No | All Specifications associated with the Product are
not copied to Samples that are created using a Sampling Plan. |
|
Synchronize Batch Status
to Sample Workflow |
Determines whether or not the Batch Life Cycle is linked
to the Sample Life Cycle.
| Value | Decription | | Yes | Ensures that the automated Batch Life Cycle functionality
is used during Batch creation. Whenever a Batch is created, Samples
are automatically generated based on the Policy. As testing progresses
for the Samples, the Batch Life Cycle passes through the Initial,
Received, Active, Pending Release, Released, Rejected, and Preliminary
Release states as required. | | No | Existing functionality is retained while creating
Batches and Samples. In other words, Batch Status is not affected
by changes in Sample Status. |
|
| Synchronize Request Status
to Sample Workflow |
Determines whether or not the Request Life Cycle is linked
to the Sample Life Cycle.
| Value | Decription | | Yes | Ensures that the automated Request Life Cycle functionality
is used during Request creation. Whenever a Request is created, Samples
are automatically generated based on the Policy. As testing progresses
for the Samples, the Request Life Cycle passes through the Initial,
Received, Open, Completed, and Released states as required. | | No | Existing functionality is retained while creating
Requests and Samples. In other words, Request Status is not affected
by changes in Sample Status. |
|
| Prod Variant Rule Level Denoting
Skip Batch |
Determines which Batch is eligible for direct Approval,
i.e., the intermediate steps of the Batch Life Cycle are skipped.
Note that the Batch Level is determined while applying the Sampling Plan.
The Batch Level must be the same as the value of this property in order
to qualify as a skipped Batch. |
| Honor Sample Receive Flags |
Determines whether or not Sample status is based on the
AutoReceive flag.
| Value | Description | | Yes | Ensures that Sample status is not derived from the
Template status. Sample status would is set to "Received" if the AutoReceive
flag is checked. Otherwise, Sample status remains "Initial". | | No | Existing functionality is retained while creating
or editing a Sample. |
|
| Maximum Split Batch Count |
Enter a number indicating the maximum number of Batches
that can be created when splitting a Batch. |
| Synchronize Batch Release to Batch Stage |
Determines whether or not the Batch Life Cycle is linked
to the Stage Life Cycle.
| Value | Decription | | Yes | All Batch Stages must be Approved before a Batch can
be Released. | | No | Batch Status is not affected by Stage Life Cycle. | | Allow Rejected Stage | Allows a Batch to be Released with Stages that have
been Rejected. Note that this requires all Stages to be Released,
Rejected, or Cancelled. |
|
| SamplingPlan Version to be used For Adhoc
Samples |
Determines Which Sampling Plan to use during Sample creation.
| Value | Description | | Force Logged Version | Sampling Plan Version of the Batch is used to create
Samples | | Force Current Version | Current version of the Sampling Plan is used to create
Samples. | | Allow Selection | The option is given to choose Logged Version or Current
Version. |
|
| Release Batches with Open Incidents |
Determines whether or not to allow Batches to Finish when
Open Incidents exist.
| Value | Description | | Block | Prevents the Batch from Finishing when there are open
Incidents for the Batch and its Samples. | | Warn | Confirm whether or not to proceed with Finishing the
Batch when open Incidents are found. | | Allow | Batch will continue to Finished whether or not there
are open Incidents. |
|
| Release Batch Stages with Open Incidents |
Determines whether or not to allow Batch Stages to Finish
when Open Incidents exist.
| Value | Description | | Block | Prevents the Batch from Finishing when there are open
Incidents for the Batch and its Samples. | | Warn | Confirm whether or not to proceed with Finishing the
Batch when open Incidents are found. | | Allow | Batch Stages will continue to Finished whether or
not there are open Incidents. |
|
| Review Samples with Open Incidents |
Determines how to handle Samples when Open Incidents exist.
| Value | Description | | Block | Prevents the Sample from being Reviewed when there
are open Incidents. | | Warn | Confirm whether or not to proceed with Sample Review
when open Incidents are found. | | Allow | Samples will continue to Reviewed whether or not there
are open Incidents. |
|
| Release Request with Open Incidents |
Determines whether or not the Request can go to Approval
if the Request or its Samples have any Open Incidents.
| Value | Description | | Block | Prevents the Request from going to Approval if the
Request or its Samples have any Open Incidents. | | Warn | Confirm whether or not to send the Request to Approval
when open Incidents are found. | | Allow | Requests will continue to be finished whether or not
there are open Incidents. |
|
| Process Request Sample Asynchronously |
Whether or not to add associated Tests or Specifications to Request Samples asynchronously (in the background).
| Value | Description | | Yes | Any Tests or Specifications associated with Request Items are copied to Request Samples asynchronously (background process). Note that when Tests and Specifications are to be copied to a large number of Request Samples, it may take some time for the Tests and Specifications to be applied. | | No | Tests and Specifications are added and applied to the Request Sample synchronously. Any Tests and Specifications are added and applied immediately upon creation of the Request Sample. |
|
| Release Batch |
Determines if a Batch can be Released when its Parent Batch
is not Released. This lets you build a Genealogy for unsuccessfully Released
Batches (such as Batches with Status of "Rejected" and Disposition
of "Fail"), and allows unsuccessfully Released Batches to be linked
(Parent-to-Child or Child-to-Parent).
| Value | Description | | Regardless If Parent Batch Provided | Allows Batches to be Released without having to identify
the parent Batches. | | Regardless of Parent Batch State | Allows a Batch to be Released whether or not its Parent
Batch is Released. | | Only if Parent Batch is Released | Allows a Batch to be Released only when its Parent
Batch is Released. |
|
| Allow Any Change to Child Sample |
Determines whether or not child Samples can be managed when their parent Batch, BatchStage, or Request has been Released or Rejected (when Approvals are required and when not).
Using a Batch as an example: Typically, once a Batch has been Released you can no longer add new or edit its associated (child) Samples without Un Releasing the Batch. You may however want the ability to make changes to these child Samples even when Approvals had been required. In this case, choose to set
"For Released Batch (With Approvals)" to "Yes". Whether the Batch was manually or automatically Released, the child Samples can be managed. When a parent Batch is automatically released (and is not associated with an Approval Type) and "For Released Batch
(Without Approvals)" is set to "Yes", the application will recognize that the parent Batch was Auto Released, thus permitting Sample
addition/editing. This logic can be defined for BatchStages and Requests. | Option | Description | | For Released Batch (With Approvals) | When "Yes" Samples can be added to (or
edited in) a Released Batch that is associated with an Approval Type.
Sample Status can transition to "Disposed" even if this
property is set to "No". | | For Released Batch Stage (With Approvals) | When "Yes" Samples can be added to (or
edited in) a Released Batch Stage that is associated with an Approval
Type. | | For Released Request (With Approvals) | When "Yes" Samples can be added to (or
edited in) a Released Request that is associated with an Approval
Type. | | For Released Batch (Without Approvals) | When "Yes" Samples can be added to (or
edited in) a Batch that is Auto Released (since it is not associated
with an Approval Type).
Sample Status can transition to "Disposed"
even if this property is set to "No". | | For Released Batch Stage (Without Approvals) | When "Yes" Samples can be added to (or
edited in) a Batch Stage that is Auto Released (since it is not associated
with an Approval Type). | | For Released Request (Without Approvals) | When "Yes" Samples can be edited in a Request
that is Auto Released (since it is not associated with an Approval
Type). | | For Rejected Batch | When "Yes" Samples can be edited in a Batch
that has been Rejected. | | For Rejected Batch Stage | When "Yes" Samples can be edited in a Batch
Stage that has been Rejected. | | For Rejected Request | When "Yes" Samples can be edited in a Request
that has been Rejected. |
When set to "No", child Samples can not be managed once the Batch, BatchStage or Request has been Released (unless unreleased). |
| Cancel Action Behavior |
This option lets you determine what happens to Child Samples
when you Cancel a parent Batch, Batch Stage, Request or Sample.
| Value | Description | | Do Not Cancel Children | Cancels only the parent. The status of any Child Samples,
Tests and Data Sets does not change. | | Cancel All Children | Cancels the parent, all associated Samples, and Tests/Data
Sets on the Sample. | | Cancel Incomplete Children | Cancels the parent, associated Samples with a status
of Initial, InProgress or Received, and Tests/Data Sets on Samples
that are not Completed. |
The following tables describe the results of Canceling each type of parent
specifically: | If you choose... | Then... | | Do Not Cancel Children | Only the Batch is canceled. The status of the Batch
Stages, Samples, Tests and Data Sets does not change. | | Cancel All Children | The Batch, Batch Stage, and Samples on the Batch and
Batch Stage are canceled. Any Tests/Data Sets on the Sample are also
canceled. | | Cancel Incomplete Children | The Batch, Batch Stages with a status of Initial and
InProgress, and Samples on the Batch (and Batch Stages) with a status
of Initial, InProgress or Received are canceled. Any Tests/Data Sets
on Samples that are not Completed are also canceled. |
| If you choose... | Then... | | Do Not Cancel Children | Only the Batch Stage is canceled. The status of the
Child Samples, Tests and Data Sets does not change. | | Cancel All Children | The Batch Stage, Samples on the Batch Stage, and any
Tests/Data Sets on the Sample are canceled. | | Cancel Incomplete Children | The Batch Stage, and Samples on the Batch Stage with
a status of Initial, InProgress or Received are canceled. Any Tests/Data
Sets on Samples that are not Completed are also canceled. |
| If you choose... | Then... | | Do Not Cancel Children | Only the Request is canceled. The status of associated
Child Samples, Tests and Data Sets does not change. | | Cancel All Children | The Request, Samples associated with the Request,
and any Tests/Data Sets on the Sample are canceled. | | Cancel Incomplete Children | The Request and Samples on the Request with a status
of Initial, InProgress or Received are canceled. Any Tests/Data Sets
on Samples that are not Completed are also canceled. |
The Cancel Action Behavior option applies to Submission Requests only. | If you choose... | Then... | | Do Not Cancel Children | Only the Sample is canceled. | | Cancel All Children | The Sample, Tests (with their Data Sets) on the Sample,
and Data Sets on the Sample are canceled. | | Cancel Incomplete Children | The Sample, Tests that are not Completed on the Sample
(and their Data Sets that are not Completed), and Data Sets that are
not Completed on the Sample are canceled. |
|
| Sample Due Date Offset Column |
Specify which Date Column to use when calculating the Due
Date. If not specified, Due Date is calculated based on the Sample's received
date. |
| SDIWorkitem Due Date Offset Column |
Specify whether an sdiworkitem date column or a Sample date
column (cannot be a moddt) is used when calculating the Workitem due Date.
If not specified, the default is Workitem Created date. |
| Match SDIWorkitem Due Date to Sample |
Determines whether or not to change the SDIWorkitem Due
Date to the Sample Due Date if it falls later than the Sample Due Date.
Choose Yes to allow LabVantage to change the Due Date to match the Sample
Due Date. |
| Copy Site from Referenced SDI to Sample |
This can be used to maintain the order in which referenced
SDIs will be searched and copy the Site to the Sample from the first referenced
SDI available with a Site Id. This allows changing the copy down order,
introducing a new foreign key link, and disabling a link if required.
This requires familiarity with Department hierarchies and relevant copy-down
of Master Data. See Departments
→ Master Data Copy-Down → Configuring Foreign Key Order when
Copying Sites from Referenced SDIs to Samples. | Property | Description | | Column (Referenced Column Id) | Column Id referenced by the Sample. | | Turn Off | "No" (default) copies the Site from the
referenced SDI. "Yes" disables copying. |
|
| Batch Count nth Level Rule is used for First Batch of the Level |
When "Yes" the ProductVariant BatchCount nth Level Rule will always Pass for the First Batch of the Level. The default is "Yes".
For example, if the rule is "Set Level to Full for every 3rd item otherwise set level to Reduced", when this property is set to "Yes" the level of the first Batch created will be "Full" as the first Batch will always pass the rule. If you prefer that the first Batch be Reduced, 2nd should be Reduced and 3rd should be Full, set this property to "No". |