What this category's data looks like
This page focuses on three types of materials in kindergarten childcare daily life management: daily life schedule, morning and afternoon check records, and child health observation records. These materials come from daily class entries and health room summaries, with an update rhythm of daily records, weekly verification, and semester-based version archiving. The daily life schedule focuses on time periods, activity segments, and responsible person fields; morning and afternoon check records focus on date, child name, body temperature, and signature; child health observation records focus on observation date, symptom description, handling method, and parent receipt. When materials enter the HTTP interface and external system functions, each plays a different role: the schedule provides the version baseline, morning and afternoon check records provide daily execution evidence, and health observation records provide individual tracking clues. The three must maintain a unique current version in the version ledger, with old versions traceable and references updated synchronously, avoiding mismatches in names, quantities, and dates for the same record across different materials.
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 are parsed from the response by subsequent nodes, or handled by the external system according to the agreement to complete the next step.
| Object | Check | Verification action |
|---|---|---|
| Daily life schedule | Whether fields, dates, and signatures are consistent with the current version | Verify the request body fields against the external interface agreement, use variables to trace placeholder sources, and compare the version number and reference list in the returned fields |
| Morning and afternoon check records | Whether the name, quantity, and date of the same record match across the two materials | Check the source of the Authorization value in the request header, use a sample request to compare the returned date and quantity fields, and confirm that the signature or receipt field is not empty |
| Child health observation records | Whether the old version can be traced when the version is not synchronized or references are not updated | Check the source of each placeholder in the variable panel, view the reference synchronization result in responseData, and confirm that the old version is traceable |
| Version ledger and change records | Unique current version, traceable old versions, synchronized references | Use a sample request to compare the response, check the status code and returned fields, and confirm that the version number and reference entries in the change records are consistent |
Three common errors
- Symptom: The dates of the same record in the schedule and morning and afternoon check records do not match. Cause: The request body fields were not passed according to the external interface agreement, and the placeholder variables resolved to old values.
- Symptom: The version is not synchronized, and the old version is still referenced. Cause: The change records were not updated with the request response, and subsequent nodes did not parse the version field in the response.
- Symptom: Morning and afternoon check records lack a signature or receipt. Cause: The request header authentication information or request body fields are empty, and the external system did not write back confirmation after receiving empty fields.
How to verify the setup
This feature acceptance: preview the rendered request, check the status code and returned fields, then compare the result against a sample; confirm that the three identifiers Authorization, variables, and responseData can all be traced to specific sources.
Business test: change one piece of content and see whether the version number and references are updated synchronously; if the number of reference entries changes, record the array length separately, and verify the tokens of the reference text separately.
- In the request preview, view the complete rendered address and verify whether the path parameter placeholders are resolved to actual values.
- In the variable panel, check the source of each placeholder and confirm whether it comes from a global variable, system variable, or the output of a preceding node.