What this category's data looks like
For the kindergarten health care and meal management scenario, materials come from the daily ledgers of the health room and the cafeteria: quantified recipes, food procurement orders and specifications, retention sample registration (time and batch), disinfection period records, and absence cause classification tables. The update rhythm is daily records, weekly summaries, and monthly statistics. Field characteristics center on food name and specification, retention sample time and batch, disinfection period, and absence cause classification. When entering this function, the recipe and procurement order assume the role of the source of the caliber, the retention sample and disinfection records assume the role of process evidence, the absence cause classification assumes the role of statistical classification, and the progress table and statistical caliber description are completed by subsequent nodes continuing execution along branches.
Configuration and implementation checks
This link is executed by workflow nodes (user selection and branching), outputting the branch direction and interaction state records. The "progress table and statistical caliber description" is then completed by subsequent nodes continuing execution along branches. When a 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 |
|---|---|---|
| Food name and specification | Whether the procurement order and recipe categories are consistent, and whether the specification is written into the header | Check the options and branch connections one by one in the node, and reference variables to record category differences |
| Retention sample time and batch | Whether the document and the retention sample batch match, and whether the time falls within the meal period | Trigger a node once, view the node status in the run record, and compare the batch field |
| Disinfection period | Whether the disinfection record is missing a period, and whether the period corresponds to the class | Reference the selection result variable in a subsequent node and run a trial once, and check the branch corresponding to nodeId |
| Absence cause classification | Whether the cause classification uses a unified caliber, and whether exceptions are separately marked | Use one week of records to check the totals, and inspect the classification field and the statistical caliber description |
Three common errors
- Phenomenon: The document and the retention sample batch do not match. Cause: The retention sample registration only records the time but not the batch, while the procurement order batch is recorded elsewhere, so they cannot be matched one by one during verification.
- Phenomenon: The recipe and procurement categories are inconsistent. Cause: The recipe is organized by week, while procurement is ordered by day, and the category names and specifications are not unified into the header caliber.
- Phenomenon: The disinfection record is missing a period. Cause: Disinfection periods are recorded separately by class, shift handovers omit entries, and period gaps appear during aggregation.
How to verify the setup
This function's acceptance: run trials option by option, check the branch direction and interaction state in the run record, confirm that each option corresponds to one branch, that the selection result variable has been passed to subsequent nodes, and that variables and nodeId are queryable in the run record.
Business test: use one week of records to check the totals, see whether the caliber and exceptions are clearly written, whether the record count and statistical count match, and whether the caliber is written into the header.
- Check the options and branch connections one by one in the node, trigger once to view the node status in the run record, and confirm that the process continues downward after the interaction is completed.
- Reference the selection result variable in a subsequent node and run a trial once, check the branch direction and interaction state records, and verify that the same session does not enter the interaction repeatedly.