What this category's data looks like
This category's data covers daily ingredient names and specifications, sampling retention times and batches, disinfection time slots, and categorized causes of absence. Ingredient acceptance sheets and purchase orders come from the cafeteria and suppliers; sampling retention records are filled in by health care staff by batch; disinfection records are registered by childcare staff by time slot for activity rooms, dormitories, and restrooms; categorized causes of absence are summarized by class teachers. The update cadence is three meals and two snacks per day, sampling retention at every meal, disinfection once in the morning and once in the afternoon, and same-day reporting of absences. When these materials enter the Q&A intake and missing-item follow-up function, each plays its own role as a field source: ingredients and specifications are used to check the recipe against purchased categories, sampling retention times and batches are used to compare against documents, disinfection time slots are used to check record completeness, and categorized causes of absence are used to determine the direction of follow-up questions.
Configuration and implementation checks
This step is executed by the HTTP node in the workflow, which outputs the response body, status code, and returned fields. The intake records and the completed question items are parsed from the response by subsequent nodes, or handled by an external system according to the agreement to finish the process. The HTTP node does not replace the external system in writing to the database or approving.
| Object | Check | Verification action |
|---|---|---|
| Ingredient acceptance sheets and purchase orders | Whether ingredient names and specifications, and the recipe and purchased categories, are consistent | Verify the ingredient name and specification fields in the request body, compare against the purchase order categories, and generate a follow-up item when inconsistent |
| Sampling retention records | Whether the sampling retention time and batch match the documents | Verify the sampling retention time and batch fields in the request body, compare against the acceptance sheet batch, and follow up when they do not match |
| Disinfection records | Whether the disinfection time slots completely cover morning and afternoon | Verify the disinfection time slot field in the request body, and generate a follow-up item when a time slot is missing |
| Categorized causes of absence | Whether the categorized causes of absence are passed in according to the agreed enumeration | Verify the cause category field in the request body, and follow up when it is missing or out of range |
Three common errors
- Symptom: the document and the sampling retention batch do not match. Cause: the acceptance sheet batch was not passed in synchronously with the sampling retention record, and the request body field is empty or retains an old value.
- Symptom: the recipe and purchased categories are inconsistent. Cause: the ingredient name and specification fields were not updated according to the recipe, and the purchase order categories and the request body fields come from different sources.
- Symptom: the disinfection record is missing a time slot. Cause: the disinfection time slot field was passed in only once, the morning and afternoon records did not each occupy a placeholder, and the variable source points to a single node.
How to verify the setup
This function's acceptance: in the request preview, look at the rendered complete address, check the status code and returned fields, then compare the result against one sample; in the variables panel, check each placeholder source, confirm that responseData and variables are traceable, and pass the Authorization header as required by the external system.
Business test: submit a question missing key information and see whether it asks a follow-up question before answering.
- In the request preview, check the rendered address, request headers, and request body, and confirm that the placeholder variables can be resolved into actual values.
- Use one sample request to compare the returned fields, and check whether the external system receives empty fields or returns 401 or a timeout.