What this category's data looks like
For multilingual materials and terminology handling in kindergarten safety protection and emergency drills, the materials include hazard rectification ledgers, drill plans and sign-in records, access control and school bus checklists, and responsible person signature pages. The sources are daily inspections and drill archives of the kindergarten, and the update cadence rolls by semester and drill round. Field characteristics: hazard items and rectification deadlines appear in pairs, the number of drill participants must correspond to the sign-in list, access control and school bus check items are checked one by one, and the responsible person's signature is used for closed-loop confirmation. When the materials enter workflow orchestration, the terminology glossary and the reference translation take on the role of unifying translated names, the ledgers and checklists provide items to be verified, the sign-in and signature pages are used to refer back to the original source, and branch selection determines which type of material subsequent nodes process.
Configuration and implementation checks
This step is executed by workflow nodes (user selection and branching), outputting branch directions and interaction state records. "Unified terminology glossary and reference translation" is continued and completed by subsequent nodes according to the branch. When the user selection node is triggered, the conversation enters an interactive 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 |
|---|---|---|
| Unified terminology glossary and reference translation | The same term is consistent throughout, the translated name can refer back to the original text, and hazard items and rectification deadlines appear in pairs | Check the options and branch connections one by one in the node, and use variables to reference the selection result variable for a trial run |
| Drill plans and sign-in records | The number of drill participants corresponds to the sign-in list, and the records do not conflict with the plan | Trigger one interaction, inspect the node status in the run record, and verify the branch direction corresponding to nodeId |
| Access control and school bus checklists | No check items are missing, access control and school bus check items are checked one by one, and the responsible person's signature can be traced back | Reference the selection result variable in a subsequent node and run a trial, confirming that the selected branch processes the corresponding checklist |
| Hazard rectification ledger | Hazard items and rectification deadlines form a closed loop, and the responsible person's signature is traceable | Check the options and branch connections one by one in the node, and confirm that the rectification ledger follows the corresponding branch |
Three common errors
- Symptom: hazards are not closed-loop, and there is still no signature after the rectification deadline has passed. Cause: the options and branches are not aligned, and the ledger material follows the default branch.
- Symptom: drill records do not match the plan, and the number of participants does not match the sign-in. Cause: after the interaction is completed, the process stops, and subsequent nodes do not continue execution according to the branch.
- Symptom: check items are missing, and the access control and school bus checklist misses one check. Cause: the same session repeatedly enters the interaction, and the state record is overwritten.
How to verify the setup
Acceptance for this feature: run trials for each option one by one, and check the branch direction and interaction state in the run record.
Business test: sample three terms and check whether their spelling is consistent throughout.
- Check the options and branch connections one by one in the node, and confirm that each option corresponds to one branch.
- Reference the selection result variable in a subsequent node and run a trial once, confirming that the selected branch continues execution.