What this category's data looks like
University laboratory safety grading and classification materials mainly consist of grading and classification tables, hazard source lists, and safety responsibility statements. The grading and classification table fields include laboratory name, hazard source category, level, quantity, date, and signature; the hazard source list fields include name, quantity, storage location, and responsible person; the safety responsibility statement fields include responsible person, date, signature, and receipt. The material sources are department submissions, laboratory self-inspections, and school reviews, and the update cadence is triggered by semester adjustments, newly added equipment, or rectification receipts. When entering the workflow, the grading and classification table serves as the main line of determination, the hazard source list is used to verify names and quantities, and the safety responsibility statement is used to verify dates and signatures; together, the three support the generation of multilingual terminology and the comparison draft.
Configuration and implementation checks
This step is executed by workflow nodes (user selection and branching), outputting branch directions and interaction state records. "Unified terminology glossary and comparison draft" is continued and completed by subsequent nodes according to the branch. When the user selection node is triggered, the conversation enters the interaction 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 |
|---|---|---|
| Grading and classification table | Whether the laboratory name, hazard source category, level, quantity, date, and signature are consistent with the hazard source list | Check the options and branch connections one by one in the node, reference variables, and run a trial once |
| Hazard source list | Whether the name, quantity, and date of the same record match the grading and classification table | Trigger a user selection node once and check the node status in the run record |
| Safety responsibility statement | Whether the responsible person, date, signature, and receipt are complete and the versions are in sync | Reference nodeId in a subsequent node and run a trial once to confirm that the selection result variable has been passed |
| Unified terminology glossary and comparison draft | Whether the same term is written consistently throughout and the translated name can refer back to the source text | Sample three terms to check whether their writing is consistent throughout, and verify the branch direction record |
Three common errors
- Symptom: The name, quantity, and date of the same record do not match between the grading and classification table and the hazard source list. Cause: The two materials are maintained by different personnel, and there is no unified terminology glossary and comparison draft.
- Symptom: The safety responsibility statement lacks a signature or receipt, and the version is not in sync. Cause: After the material was updated, re-verification was not triggered, and the old version is still in circulation.
- Symptom: After selecting an option, the default branch is still taken, and the process stops after the interaction is completed. Cause: The options and branch connections were not checked one by one, and the selection result variable was not passed to subsequent nodes.
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 check whether variables, nodeId, and the selection result variable have been passed to subsequent nodes.
Business testing: sample three terms to check whether their writing is consistent throughout, and refer back to the source text to confirm that the translated names are correct.
- Check the options and branch connections one by one in the node, trigger a user selection node once, and check the node status in the run record.
- Reference the selection result variable in a subsequent node and run a trial once to confirm that the branch direction and interaction state records are complete.