What this category's data looks like
This page addresses the kindergarten health care and meal management scenario, with materials from the kindergarten's health room and cafeteria: morning check and absence records, quantified recipes, procurement and acceptance documents, sample retention registration, and disinfection time schedules. These materials have different update rhythms: recipes are adjusted weekly, procurement documents are generated per batch, and sample retention and disinfection records are filled in per shift. After entering this function, each material plays a different role: recipes and procurement documents are used to check categories and specifications, sample retention registration is used to trace back to batches and times, disinfection time schedules are used to trace back to time periods, and absence records are used to trace back to cause classification. Field characteristics center on ingredient names and specifications, sample retention times and batches, disinfection time periods, and absence cause classification. Cross-material comparison is prone to discrepancies in definitions, requiring item-by-item tracing back to the original text.
Configuration and implementation checks
This step is executed by workflow nodes (user selection and branches), outputting branch directions and interaction state records. "Basis entries that can be traced back to the original text" 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 state. After the user completes the selection, execution continues along the branch corresponding to the selected option.
| Object | Check | Verification action |
|---|---|---|
| User selection node | Each option corresponds to one branch; options and branch connections must be matched one by one | Check options and branch connections one by one in the node, run a test once to view the branch direction, and check the interaction state corresponding to nodeId in the run records |
| Interaction state | The state is recorded when entering the node, and the process continues downward after the interaction is completed | Trigger once, check the node state and interaction state records in the run records, and confirm that the process does not stop after the interaction is completed |
| Selection result variable | Has been passed to subsequent nodes for subsequent nodes to continue execution according to the branch | Reference variables in subsequent nodes and run a test once to confirm that the value changes with the option and that the same session does not repeatedly enter the interaction |
| Ingredient names and specifications | Recipe and procurement categories must match, and specification definitions must be consistent | Extract recipe entries and procurement documents, compare ingredient names and specifications item by item, and trace back to the original text entries |
Three common errors
- Phenomenon: Documents and sample retention batches do not match. Cause: Sample retention registration is filled in per shift, while procurement documents are generated per batch, and the time and batch definitions of the two are not aligned.
- Phenomenon: Recipe and procurement categories are inconsistent. Cause: Recipes are adjusted weekly, procurement documents are generated per batch, and category names and specifications are not traced back to the original text item by item.
- Phenomenon: Disinfection records are missing time periods. Cause: The disinfection time schedule is filled in per shift, and during cross-material comparison the time period fields are not checked against the original text item by item.
How to verify the setup
This function's acceptance: run tests on each option one by one, check the branch direction and interaction state in the run records, and confirm that options and branch connections are consistent, variables has been passed to subsequent nodes, and records corresponding to nodeId can be queried.
Business test: ask a cross-material basis question, see whether the answer provides a traceable source, and check that the basis comes from the kindergarten's materials, the version is current, and the entries match the original text.
- Check options and branch connections one by one in the node, run a test once, and view the branch direction and interaction state in the run records.
- Reference
variablesin subsequent nodes and run a test once to confirm that the value changes with the option and that the process continues downward.