What this category's data looks like
This category's data covers four types: ingredient names and specifications, retention sample times and batches, disinfection periods, and absence cause classification. Ingredient and retention sample batch data come from purchase orders and retention sample registration, with updates rolling by meal and batch; disinfection periods are reported daily by childcare staff, and absence cause classification is aggregated from morning checks and class records. When entering workflow orchestration, ingredient names and specifications are used to compare recipes with purchased categories, retention sample times and batches are used to check whether documents and physical items are from the same batch, disinfection periods are used to check whether any period is missing, and absence cause classification is used to determine whether an escalation branch needs to be triggered. Each material serves as a basis for judgment and is not mixed into the same object, making it easy to select and verify branch by branch in interaction nodes.
Configuration and implementation checks
This step is executed by workflow nodes (user selection and branches), outputting branch directions and interaction state records. The handover-ready deployment state and operation records are completed by subsequent nodes continuing execution along the branches. When a 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 |
|---|---|---|
| Ingredient names and specifications | Whether recipes and purchased categories are consistent | Check options and branch connections one by one in the node, and reference variables to see whether the selection result variable is passed to subsequent nodes |
| Retention sample times and batches | Whether documents and retention sample batches match | Trigger a user selection node once, check the node status in the run record, and verify the branch direction corresponding to nodeId |
| Disinfection periods | Whether any disinfection record period is missing | Reference the selection result variable in a subsequent node and run a test once, and verify whether the variables value is consistent with the selected branch |
| Absence cause classification | Whether the classification is consistent with morning check records | Check item by item according to the handover form, see which record is missing, and verify whether the interaction state of nodeId is recorded |
Three common errors
- Symptom: after selecting an option, the default branch is still taken. Cause: options and branch connections were not checked one by one, and the interaction state record was not compared with the branch direction.
- Symptom: documents and retention sample batches do not match. Cause: retention sample times and batches were not updated rolling by meal, and the handover form lacks a batch record item.
- Symptom: disinfection records are missing a period. Cause: disinfection periods were not reported period by period, the process stops after interaction is completed, and subsequent nodes do not continue execution along the branch.
How to verify the setup
This feature acceptance: run a test for each option one by one, and check the branch direction and interaction state in the run record.
Business test: check item by item once according to the handover form, and see which record is missing.
- Check options and branch connections one by one in the node, and confirm that each option corresponds to one branch.
- Reference the selection result variable in a subsequent node and run a test once, and verify the
variablesandnodeIdrecords.