What this category's data looks like
This page addresses the university laboratory safety grading and classification scenario, covering three types of materials: the laboratory grading and classification table, the hazard source list, and the safety responsibility statement. The grading and classification table records risk levels, hazard source categories, and control tiers by room and experiment type; the hazard source list records names, quantities, storage locations, and responsible positions by entry; the safety responsibility statement records scope of duties, signatures, and dates by position and personnel. Material sources are departmental submissions, laboratory self-inspections, and functional department consolidation, with update cadence triggered by semesters, personnel adjustments, and equipment changes. When entering this function, the grading and classification table provides the grading basis and room attribution, the hazard source list provides the entry-level verification draft, and the safety responsibility statement provides the responsible persons and sign-off recipients. Together, the three support a signable material draft and handover record; only when fields are complete, responsible persons are clear, and versions and dates are consistent can it proceed to the next step of sign-off.
Configuration and implementation checks
This step is executed by workflow nodes (user selection and branching), outputting branch directions and interaction state records. The "signable material draft and handover record" is completed by subsequent nodes continuing execution along the branch. When a node is triggered, the conversation enters an interaction state and records the workflow state; after the user completes the selection, execution continues along the branch corresponding to the chosen option.
| Object | Check | Verification action |
|---|---|---|
| Laboratory grading and classification table | Whether the room name, risk level, hazard source category, and effective date in the grading and classification table correspond entry by entry with the hazard source list, and whether the signature field lands on a responsible position | Compare the names, quantities, and dates of the two materials entry by entry, check signatures and version numbers, and after recording missing items, roll back for supplementary entry |
| Hazard source list | Whether the name, quantity, storage location, and responsible position of the list entries are consistent across the two materials, and whether versions and dates are synchronized | Extract fields by entry and cross-check against the grading and classification table and the safety responsibility statement, and check the values of the referenced variable variables and the node nodeId |
| Safety responsibility statement | Whether the position, personnel, scope of duties, and signature date in the responsibility statement are consistent with the responsible persons in the grading and classification table and the hazard source list | Check whether signatures and receipts are complete, compare versions and dates, and after confirming the responsible person is clear, hand over to the next step for sign-off |
| Handover record | Whether the sign-off recipient, sign-off date, and material version in the handover record are consistent with the three materials, and whether the receipt is retained | Draft one according to the template and complete one handover, check whether missing items are blocked, and check the branch direction and interaction state |
Three common errors
- Symptom: The name, quantity, and date of the same hazard source do not match across the two materials. Cause: The grading and classification table and the hazard source list are maintained separately, lacking entry-level cross-checking and version synchronization.
- Symptom: Material versions are not synchronized, and an old version of the responsibility statement is still referenced. Cause: Version numbers and effective dates are not updated with personnel adjustments, and version consistency is not checked during handover.
- Symptom: Signatures or receipts are missing, and the handover record cannot be signed off. Cause: Responsible positions are not assigned to specific personnel, and the sign-off step does not validate signature and receipt fields.
How to verify the setup
This function's acceptance: try running each option one by one, check the branch directions and interaction states in the run records, and confirm that options and branch connections are consistent, that the selection result variable variables has been passed to subsequent nodes, and that the node nodeId state is recorded.
Business test: draft one according to the template and complete one handover, and see whether missing items are blocked.
- In the node, check options and branch connections one by one, and after triggering once, view the node state and branch direction in the run records.
- Reference the selection result variable in a subsequent node and run it once, and check whether the branch direction and interaction state records are consistent.