What this category's data looks like
This category's data covers three types of materials: daily life schedules, morning and afternoon check records, and child health observation records. The sources are daily entries by class teachers and review by health care personnel. The update rhythm advances daily; morning and afternoon checks are recorded once at entry and once before and after nap, health observations are added immediately when abnormalities occur, and daily life schedules are arranged weekly. The three types of materials play different roles in progress records and statistical verification: the daily life schedule provides activity time periods and responsible persons as the progress baseline; morning and afternoon check records provide item-by-item details such as attendance and body temperature, and are the source of record counts; child health observation records carry abnormality tracking and handling receipts, and are the source of exception criteria. Field characteristics center on date, child name, item name, quantity, signature, and receipt. After entering this function, the workflow reads and summarizes them for weekly or monthly report verification of totals.
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 criteria description" is parsed by subsequent nodes from the response, or handled externally according to the agreement to complete the next step. Variables can be used as placeholders in three places: the request URL and path parameters, request headers, and request body. Variables come from global variables, system variables, or outputs of preceding nodes, and the variables panel can be used to verify the source of each placeholder one by one.
| Object | Check | Verification action |
|---|---|---|
| Daily life schedule | Fields include date, time period, activity name, and responsible person, aligned day by day with morning and afternoon check records | Take one week's schedule, check whether dates and time periods are continuous, then compare names by date with morning and afternoon check records |
| Morning and afternoon check records | Fields include date, child name, item, quantity, and signature; statistical criteria are written in the header | Summarize record counts by week, check whether the total matches the statistical count, and list items missing signatures separately |
| Child health observation records | Fields include observation date, abnormality description, handling, and receipt; exception criteria are stated clearly | Extract abnormal entries and check whether their dates and quantities can be matched in the morning and afternoon check records |
| Request body and returned fields | Fields are consistent with the external interface agreement, and returned fields can be parsed by subsequent nodes | Use one sample request to compare the response, and check whether the field names in responseData match the agreement |
Three common errors
- Symptom: the activity name, quantity, or date of the same record does not match between the schedule and the morning and afternoon check records. Cause: the two materials are filled in separately and are not verified against the same date and criteria.
- Symptom: after the health observation record is updated, the progress table still shows the old version, and the statistical total deviates. Cause: the version was not synchronized, and an unupdated copy was read during summarization.
- Symptom: morning and afternoon check records or observation receipts lack signatures, but they are included in the total during statistics. Cause: signatures and receipts were not archived together with the records, and were not excluded during verification.
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 to confirm that Authorization and variables placeholders are parsed correctly.
Business test: use one week's records to verify the total, and see whether the criteria and exceptions are clearly stated.
- In the request preview, view the complete rendered URL and check whether path parameter placeholders are parsed into actual values.
- In the variables panel, check the source of each placeholder and confirm that request header names and value sources meet the external system's requirements.