What this category's data looks like
This category's data covers materials such as ingredient names and specifications, retention sample times and batches, disinfection periods, and absence cause classification. Ingredient acceptance sheets and retention sample records are updated daily, menus are published weekly, disinfection records are filled in by shift, and absence registrations are summarized according to the morning and afternoon check rhythm. These materials each have a role when entering workflow orchestration: acceptance sheets and retention sample records serve as the source evidence for exception tracing, menus and procurement categories serve as the basis for consistency comparison, disinfection records are used for period completeness checks, and absence cause classification is used for attribution review. Field characteristics appear as structured information such as batch numbers, time points, category names, and cause codes, and must correspond item by item with the original documents.
Configuration and implementation checks
This step is executed by workflow nodes (user selection and branches), outputting branch directions and interaction state records. The "exception list and review conclusions" are then completed by subsequent nodes continuing execution according to the branch. When the user selection node is triggered, the conversation enters an interactive 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 acceptance sheets and retention sample records | When the documents and retention sample batches do not match, check whether the ingredient names and specifications, retention sample times and batches are consistent | Check the 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 |
| Menus and procurement categories | When the menus and procurement categories are inconsistent, check whether the category names and specifications correspond | Reference variables in a subsequent node and run a test once to confirm that the selection result variable has been passed |
| Disinfection records | When disinfection records are missing periods, check whether the disinfection periods are complete | Trigger the user selection node once and check the node status and nodeId in the run records |
| Absence cause classification | When the absence cause classification is inconsistent with the original registration, check the classification fields | Check the options and branch connections one by one in the node to confirm the branch direction |
Three common errors
- Symptom: after selecting an option, the default branch is still taken. Cause: the options and branch connections were not checked item by item, and the selection result variable was not correctly passed to subsequent nodes.
- Symptom: the documents and retention sample batches do not match. Cause: the retention sample times and batches were not recorded in sync with the acceptance sheets, so the source materials cannot be located during tracing.
- Symptom: the menus and procurement categories are inconsistent. Cause: menu publication and procurement categories were not aligned by the same category names and specifications, resulting in deviations during comparison.
How to verify the setup
Feature acceptance: run tests for each option one by one, check the branch direction and interaction state in the run records, and confirm that variables and nodeId are recorded completely.
Business test: create an exception record, see whether the source materials can be traced, and confirm the reviewer signature and the responsible person's handling path.
- Check the options and branch connections one by one in the node, trigger the user selection node once, and check the node status and
nodeIdin the run records. - Reference
variablesin a subsequent node and run a test once to confirm that the selection result variable has been passed, and that the exception list and review conclusions are completed by subsequent nodes continuing execution according to the branch.