Update Samples

From Commander4j
Revision as of 12:01, 1 April 2026 by Dgarratt (talk | contribs) (Updated by push_wiki.py)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)

Update Samples is the screen in Commander4j's Quality Management module where test results are entered against collected samples. It is the day-to-day data entry tool for laboratory technicians and quality operators.

Overview

The screen displays samples grouped by Process Order and Activity. For each sample, a column is shown for every test defined in the Dictionary for that inspection and activity. Operators enter results directly into the table cells.

Selecting Samples to Update

The operator first selects a Process Order. The system retrieves the associated material, inspection, and available activities. The operator then selects an Activity from the dropdown.

The screen then loads:

  • An index panel (left side) listing all Sample IDs that have been created for this Process Order, Inspection, and Activity.
  • A results grid (right side) with one column per test defined in the Dictionary for this inspection and activity.

The two panels scroll together — selecting a row in one highlights the corresponding row in the other.

Entering Results

Operators click on a cell in the results grid to enter or edit a result. The input method depends on the test's data type as defined in the Dictionary:

Data Type Input Method
String Free text entry
Numeric Numeric keyboard input; non-numeric values are rejected
List Dropdown selection from the options defined in the associated Select List

Results are saved to the database as the operator moves between cells.

Applying Default Values

The Defaults button applies pre-configured default values from the Dictionary to any cells that are currently empty. This is useful when most results for a sample are expected to be within a standard range and only exceptions need to be changed.

The defaults function checks a configurable reference test (set by the system key QM_RESULTS_TEST_DEFAULTS); if that test already has a value for a sample, default values from the dictionary are copied into the remaining empty cells for that sample.

Editing Sample Metadata

Double-clicking a sample row, or using the Edit button, opens the Sample Record screen for that sample. This allows the User Data fields and sample date to be corrected without leaving the results workflow.

Database Tables

Results are stored in APP_QM_RESULT, with one row per sample per test. The screen reads test definitions from APP_QM_DICTIONARY and sample records from APP_QM_SAMPLE.

Relationship to Other Screens

Step Screen
1. Define tests Dictionary
2. Configure inspections Inspections
3. Create samples and print labels Quality Control Sample
4. Enter test results Update Samples (this screen)
5. Review and report on results Results Analysis and Reporting

See also: Inspections, Dictionary, Quality Control Sample, Results Analysis and Reporting