What this category's data looks like
This page focuses on material verification and discrepancy localization in kindergarten health care and meal management, covering four verification dimensions: ingredient names and specifications, retention sample times and batches, disinfection periods, and absence cause classification. Material sources include procurement documents, retention sample records, recipe ledgers, disinfection registrations, and absence registrations, updated daily or weekly, with fields primarily consisting of names, quantities, dates, periods, and batches. When entering this function, procurement documents and retention sample records serve as materials to be verified, recipe ledgers and disinfection registrations serve as comparison benchmarks, and absence cause classification serves as classification verification material, each assuming different roles and jointly supporting the generation and review of the discrepancy list.
Configuration and implementation checks
This step is executed by workflow nodes (user selection and branching), outputting branch directions and interaction state records. The "discrepancy list" is completed by subsequent nodes continuing execution according to the branch. When a node is triggered, the conversation enters an interactive state and records the workflow state. After the user completes the selection, the branch corresponding to the selected option continues execution. The selection result variable has been passed to subsequent nodes. Subsequent nodes reference this variable and run a test once to confirm the direction.
| Object | Check | Verification action |
|---|---|---|
| Procurement documents and retention sample records | Whether ingredient names and specifications, retention sample times and batches are consistent | Compare names, specifications, batches, and retention sample times one by one, check options and branch connections individually in the node, and record inconsistent fields |
| Recipe ledgers and procurement categories | Whether the categories listed in the recipe correspond to the procurement categories | Check recipe categories against procurement categories daily, trigger once to view node status in the run records, and mark missing or extra categories |
| Disinfection registrations and absence registrations | Whether disinfection periods are continuous and absence cause classification is unified | Check whether disinfection periods have omissions, inspect the classification criteria for absence causes, reference variables and nodeId in subsequent nodes, and run a test once |
Three common errors
- Phenomenon: Document and retention sample batches do not match. Cause: Retention sample records are registered by batch, while procurement documents are summarized by category. The two sets of numbers have no established correspondence, making it impossible to locate items one by one during verification.
- Phenomenon: Recipe and procurement categories are inconsistent. Cause: Recipes are organized weekly, while procurement orders are placed daily. Category names and specification criteria differ, resulting in same name different specification or same specification different name during comparison.
- Phenomenon: Disinfection records are missing periods. Cause: Disinfection registrations are filled in by shift, and handover periods are not covered. During verification, period gaps are found, making it impossible to determine whether disinfection has been completed.
How to verify the setup
This function acceptance: run a test for each option, check the branch direction and interaction state in the run records, confirm that each option corresponds to one branch, that the state is recorded when entering the node, and that the selection result variable has been passed to subsequent nodes.
Business test: use one real record to find fields inconsistent with the ledger, and check whether the name, quantity, and date of that field are consistent across procurement documents, retention sample records, recipe ledgers, disinfection registrations, and absence registrations.
- Check options and branch connections individually in the node, trigger once to view node status in the run records, and confirm that the process continues downward after the interaction is completed.
- Reference
variablesandnodeIdin subsequent nodes and run a test once, check whether the selection result variable is passed in according to the branch, and record the branch direction and interaction state.