What this category's data looks like
This category's data looks like this: For kindergarten health care and meal management scenarios, materials come from morning check records, menus, purchase orders, sample retention ledgers, disinfection records, and absence registrations. The update cadence advances daily and per meal, and at handover the fields must be complete, the responsible person must be clear, and the version and date must be consistent. When entering this function, ingredient names and specifications, sample retention times and batches, disinfection periods, and absence cause classification are each used as verification objects: ingredients and specifications are used to compare menu and purchase categories, sample retention times and batches are used to compare documents and retention batches, disinfection periods are used to check whether disinfection records are missing periods, and absence cause classification is used to confirm that the registration standard is consistent. Draft materials that can be issued and handover records are completed by subsequent nodes continuing execution along branches; this function is only responsible for orchestrating branch direction and recording interaction status.
Configuration and implementation checks
Configuration and implementation checks: This step is executed by workflow nodes (user selection and branching), outputting branch direction and interaction status records. Draft materials that can be issued and handover 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 status; after the user completes the selection, execution continues along the branch corresponding to the selected option.
| Object | Check | Verification action |
|---|---|---|
| Ingredient names and specifications | Whether the menu and purchase categories are consistent | Check menu entries against purchase order categories, compare item by item, and record discrepancies |
| Sample retention times and batches | Whether the documents and retention batches match | Check the retention ledger batches against the handover documents, and confirm that the times and batches are consistent |
| Disinfection periods | Whether the disinfection records are missing periods | Check the periods covered by the disinfection records, and mark missing periods |
| Absence cause classification | Whether the classification standard is consistent | Check absence registrations against cause classification, and confirm that the standard is unified |
Three common errors
- Phenomenon: handover documents and retention batches do not match. Cause: sample retention times and batches were not updated in sync with the documents, and the version and date are inconsistent.
- Phenomenon: the menu and purchase categories are inconsistent. Cause: ingredient names and specifications were not checked against the same standard during drafting, and the purchase order was not backfilled.
- Phenomenon: disinfection records are missing periods. Cause: disinfection periods were not registered item by item according to meal or period, and each period was not verified during handover.
How to verify the setup
This function's acceptance: run through each option, and check the branch direction and interaction status in the run records; reference variables and nodeId in a subsequent node and run once to confirm that the selection result variable has been passed to the subsequent node.
Business test: draft one copy according to the template and complete one handover, and see whether missing items are blocked.
- In the node, check the options and branch connections one by one, and confirm that each option corresponds to one branch
- Trigger the user selection node once, view the node status in the run records, and confirm that the process continues downward after the interaction is completed