What this category's data looks like
This category's data looks like this: Progress records and statistical reconciliation for kindergarten health care and meal management; the materials come from three places: the health room, the cafeteria, and the classes. The health room submits absence cause classification tables and disinfection period records; the cafeteria submits ingredient name and specification sheets, retention sample time and batch ledgers, and menu-to-purchasing-category comparisons; the classes submit weekly attendance and meal records. When the materials enter this function, the HTTP node is responsible for sending requests for the progress table and statistical scope description to the external system; the materials themselves are referenced as request body fields or path parameters and the scope is not rewritten here. The update rhythm has two tiers, weekly and monthly: weekly records are for aggregate reconciliation, monthly records are for archiving. Field characteristics center on batch numbers, period start and end, cause classification codes, and specification names; these fields determine whether the statistical counts can match the record counts.
Configuration and implementation checks
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 "progress table and statistical scope description" is parsed from the response by subsequent nodes, or the external system handles it as agreed and then completes it. The HTTP module sends requests to the target address, and variables can be used as placeholders in all three places: path parameters, request body, and request headers.
| Object | Check | Verification action |
|---|---|---|
| Request address and path parameters | The placeholder variables can be resolved into actual values, and the address points to the external system's progress record interface | View the fully rendered address in the request preview, and check whether the path parameters resolve to ingredient names and specifications, retention sample time, and batch |
| Request headers | Authentication information is passed in according to the external system's requirements, and the value source is traceable | Check the request header names and value sources, and confirm that Authorization comes from a global variable or the output of a preceding node |
| Request body | The fields are consistent with the external interface agreement, and absence cause classification and disinfection periods can be matched | Use a sample request to compare the response, and check whether the record count and statistical count in responseData are consistent |
| Variable sources | Every placeholder can be traced to a specific origin | Check the source of each placeholder in the variables panel, and confirm that each item in the variables panel corresponds to a global variable, system variable, or the output of a preceding node |
Three common errors
- Symptom: documents and retention sample batches do not match. Cause: the batch field in the request body is taken from the output of a preceding node, and that output is not sorted by retention sample time, causing statistical counts to be aggregated under the wrong batch.
- Symptom: the menu and purchasing categories are inconsistent. Cause: when the path parameter references ingredient names and specifications, an abbreviation is used, the external system fails to match by full name, and empty values appear in the returned fields.
- Symptom: disinfection records are missing periods. Cause: request header authentication passes but the request body does not pass the disinfection period start and end, so the external system writes according to the default period, and the totals do not match the original records.
How to verify the setup
How to verify the setup: Acceptance for this function: preview the rendered request, check the status code and returned fields, then compare the result against one sample to confirm that the record count and statistical count in responseData are consistent.
Business test: use one week of records to reconcile the totals, check whether the scope and exceptions are clearly written, and whether absence cause classification and disinfection periods are missing.
- In the request preview, check the fully rendered address and confirm that the path parameters resolve into actual values.
- In the variables panel, check the source of each placeholder and confirm that each item in
variablescan be traced to a global variable, system variable, or the output of a preceding node.