What this category's data looks like
School safety hazard inspections and campus incident reporting involve three types of materials: safety inspection checklists, hazard rectification ledgers, and emergency incident reports. Safety inspection checklists are filled out weekly or monthly by the inspector, with fields including inspection item, location, date, and inspector signature; hazard rectification ledgers are updated by rectification cycle, with fields including hazard name, quantity, responsible person, rectification deadline, and re-inspection signature; emergency incident reports are submitted immediately upon the occurrence of an incident, with fields including incident name, number of people involved, date of occurrence, reporter, and receipt. After the three types of materials enter the workflow, the checklists and ledgers are used to generate the original records of the abnormal list, and the incident reports are used to trace the source of the incident and the review conclusion. Material versions are often not synchronized due to supplementary entries and revisions, causing the name, quantity, and date of the same record to mismatch across the two materials, or signatures and receipts to be missing.
Configuration and implementation checks
This step is executed by workflow nodes (user selection and branching), outputting branch directions and interaction state records. The abnormal list and review conclusion are completed by subsequent nodes continuing execution along the branch. When a node is triggered, the conversation enters an interaction state and the workflow state is recorded; after the user completes the selection, execution continues along the branch corresponding to the selected option.
| Object | Check | Verification action |
|---|---|---|
| Safety inspection checklist | Inspection item, location, date, and inspector signature are complete, and the name, quantity, and date of the same hazard match the ledger | Check the options and branch connections one by one in the node, reference variables and nodeId for a trial run, and view the node status in the run records |
| Hazard rectification ledger | Hazard name, quantity, responsible person, rectification deadline, and re-inspection signature are compared field by field with the corresponding records in the inspection checklist, and versions are synchronized | Reference the selection result variable in a subsequent node and run a trial once, checking the branch direction and interaction state |
| Emergency incident report | Incident name, number of people involved, date of occurrence, reporter, and receipt are cross-consistent with the ledger and checklist, with no missing signatures | Trigger a user selection node once, and view the node status and branch direction in the run records |
| Abnormal list and review conclusion | The abnormality is supported by original records, the reviewer's signature is complete, and the source material can be traced | Create an abnormal record, continue execution along the branch in a subsequent node, and verify whether the source material can be traced |
Three common errors
- Symptom: The name, quantity, and date of the same hazard mismatch between the safety inspection checklist and the rectification ledger. Cause: The two materials are entered separately, without cross-comparison and version synchronization.
- Symptom: The emergency incident report lacks the reporter's signature or receipt, and the review conclusion cannot be confirmed. Cause: The reporting step does not enforce a receipt, and signatures are missing during material 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
This feature acceptance: run trials for each option one by one, check the branch direction and interaction state in the run records, and confirm that variables and nodeId are correctly referenced in subsequent nodes.
Business test: create an abnormal record, see whether the source material can be traced, and check the reviewer's signature and the support of the original records.
- Check the options and branch connections one by one in the node, and after a trial run, view the node status and branch direction in the run records.
- Reference the selection result variable in a subsequent node and run a trial once, confirming that the process continues downward after the interaction is completed.