What this category's data looks like
University laboratory safety grading and classification involves three types of materials: the laboratory grading and classification table, the hazard source list, and the safety responsibility statement. Sources are departmental submissions, asset office consolidation, and safety office review. The grading and classification table is classified by room number, hazard source category, and risk level; the hazard source list records name, quantity, storage location, and control measures; the safety responsibility statement contains the responsible person, signature, and receipt date. The update rhythm is triggered by changes in experimental projects, equipment additions or removals, and personnel adjustments, usually with a centralized revision once per semester, and temporary changes are added as they occur. After the three types of materials enter the workflow, their roles differ: the grading and classification table serves as the main grading file, the hazard source list serves as the grading basis and quantity verification draft, and the safety responsibility statement serves as the responsibility anchor and signature receipt evidence. The fields of the three cross-reference each other, and room number, hazard source name, quantity, date, and signature must be consistent; any change will affect the versions of the other materials.
Configuration and implementation checks
This step is executed by workflow nodes (user selection and branching), outputting branch direction and interaction state records. The "version ledger and change records" are continued and completed by subsequent nodes according to the branch. When a node is triggered, the conversation enters an interactive state and records the workflow state; after the user completes the selection, execution continues along the branch corresponding to the selected option.
| Object | Check | Verification action |
|---|---|---|
| Laboratory grading and classification table | Whether the room number, hazard source category, risk level, and effective date are consistent with the hazard source list, and whether the signature field is complete | Check the options and branch connections one by one in the node, run a trial and view the node status in the run record, and use nodeId to locate the branch |
| Hazard source list | Whether the same hazard source name, quantity, and storage location match in the two materials, and whether the version number is synchronized | Reference the selection result variable in variables in a subsequent node and run a trial once, and check the quantity and date fields |
| Safety responsibility statement | Whether the responsible person, signature, and receipt date are complete, and whether it references the current version of the grading and classification table | Trigger an interaction once, view the node status in the run record, and confirm that the signature receipt is updated with the version |
| Version ledger and change records | Whether the current version is unique, whether old versions are traceable, and whether references are updated synchronously | After changing one piece of content, run a trial and check whether the version number and number of references change synchronously |
Three common errors
- Symptom: The name or quantity of the same hazard source does not match in the two materials. Cause: Each was revised separately, not synchronized through the same branch, and the versions were not synchronized.
- Symptom: The grading and classification table has been versioned, but the safety responsibility statement still references the old version's date and signature. Cause: The reference was not updated with the branch, and the old version was not archived for traceability.
- Symptom: The safety responsibility statement lacks a signature or receipt, but the ledger records it as completed. Cause: After the interaction was completed, the receipt was not checked, and the process stopped without continuing.
How to verify the setup
Acceptance of this feature: run trials for each option one by one, check the branch direction and interaction state in the run record, confirm that each option corresponds to one branch, and that the selection result variable has been passed to subsequent nodes.
Business test: change one piece of content and see whether the version number and references are updated synchronously.
- Check the options and branch connections one by one in the node, trigger once and view the node status in the run record.
- Reference
variablesin a subsequent node and run a trial once, and usenodeIdto locate the branch direction and interaction state record.