AUTO_COMPLETE_LAB_BATCH_JOBS
BOOLEAN
When the last sample in a laboratory batch job achieves a Workflow Status of Completed, or another end-state like Listed Not Received, Insufficient Sample, Not Analysed or No Result, and a cascade is being performed to determine the job's Workflow Status, then:
- If checked (default on deploy) and the AUTO_VALIDATE_LAB_BATCH_SAMPLES application preference is checked, then the job's Workflow Status becomes Completed if it is not already completed, and the job's Validated Date is stamped if it is not already stamped. When a laboratory batch job's Validated Date is stamped, the cascade up occurs in each production job for the related sample scheme analytes.
- If checked (default on deploy)and the AUTO_VALIDATE_LAB_BATCH_SAMPLES application preference is cleared, then the job's Workflow Status becomes Completed if it is not already completed, but the job's Validated Date is not stamped (such that the job needs to be validated manually).
- If cleared (default if missing) and the AUTO_VALIDATE_LAB_BATCH_SAMPLES application preference is checked, then the job's Workflow Status becomes Released if it is not already released, and does not proceed to Completed, and the job's Validated Date is not stamped (such that the job needs to be completed manually, but as soon as it becomes completed then it is validated automatically).
- If cleared (default if missing) and the AUTO_VALIDATE_LAB_BATCH_SAMPLES application preference is cleared, then the job's Workflow Status becomes Released if it is not already released, but the job does proceed to Completed, and the job's Validated Date is not stamped (such that the job needs manual completion and validation).
Typically the preference is not set at role or user level.
