What this category's data looks like
This page addresses kindergarten health care and meal management scenarios, bringing together four types of materials: ingredient names and specifications, retention sample times and batches, disinfection periods, and absence cause classification. Ingredients and procurement documents come from handover records between the health room and the kitchen; retention sample and disinfection records come from daily duty logs; absence causes come from class morning checks and parent feedback. Materials are updated daily or per batch, with fields mainly consisting of batch numbers, time periods, and category names, while specifications and time points are often mixed in text form. After entering the exception tracing and manual review function, ingredient and retention sample batches are used to compare document consistency, disinfection periods are used to check record completeness, and absence cause classification is used to determine whether the classification matches the original description.
Configuration and implementation checks
This step is executed by the HTTP node in the workflow, outputting the response body, status code, and returned fields. The exception list and review conclusions are parsed from the response by subsequent nodes, or handled by an external system according to the agreement. The HTTP module sends requests to the target address, and variables can be used as placeholders in three places: path parameters, request body, and request headers. Variables come from global variables, system variables, or outputs from preceding nodes.
| Object | Check | Verification action |
|---|---|---|
| Ingredient names and specifications | Whether the procurement documents and recipe categories are consistent | Compare the recipe and procurement records item by item for names and specifications, and see whether the source document can be traced |
| Retention sample times and batches | Whether the retention sample batch matches the batch on that day's documents | Search retention sample records by batch number, and check whether the time point and document batch are consistent |
| Disinfection periods | Whether the disinfection records cover all periods that should be disinfected | Check period by period against the period list, mark missing periods, and review the original duty log |
| Request address and path parameters | Whether the placeholder variables can be resolved into actual values | View the fully rendered address in the request preview, and check the source of variables |
Three common errors
- Symptom: The retention sample batch does not match the document batch. Cause: Retention sample records are written by cooking completion time, while documents are written by procurement batch, and the two numbering systems have not been mapped.
- Symptom: The recipe and procurement categories are inconsistent. Cause: Recipes are arranged weekly, procurement orders are placed daily, substituted ingredients are not written back to the recipe, and category names deviate.
- Symptom: Disinfection records are missing periods. Cause: Duty logs are filled in by shift, handover periods are not supplemented, causing some disinfection periods to have no original records during tracing.
How to verify the setup
This function's acceptance: preview the rendered request, check the status code and returned fields, then compare the result against one sample, and check whether responseData and Authorization are passed in according to the external system agreement.
Business test: create one exception record, see whether the source material can be traced, and confirm that the exception is supported by original records and signed by the reviewer.
- In the variables panel, check the source of each placeholder, and confirm that
variablescan be traced to global variables, system variables, or outputs from preceding nodes. - Use one sample request to compare the returned fields with the external interface agreement, and check whether request body fields are empty and whether request header authentication is passed in according to the external system requirements.