What this category's data looks like
The materials for kindergarten safety protection and emergency drills cover four types of ledgers: hazard items and rectification deadlines, drill participant counts and sign-ins, access control and school bus check items, and responsible person signatures. The sources are kindergarten inspection forms, drill plans and sign-in sheets, access control and school bus daily inspection records, and rectification notices and receipts. The update cadence rolls forward with semesters, drill rounds, and rectification cycles, and old versions must be archived for reference. Field characteristics are version number, effective date, reviser, reference location, and responsible person signature. When materials enter workflow orchestration, the hazard ledger handles closed-loop rectification judgment, the drill materials handle comparison of participant counts and plan consistency, the access control and school bus records handle completeness verification of check items, and the signature materials handle responsible person confirmation. The version ledger and change records are completed by subsequent nodes continuing execution along branches, and reference synchronization depends on branch direction and interaction state records.
Configuration and implementation checks
This stage is executed by workflow nodes (user selection and branches), outputting branch direction and interaction state records. The "version ledger and change records" are then completed by subsequent nodes continuing execution along 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 selected option.
| Object | Check | Verification action |
|---|---|---|
| Hazard items and rectification deadline ledger | Whether the hazard is closed-loop, whether the rectification deadline has expired, whether old-version hazard entries are still referenced | In the node, check the options and branch connections one by one, confirming that closed-loop and non-closed-loop each follow one branch; reference variables in a subsequent node and run a trial once, then view the node status in the run record |
| Drill participant counts and sign-in materials | Whether the sign-in count matches the plan count, whether the drill record matches the plan, whether the old-version plan is still referenced | Check the options and branch connections, confirming that matching and non-matching counts each follow one branch; in a subsequent node, use nodeId to locate that branch and run a trial, then check whether the interaction state is recorded |
| Access control and school bus check item records | Whether check items are missing, whether school bus daily inspections have missing items, whether responsible person signatures are complete | In the node, check the options and branch connections one by one, confirming that missing items and complete items each follow one branch; reference variables in a subsequent node and run a trial once, then view the branch direction |
| Responsible person signatures and change records | Whether signatures correspond to the current version, whether old-version signatures are traceable, whether reference locations are synchronized | Check the options and branch connections, confirming that the current version and old version each follow one branch; in a subsequent node, use nodeId to locate and run a trial, then view the interaction state record |
Three common errors
- Symptom: the hazard ledger shows non-closed-loop, but the version number has already been upgraded to the new version. Cause: the rectification deadline and closed-loop judgment were not updated in sync with the branch, and old-version entries are still referenced.
- Symptom: the sign-in sheet is archived using the planned count despite a different participant count in the drill record. Cause: the comparison between drill materials and the plan did not follow an independent branch, and the reference location was not synchronized.
- Symptom: access control and school bus check items have missing items, but the responsible person signature column still shows complete. Cause: check item completeness verification did not follow branches item by item, and the interaction state was not recorded.
How to verify the setup
Feature acceptance: run trials option by option, and check the branch direction and interaction state in the run record.
Business test: change one piece of content, and see whether the version number and references are updated in sync.
- In the node, check the options and branch connections one by one, confirm that each option corresponds to one branch, and run a trial once after locating it with
nodeId. - Reference
variablesin a subsequent node and run a trial once, then check whether the node status and branch direction in the run record are consistent.