What this category's data looks like
For kindergarten health care and meal management, materials come from morning checks and absence registration, menus and purchase orders, sample retention and disinfection records, parent notifications and reports to higher authorities. Ingredient names and specifications, sample retention times and batches, disinfection periods, and absence cause classification each play different roles: ingredients and specifications determine whether menus and purchases match, sample retention times and batches determine whether documents can be traced back to specific meals, disinfection periods determine whether records are continuous, and absence cause classification determines whether reporting standards are consistent. The update rhythm produces morning check and disinfection records daily, sample retention and menus per meal, and summarizes purchases and absence classification weekly. When materials enter the authorized access and external services workflow, the user first selects nodes to determine visitor identity and visible scope, and then subsequent nodes organize external entry points by branch.
Configuration and implementation checks
This link is executed by workflow nodes (user selection and branching), outputting branch directions and interaction status records. The externally available entry points and authorization scope are further executed and completed by subsequent nodes according to branches. When the user selection node is triggered, the conversation enters an interactive state and records the workflow status. After the user completes the selection, the corresponding option is followed to continue execution along the branch.
| Object | Check | Verification action |
|---|---|---|
| Sample retention records | Whether sample retention times and batches can correspond to the day's documents meal by meal | Check options and branch connections one by one in the node, use nodeId to locate the sample retention branch, and run a trial to see whether batches follow the options into the corresponding branch |
| Menu and purchase categories | Whether ingredient names and specifications are consistent with purchase categories | Reference the selection result variable in variables in subsequent nodes and run a trial to check whether menu categories and purchase categories come from the same source |
| Disinfection records | Whether disinfection periods cover all periods of the day without omission | Trigger an interaction once, check the node status in the run record, and confirm whether the disinfection period branch enters according to the option |
| Absence cause classification | Whether absence cause classification is consistent with the reporting standard | Access once with a restricted identity and see whether the visible scope of the absence classification branch matches the setting |
Three common errors
- Phenomenon: Sample retention documents and sample retention batches do not match. Cause: The selection result variable is not passed to subsequent nodes, and batches are taken from the default branch.
- Phenomenon: The categories listed in the menu are inconsistent with the purchase categories. Cause: Ingredient names and specifications are not synchronized with the branch, and each side takes its own set.
- Phenomenon: Disinfection records are missing periods. Cause: After the interaction is completed, the process stops, and subsequent nodes do not continue execution according to the branch.
How to verify the setup
Acceptance of this function: Run trials for each option one by one, check the branch direction and interaction status in the run record, and reference variables and nodeId in subsequent nodes to confirm that the selection result has been passed.
Business test: Access once with a restricted identity and see whether the visible scope matches the setting.
- Check options and branch connections one by one in the node, and confirm that each option corresponds to one branch.
- Trigger an interaction once, and check whether the node status in the run record is recorded.