What this category's data looks like
The material on this page comes from the daily ledgers of kindergarten safety protection and emergency drills: hazard inspection records, rectification receipts, drill plans and sign-in sheets, access control and school bus checklists, and responsible person signature pages. These materials are updated by shift and drill cycle; hazard items carry rectification deadlines, drill records carry headcounts and sign-ins, and checklists carry item-by-item checkmarks and signatures. When the materials enter workflow orchestration, each has a different role: hazard items and rectification deadlines are used to determine closure, drill headcounts and sign-ins are used to determine whether records match the plan, access control and school bus check items are used to determine omissions, and responsible person signatures are used to determine whether the handover is complete. Only when version, connection, and task records are consistent do they form a handover-ready deployment state and operation record.
Configuration and implementation checks
This step is executed by workflow nodes (user selection and branching), outputting branch direction and interaction state records. The handover-ready deployment state and operation record are completed by subsequent nodes continuing execution along the branch. When the user selection node is triggered, the conversation enters the interaction state and records the workflow state; after the user completes the selection, execution continues along the branch corresponding to the selected option.
| Object | Check | Verification action |
|---|---|---|
| Hazard inspection records | Whether hazard items and rectification deadlines are closed, and whether unclosed items carry deadlines and responsible person signatures | Compare hazard items, rectification deadlines, and signature pages one by one, and verify options and branch connections in the node |
| Drill sign-in sheets | Whether drill headcounts and sign-ins match the plan, and whether records are consistent with the plan process | Check headcounts, sign-ins, and process against the plan, reference the selection result variable in subsequent nodes, and run a test once |
| Access control and school bus checklists | Whether access control and school bus check items are omitted, and whether responsible person signatures are complete | Check item by item according to the checklist, and trigger once to view node status in the run record |
| Deployment and operation records | Whether version, connection, and task records are consistent, and whether branch direction is traceable | Verify nodeId and branch direction in the run record, and record the variables reference relationships |
Three common errors
- Symptom: A hazard item still shows as unclosed on the handover form. Cause: The rectification deadline and responsible person signature were not recorded along with the branch direction, so subsequent nodes cannot determine closure.
- Symptom: The drill record does not match the plan, and the headcount and sign-ins do not correspond. Cause: The selection result variable was not passed to subsequent nodes, and the branch continued execution along the default path.
- Symptom: Access control and school bus check items are omitted, and the signature page is missing items. Cause: Options and branch connections were not checked one by one, and after the interaction completed, the process stopped or repeatedly entered the interaction.
How to verify the setup
Acceptance of this feature: run a test for each option one by one, check the branch direction and interaction state in the run record, and check whether the references of nodeId and variables are consistent.
Business testing: check once item by item according to the handover form to see which record is missing, focusing on hazard closure, drill headcount and sign-ins, access control and school bus check items, and responsible person signatures.
- Check options and branch connections one by one in the node, and trigger once to view node status in the run record.
- Reference the selection result variable in subsequent nodes and run a test once to confirm that the branch direction and interaction state record are handover-ready.