What this category's data looks like
This category's data looks like Kindergarten childcare daily life management involves three types of materials: daily life schedule, morning and afternoon check records, and child health observation records. The daily life schedule comes from the kindergarten's childcare plan, updated at the beginning of each semester, and includes activity names, time periods, responsible persons, and signature fields; morning and afternoon check records are filled in daily by class teachers, including child's name, date, body temperature, oral and hand examination results, handling opinions, and signature; child health observation records are filled in by health care workers as needed, including observation date, symptom description, water intake, eating and sleeping conditions, follow-up measures, and receipt. When these three types of materials enter workflow orchestration, the daily life schedule serves as the progress baseline, morning and afternoon check records serve as the basis for daily check-ins, and health observation records serve as the source of exception items. Field characteristics are concentrated in date, child's name, activity or symptom name, quantity, signature, and receipt, with an update rhythm that is a mix of daily updates and semester updates.
Configuration and implementation checks
This step is executed by workflow nodes (user selection and branching), outputting branch directions and interaction status records. The "Progress table and statistical scope description" is continued and completed by subsequent nodes according to the branch. When the user selection node is triggered, the conversation enters an interactive state and records the workflow status. After the user completes the selection, execution continues along the branch corresponding to the selected option.
| Object | Check | Verification action |
|---|---|---|
| Daily life schedule | Whether activity names, dates, and signatures correspond item by item with the morning and afternoon check records | Check the options and branch connections one by one in the node, reference variables and nodeId, and trigger once to view the node status in the run records |
| Morning and afternoon check records | Whether child's name, quantity, date, and signature are consistent with the health observation records | Reference the selection result variable in subsequent nodes and run a trial once, checking the name and quantity of the same record in the two materials |
| Child health observation records | Whether symptom name, observation date, follow-up measures, and receipt are complete | Check whether the versions are synchronized, and confirm whether entries missing signatures or receipts enter the exception branch |
| Progress table and statistical scope description | Whether the number of records matches the statistical count, and whether the scope is written in the header | Use one week of records to verify the total, see whether the scope and exceptions are clearly stated, and check the branch direction and interaction status records |
Three common errors
- Phenomenon: The child's name or quantity in the same morning and afternoon check record does not match between the daily life schedule and the health observation record. Cause: The two materials are maintained separately, and no field-level comparison is performed in the workflow.
- Phenomenon: The daily life schedule has been updated, but the morning and afternoon check records are still filled in according to the old version. Cause: The versions are not synchronized, and the workflow does not record the material version and effective date.
- Phenomenon: Health observation records are missing signatures or receipts, but they are still included in the total during statistics. Cause: The scope is not written in the header, and exception items do not go through an independent branch.
How to verify the setup
Acceptance of this function: run trials for each option one by one, check the branch direction and interaction status in the run records, and confirm that variables and nodeId have been passed to subsequent nodes.
Business test: use one week of records to verify the total, see whether the scope and exceptions are clearly stated, and whether the number of records matches the statistical count.
- Check the options and branch connections one by one in the node, and trigger once to view the node status in the run records.
- Reference the selection result variable in subsequent nodes and run a trial once, checking whether the process continues after the interaction is completed.