What this category's data looks like
This page addresses the kindergarten health care and meal management scenario, where materials include ledgers and records such as ingredient names and specifications, sample retention times and batches, disinfection periods, and absence cause classifications. These materials come from daily reporting by the health room, cafeteria, and classes, with an update cadence of daily or per meal, and field characteristics of batch numbers, periods, and classification codes. When entering the HTTP interface and external system feature, ingredient specifications and sample retention batches serve as request body fields, while disinfection periods and absence causes serve as path parameters or query variables, each playing the role of transmitting the current version and change records to the external system, ensuring the current version is unique, old versions are traceable, and references are synchronized.
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 version ledger and change records must be handled by subsequent nodes parsing the response, or by the external system according to the agreement. The HTTP node is only responsible for sending requests according to the agreement, and does not replace the external system in writing to the database or approving.
| Object | Check | Verification action |
|---|---|---|
| Ingredient names and specifications | The request body fields are consistent with the external interface agreement and correspond to the recipe and procurement categories | Use a sample request to compare the response, and check whether the ingredient names and specifications are consistent with the procurement categories |
| Sample retention times and batches | The batch number in the path parameter or request body can be parsed into an actual value and matches the document batch | View the full rendered address in the request preview, and check whether the sample retention times and batches are consistent with the document |
| Disinfection periods | The request headers and request body fields cover the complete periods, with no missing periods | Check the request header names and value sources, and check whether the disinfection records have missing periods |
| Absence cause classification | The variable sources are traceable, and the classification codes are consistent with the external system agreement | Check the source of each placeholder in the variable panel, and confirm that the absence cause classification field is not empty |
Three common errors
- Symptom: The document and sample retention batch do not match. Cause: The batch number in the request body is taken from the output of the preceding node and is not synchronized with the actual document batch, causing the external system to receive an empty field or an old batch.
- Symptom: The recipe and procurement categories are inconsistent. Cause: The ingredient names and specifications are hardcoded in the request body without referencing variables, so after updating one place, the references are not updated synchronously.
- Symptom: Disinfection records have missing periods. Cause: The path parameters or request body do not cover all disinfection periods, and after the HTTP node sends the request according to the agreement, the external system writes to the database with missing-period data.
How to verify the setup
Preview the rendered request, check the status code and returned fields, then compare the result against a sample; check the source of each placeholder in variables, confirm that the Authorization request header is passed in as required by the external system, and check that the returned responseData fields are consistent with the agreement.
Business test: change one piece of content and see whether the version number and references are updated synchronously
- Check the full rendered address and request headers in the request preview, and confirm that the placeholder variables can be parsed into actual values
- Check the source of each placeholder in the variable panel, and confirm that the
variables,Authorization, andresponseDatafields are consistent with the external interface agreement