What this category's data looks like
This category's data covers four types of materials: ingredient names and specifications, sample retention times and batches, disinfection periods, and absence cause classification. Ingredient names and specifications come from procurement and menus; sample retention times and batches come from kitchen operation records; disinfection periods come from childcare execution sheets; absence cause classification comes from class morning checks. When these materials enter authorized access and external services, ingredient names and specifications determine the visible scope of menus, sample retention batches determine the external fields of traceability documents, disinfection periods determine the content of childcare records opened to superiors, and absence cause classification determines the granularity opened to parents. The update rhythm advances daily and per meal; field characteristics are mainly time, batch, period, and classification, and the external entrance must remain consistent with internal documents.
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 externally available entrance and authorization scope" are completed by subsequent nodes parsing the response, or by the external system handling it according to the agreement. The request URL, path parameters, request headers, and request body can all use variable placeholders; variables come from global variables, system variables, or the output of preceding nodes.
| Object | Check | Verification action |
|---|---|---|
| Ingredient names and specifications | Whether the menu and procurement category are consistent, and whether the specifications can correspond to a specific meal | Use variables in the request body to reference the ingredient fields output by the preceding node, and after preview rendering, compare with the procurement document |
| Sample retention times and batches | Whether the document and sample retention batch match, and whether the time can fall on a specific meal | Reference the sample retention batch variable in the path parameters, and check whether the time and batch in the returned fields are consistent with the sample retention record |
| Disinfection periods | Whether the disinfection record is missing periods, and whether the periods can cover the childcare execution sheet | Pass Authorization in the request header and then send the request, and check whether the disinfection periods in the returned fields are complete |
| Absence cause classification | Whether the classification is exposed at the agreed granularity, and whether restricted identities can see beyond their authorization | Access once with a restricted identity, and check whether the visible scope in responseData matches the setting |
Three common errors
- Symptom: The external document and the sample retention batch do not match, and the corresponding meal cannot be found during traceability. Cause: The batch variable in the request body comes from a different source and is not aligned with the sample retention record.
- Symptom: The menu and procurement category are inconsistent, and the ingredients parents see differ from the procurement document. Cause: Ingredient names and specifications are not rendered from the same source, and the variable placeholder resolves to an old value.
- Symptom: The disinfection record is missing periods, and superiors cannot determine whether childcare execution is complete when viewing it. Cause: The disinfection period field is not passed in with the request body, and the returned field is empty.
How to verify the setup
Acceptance for this feature: preview the rendered request, check the status code and returned fields, then compare the result against one sample; confirm that the variables in the path parameters, request headers, and request body all resolve to actual values, that Authorization is passed in according to the external system's requirements, that the responseData fields are consistent with the agreement, and that the status code is 200.
Business test: access once with a restricted identity, and see whether the visible scope matches the setting.
- In the request preview, view the complete rendered address and check whether the path parameter placeholders resolve to actual values.
- In the variable panel, check the source of each placeholder, and confirm that the request header names and value sources meet the external system's requirements.