What this category's data looks like
Kindergarten health care and meal management materials include quantified recipes, food ingredient purchase orders, sample retention records, disinfection records, absence cause registration, health room shift handover forms, and parent notification documents. Sources are mostly daily entries by health care workers, cafeteria managers, and class teachers. The update rhythm rolls forward by meal service, disinfection period, and daily absence report. Field characteristics center on ingredient names and specifications, sample retention time and batch, disinfection period, and absence cause classification. When entering workflow orchestration, quantified recipes and purchase orders assume the role of category comparison, sample retention records and disinfection records assume the role of period and batch verification, absence cause registration assumes the role of unifying classification standards, and parent notification documents assume the role of synchronizing external references.
Configuration and implementation checks
This stage is executed by workflow nodes (user selection and branching), outputting branch directions and interaction status records. The "version ledger and change records" are completed by subsequent nodes continuing execution according to 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 |
|---|---|---|
| Quantified recipes and food ingredient purchase orders | Whether ingredient names and specifications are aligned item by item, and whether recipe and purchase categories are consistent | Select "compare by category" in the option branch, check the branch direction and interaction status in the run record, and reference variables in a subsequent node to do a trial run |
| Sample retention records and disinfection records | Whether sample retention time and batch match, and whether disinfection periods are missing | Select the "verify by period" branch, check the node status corresponding to nodeId, and inspect whether the documents and sample retention batches are consistent |
| Absence cause registration | Whether the classification standard for absence causes is unified, and whether old classifications are traceable | Select the "by classification standard" branch, check whether the selection result variable has been passed to subsequent nodes, and record the number of array items |
| Parent notification documents | Whether external references are synchronously updated with the current version | Select the "reference synchronization" branch, and check whether subsequent nodes continue execution according to the branch and update references |
Three common errors
- Phenomenon: documents and sample retention batches do not match. Cause: sample retention records are updated by meal service, purchase orders are summarized daily, and the batch field is not synchronized with the option branch.
- Phenomenon: recipes and purchase categories are inconsistent. Cause: ingredient names and specifications are written differently in quantified recipes and purchase orders, and were not checked item by item in the nodes.
- Phenomenon: disinfection records are missing periods. Cause: disinfection periods are reported by class, the process stops after interaction is completed, and subsequent nodes do not continue execution according to the branch.
How to verify the setup
Feature acceptance: try each option one by one, check the branch direction and interaction status in the run record, confirm that each option corresponds to one branch, and check whether variables and nodeId references take effect in subsequent nodes.
Business test: change one piece of content, see whether the version number and references are synchronously updated, and confirm that the current version is unique, old versions are traceable, and references are synchronized.
- Check options and branch connections one by one in the nodes, trigger once, and view the node status in the run record
- Reference the selection result variable in a subsequent node and do a trial run once, recording the number of array items and the tokens of the referenced text