What this category's data looks like
University laboratory safety grading and classification materials mainly consist of laboratory grading and classification tables, hazard source lists, and safety responsibility statements. The sources are department submissions and archiving by the university laboratory management department, and the update cadence rolls with semesters, project changes, and rectification cycles. When the three types of materials enter workflow orchestration, their roles differ: the grading and classification table provides laboratory level and category fields, the hazard source list provides hazard source names, quantities, locations, and control measures, and the safety responsibility statement provides responsible persons, signatures, and dates. Field characteristics are concentrated in names, quantities, dates, signatures, and receipts. The same record often has mismatched names, quantities, and dates across two materials, versions are not synchronized, and signatures or receipts are missing. In deployment, operations, and application handover scenarios, these materials must serve both as the basis for branch decisions and as the verification draft for handover-ready deployment status and operation records.
Configuration and implementation checks
This step is executed by workflow nodes (user selection and branches), outputting branch directions and interaction status records. The "handover-ready deployment status and operation records" are completed by subsequent nodes continuing execution according to the branch. When the user selection node is triggered, the conversation enters an interaction state and records the workflow status. 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 name, date, and signature are consistent with the hazard source list | Check the options and branch connections one by one in the user selection node, run a trial and then view the node status in the run records, and compare the name, date, and signature in the grading and classification table with those in the hazard source list |
| Hazard source list | Whether the quantity, date, and receipt are consistent with the safety responsibility statement | Reference the selection result variable variables in subsequent nodes and run a trial once, and check the quantity, date, and receipt on the same record in the hazard source list and the safety responsibility statement |
| Safety responsibility statement | Whether signatures and receipts are complete and versions are synchronized | Check signatures and receipts item by item according to the handover form, view the run records corresponding to nodeId, and confirm items with unsynchronized versions or missing items |
| Deployment status and operation records | Whether version, connection, and task records are consistent | Check the deployment status, connection, and task records item by item, and confirm that the branch direction and interaction status records are handover-ready |
Three common errors
- Phenomenon: 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 submitted separately and are not updated in sync under the same version.
- Phenomenon: The safety responsibility statement lacks signatures or receipts, making it impossible to confirm responsibility ownership during handover. Cause: Signatures and receipts were not included in the handover form for item-by-item verification.
- Phenomenon: After selecting an option, the default branch is still followed, 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 correctly 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 status in the run records, confirm that the selection result variable variables has been passed to subsequent nodes, and check the node status corresponding to nodeId.
Business testing: Check once item by item according to the handover form, see which record is missing, and focus on checking the fields, dates, and signatures of the grading and classification table, hazard source list, and safety responsibility statement.
- In the user selection node, check the options and branch connections one by one, trigger an interaction once, and then view the node status in the run records.
- Reference the selection result variable in subsequent nodes and run a trial once, and check the deployment status, connection, and task records item by item according to the handover form.