What this category's data looks like
This page addresses the scenario of school safety hazard inspections and campus incident reporting, covering three types of materials: safety inspection checklists, hazard rectification ledgers, and emergency incident reports. Safety inspection checklists come from daily patrols and special inspections, updated weekly or per inspection, with fields including inspection item, location, date, and inspector signature; hazard rectification ledgers come from checklists being transferred for handling, updated by rectification milestone, with fields including hazard name, quantity, responsible person, deadline, and re-inspection signature; emergency incident reports come from on-site reporting, updated by incident progress, with fields including incident name, time, number of people involved, handler, and receipt. After the three types of materials enter the workflow, they respectively take on the roles of discovery, tracking, and reporting; across materials, names, quantities, dates, and signatures must remain consistent, versions must be synchronized, and missing items are intercepted by nodes.
Configuration and implementation checks
This stage is executed by workflow nodes (user selection and branching), outputting branch directions and interaction state records. "Signable material drafts and handover records" are then completed by subsequent nodes continuing execution along the branches. When the user selection 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 |
|---|---|---|
| Safety inspection checklist | Fields complete, responsible person clear, version and date consistent | Check inspection item, location, date, and inspector signature; in the node, verify options and branch connections one by one, confirming options correspond one-to-one with branches |
| Hazard rectification ledger | The name, quantity, and date of the same record match between the checklist and the ledger | Check hazard name, quantity, responsible person, deadline, and re-inspection signature; reference variables in subsequent nodes and run a trial once, confirming the selection result variable has been passed to subsequent nodes |
| Emergency incident report | Blocked when signature or receipt is missing | Check incident name, time, number of people involved, handler, and receipt; trigger once, view the node status in the run record, and confirm the interaction state is recorded |
| Handover record | Version and date consistent, responsible person clear | Check both parties of the handover, handover date, and receipt status; locate the node by nodeId in the run record, and confirm the branch direction and interaction state record |
Three common errors
- Symptom: The name and quantity of the same hazard do not match between the checklist and the ledger. Cause: The two were entered separately, not backfilled according to the same record, and fields were not compared one by one during handover.
- Symptom: Material versions are not synchronized, and the old version is still issued. Cause: After modification, the version and date were not updated, and subsequent nodes still referenced the old draft to continue execution.
- Symptom: The handover record lacks a signature or receipt. Cause: The receipt step did not enforce a receipt, the responsible person did not confirm during handover, and missing items were not intercepted by nodes.
How to verify the setup
This feature's acceptance: run trials option by option, and check the branch directions and interaction states in the run record; confirm options correspond one-to-one with branches, the selection result variable has been passed to subsequent nodes, locate the node by nodeId in the run record, and check whether the variables reference takes effect.
Business test: draft one according to the template and complete one handover, and see whether missing items are intercepted.
- In the node, verify options and branch connections one by one, confirming each option corresponds to one branch; after triggering once, view the node status in the run record.
- Reference the selection result variable in subsequent nodes and run a trial once, confirming it has been passed to subsequent nodes; at the same time, check whether the material name, quantity, date, and signature receipt are consistent.