What this category's data looks like
Kindergarten home-school co-education communication materials include commitment items and response times, descriptions of children's performance, classification of parents' requests, and notification delivery records. These materials are continuously generated through daily communication, sourced from class teacher records, parent feedback, and kindergarten notifications, with updates rolling on a daily or weekly basis. After entering the scheduled tasks and automation feature, commitment items and response times are used to determine whether responses form a closed loop, descriptions of children's performance are used to check whether the wording is consistent with observation records, classification of parents' requests is used to aggregate where feedback goes, and notification delivery records are used to confirm delivery status. Material versions must keep the current version unique, old versions traceable, and references updated in sync, forming a version ledger and change records.
Configuration and implementation checks
This part is executed by trigger configuration and tool nodes (scheduled capability is not in the tool introduction), outputting trigger records and execution results. The "version ledger and change records" are completed by business processing according to the records or by supplementary runs.
| Object | Check | Verification action |
|---|---|---|
| Commitment items and response times | Whether the commitment is responded to within the agreed time, and whether the response time corresponds to the commitment time | Check the trigger records and execution results, see whether a response record is generated for the commitment item after the scheduled time, and whether unresponded items enter supplementary runs |
| Descriptions of children's performance | Whether the wording is consistent with the observation records, and whether the described content can be traced back to the original observation records | Compare the current version with the old version, and check whether the description fields and observation record fields are updated in sync |
| Classification of parents' requests | Whether the feedback has been classified, and whether the classification result matches the request content | Check whether request items in the trigger records are aggregated by classification, and whether unclassified items are handled in supplementary runs |
| Notification delivery records | Whether the notification is delivered, and whether the delivery status corresponds to the trigger execution results | Check the delivery records in the execution results, confirm execution at the scheduled time and only once, and whether undelivered items are handled in supplementary runs |
Three common errors
- Symptom: the commitment is not responded to at the scheduled time, and the parent asks again. Cause: the trigger configuration is not connected to the corresponding tool node, or no execution record is generated after the scheduled time, and business processing does not perform supplementary runs according to the records.
- Symptom: descriptions of children's performance do not match the observation records, and wording conflicts between versions. Cause: after changing one piece of content, the old version leaves no trace, references are not updated in sync, and the current version is not unique.
- Symptom: parents' requests are not classified, and where the feedback goes is unclear. Cause: the classification field is not written along with the trigger execution results, business processing does not aggregate according to the records, and supplementary runs miss items.
How to verify the setup
Acceptance of this feature: look at the trigger records and execution times, confirm execution at the scheduled time and only once, that the trigger is connected to the corresponding tool node, and that when no summary is needed it is connected at the end of the tool.
Business test: change one piece of content, see whether the version number and references are updated in sync, and check that the current version is unique, old versions are traceable, and references are synchronized.
- Check the process connections and trigger records, confirm that the trigger conditions are connected to the corresponding tool node, that the tool introduction clearly states when execution should occur, and that the termination node is connected at the end of steps that do not need a summary.
- Check the version ledger and change records, confirm that after changing one piece of content the version number and references are updated in sync, and whether unresponded commitments, unclassified requests, and undelivered notifications are handled in supplementary runs according to the records.