What this category's data looks like
This page addresses kindergarten childcare daily life management; the materials include the daily life schedule, morning and afternoon check records, and child health observation records. The daily life schedule is updated weekly or daily and contains activity time periods, segment names, venues, and responsible persons; the morning and afternoon check records are generated per class per day and contain child names, body temperature, throat and hand observations, abnormality markers, inspectors, and signatures; the child health observation records are generated as needed and contain observation time, symptom description, handling method, and parent receipt. When these three types of materials enter the question acceptance and missing-item follow-up function, the schedule provides the basis for time periods and segments, the morning and afternoon check records provide the health facts of the day, and the observation records provide clues for continuous individual tracking. Field characteristics center on names, quantities, dates, and signatures; the update rhythm is mainly daily, supplemented by weekly; receipts and signatures determine whether the materials can be trusted.
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 "accepted records and items to be completed" are parsed from the response by subsequent nodes, or handled externally according to the agreement to complete the process. The request URL, path parameters, request headers, and request body can all reference global variables, system variables, or outputs from preceding nodes via variables; authentication information is placed in Authorization according to the external system's requirements, and the returned content is received in responseData.
| Object | Check | Verification action |
|---|---|---|
| Daily life schedule | Time periods, segment names, dates, and responsible person signatures are complete, and correspond to the class and date in the morning and afternoon check records | In the request preview, check the rendered URL and request body fields, and compare whether the dates and segment names in the schedule and the morning and afternoon check records are consistent |
| Morning and afternoon check records | Child names, body temperature, abnormality markers, inspector signatures, and inspection dates are not missing, and the names and quantities in the same record are consistent across materials | Use one sample request to compare the returned fields, and check whether the name, body temperature, date, and signature fields in responseData are consistent with the paper records |
| Child health observation records | Observation time, symptom description, handling method, parent receipt, and version are synchronized, with no missing signatures or missing receipts | In the variables panel, check the source of each placeholder, and check whether the observation record fields and receipt status in variables are complete |
| HTTP request and external interface | Request header authentication information is passed in according to the external system's requirements, and the request body fields are consistent with the external interface agreement | Check the request header names and value sources, and check the value source of Authorization and the returned status code |
Three common errors
- Symptom: The names, quantities, and dates of the same record do not match between the schedule and the morning and afternoon check records. Cause: The two materials are entered separately, and no comparison is made using the same date and class as the key.
- Symptom: The observation record version is not synchronized, and the old and new versions circulate at the same time. Cause: After updating, the external system is not written back, and the request body still references the old fields.
- Symptom: Morning and afternoon check records are still accepted even though signatures are missing or receipts are missing. Cause: The request body does not validate the signature field, and the external system does not intercept according to the agreement.
How to verify the setup
This function's acceptance: preview the rendered request, check the status code and returned fields, then compare the result against one sample, and confirm that the values and sources of variables, Authorization, and responseData are consistent.
Business test: submit a question missing key information and see whether it asks a follow-up question before answering.
- In the variables panel, check the source of each placeholder, and confirm that global variables, system variables, or outputs from preceding nodes can be resolved into actual values.
- Use one sample request to compare the return, check the request header names and value sources, and confirm that authentication information is passed in according to the external system's requirements.