What this category's data looks like
Kindergarten health care and meal management involves materials such as ingredient names and specifications, sample retention times and batches, disinfection periods, and categorization of absence causes. Ingredient purchase orders and menus are updated weekly, sample retention records are generated by meal batch, disinfection records are filled in by period such as nap time, before meals, and at departure, and absence causes are categorized based on morning checks and parent notifications. When these materials enter the form input node, each plays a different role: purchase orders and menus are used to check category consistency, sample retention records are used to check batch and time, disinfection records are used to check period completeness, and absence causes are used to check categorization criteria. Visitor identity determines the visible scope: parents can see their class's menu and absence feedback, while superiors can see aggregated sample retention and disinfection periods. The update rhythm of materials is bound to meals and periods, and field characteristics are structured values such as batch number, period, and cause category.
Configuration and implementation checks
This step is executed by the form input node (interaction node) in the workflow, which outputs the field values filled in by the user (passed to subsequent nodes after submission). The externally available entry points and authorization scope are then completed by subsequent nodes or manually. After the form input node is triggered, the conversation enters an interactive state and records the workflow state. After the user fills in the required items and submits, the form information is passed to subsequent nodes for use.
| Object | Check | Verification action |
|---|---|---|
| Ingredient names and specifications | Consistent with the menu and purchase category, and specifications can correspond to a specific meal | Check field names one by one in the formInput node configuration, use userSelect to select an ingredient and submit, then check the specification value obtained by subsequent nodes |
| Sample retention time and batch | The document matches the sample retention batch, and the time falls within the corresponding meal | Check whether the sample retention field is required, reference this field in a subsequent node after submission and run a test, and confirm that the batch value can be obtained |
| Disinfection period | The disinfection record has no missing periods, and periods such as nap time, before meals, and at departure are complete | Check the period field name and required marker, submit once, and then check whether the period value obtained by subsequent nodes is complete |
| Absence cause categorization | The categorization criteria are unified, and the visible scope for parents and superiors matches identity | Access once with a restricted identity, check whether the visible scope matches the setting, and check the cause categorization field value |
Three common errors
- Phenomenon: The sample retention document does not match the sample retention batch. Cause: The form fields do not correspond one-to-one with the batch number, so after submission the batch value obtained by subsequent nodes is missing or misaligned.
- Phenomenon: The menu is inconsistent with the purchase category. Cause: The ingredient name and specification fields are not marked as required, so they can pass even when empty on submission, and subsequent nodes cannot obtain the corresponding category value.
- Phenomenon: The disinfection record is missing periods. Cause: The disinfection period fields were not checked one by one, so after submission in the interactive state the field values are incomplete, and subsequent nodes cannot restore the complete periods.
How to verify the setup
Acceptance for this feature: fill it out once and submit, check the field values obtained by subsequent nodes, confirm that formInput enters the interactive state after being triggered, and that after submission the field values are passed to subsequent nodes; use userSelect to select an ingredient and then check the obtained value.
Business test: access once with a restricted identity, see whether the visible scope matches the setting, and confirm that unauthorized content is not visible.
- Check field names and required markers one by one in the
formInputnode configuration to ensure that key material fields are marked as required. - Reference this field in a subsequent node and run a test to confirm that the corresponding field value can be obtained after submission, and that the conversation does not remain in the interactive state.