What this category's data looks like
School safety hazard inspections and campus incident reporting draw on materials from safety inspection checklists, hazard rectification ledgers, and emergency incident reports. Safety inspection checklists are updated weekly or monthly, with fields including inspection item, location, date, and inspector signature; hazard rectification ledgers roll forward by rectification cycle, with fields including hazard name, quantity, rectification deadline, responsible person, and receipt; emergency incident reports are triggered by events, with fields including incident name, number of people involved, report time, and handler signature. The three types of materials play different roles when they enter workflow orchestration: safety inspection checklists serve as the basis for triggering and classification, hazard rectification ledgers serve as the basis for post-branch verification and receipts, and emergency incident reports serve as the basis for reporting and handover. When update rhythms are inconsistent, the name, quantity, and date of the same record in two materials easily fail to match, versions are not synchronized, and signatures or receipts are missing, causing deployment status and operation records to be impossible to hand over item by item.
Configuration and implementation checks
This step is executed by workflow nodes (user selection and branching), outputting branch directions and interaction state records. The handover-ready deployment status and operation records are completed by subsequent nodes continuing execution along 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 |
|---|---|---|
| Safety inspection checklist | Whether inspection item, location, date, and inspector signature correspond item by item with the hazard rectification ledger | In the user selection node, check the options and branch connections one by one, then reference the selection result variable in subsequent nodes and run a trial once |
| Hazard rectification ledger | Whether hazard name, quantity, rectification deadline, responsible person, and receipt are consistent with the emergency incident report | Trigger a node once, check the node status in the run records, and verify the material fields against the branch direction |
| Emergency incident report | Whether incident name, number of people involved, report time, and handler signature match the dates in the safety inspection checklist | Reference variables and nodeId in subsequent nodes, run a trial once, and observe the branch direction and interaction state records |
| Deployment status and operation records | Whether version, connection, and task records are consistent | Check item by item against the handover form once, see which record is missing, and verify the branch direction in the run records |
Three common errors
- Symptom: The name and quantity of the same hazard do not match between the safety inspection checklist and the hazard rectification ledger. Cause: The two materials have different update rhythms, and entries were not checked item by item against the same record.
- Symptom: The emergency incident report has been submitted, but the hazard rectification ledger still shows the old version. Cause: Versions were not synchronized, and the workflow branch direction and interaction state records were not updated along with the materials.
- Symptom: During handover, a missing signature or receipt is found, making it impossible to determine which branch to take. Cause: The selection result of the user selection node was not passed to subsequent nodes, and the process stalls after the interaction completes.
How to verify the setup
Feature acceptance: run a trial for each option one by one, check the branch direction and interaction state in the run records, confirm that each option corresponds to one branch, and check whether the references to variables and nodeId in subsequent nodes take effect.
Business testing: check item by item against the handover form once, see which record is missing, and verify whether the fields, dates, and signatures of the safety inspection checklist, hazard rectification ledger, and emergency incident report are consistent.
- In the user selection node, check the options and branch connections one by one, and trigger once to view the node status in the run records.
- Reference the selection result variable in subsequent nodes and run a trial once, and verify whether version, connection, and task records are consistent.