ALLOW_STANDARDS_AS_SPIKES
BOOLEAN
When a QC mask member is being updated where the QC mask member's Analytical Type is Spike, then :
- If checked (default on deploy), then the Standard Code can be associated with a standard that has a QC Type of Spike or Standard, or the Standard Group Code can only be associated with a standard group that has a QC Type of Spike or Standard.
- If cleared (default if missing), then the Standard Code can only be associated with a standard that has a QC Type of Spike, or the Standard Group Code can only be associated with a standard group that has a QC Type of Spike.
When a standard or spike QC sample is being written to QC history, then:
- If checked (default on deploy), then the QC history record for the standard or spike QC sample is created with an Analytical Type of Standard.
- If cleared (default if missing), then the QC history record for the standard QC sample is created with an Analytical Type of Standard, and the QC history record for the spike QC sample is created with an Analytical Type of Spike.
Typically the preference is not set at role or user level.
