What this category's data looks like
Kindergarten home-school co-education communication materials come from commitments and response times formed in the daily operation of the kindergarten, descriptions of children's performance, classification of parents' demands, and notification delivery records. The update rhythm follows the progress of the semester and daily class affairs. Commitments and response times are updated during teacher handover, descriptions of children's performance are synchronized with observation records, parents' demands are classified and aggregated by feedback channel, and notification delivery is based on publication and confirmation nodes. When these materials enter workflow orchestration, each has a different role: commitments and response times are used to determine whether a response has been given, descriptions of children's performance are used to check whether they are consistent with observation records, classification of parents' demands is used to confirm whether feedback has been categorized, and notification delivery is used to confirm whether it has been reached. Field characteristics include timestamps, class identifiers, child identifiers, demand types, delivery status, and original text location.
Configuration and implementation checks
This step is executed by workflow nodes (user selection and branching), outputting branch directions and interaction status records. "Evidence items that can refer back to the original text" are completed by subsequent nodes continuing execution 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 |
|---|---|---|
| Commitments and response times | Whether the commitment has been responded to, and whether the response time falls within the agreed range | Check the options and branch connections one by one in the node, check the timestamps of the commitment items and response records, and confirm whether unresponded items enter the to-do branch |
| Descriptions of children's performance | Whether the statement is consistent with the observation record | Compare the performance descriptions with the observation records one by one, confirm that the description source can refer back to the original text location, and mark inconsistent items to enter the review branch |
| Classification of parents' demands | Whether the feedback has been categorized and whether the category matches the demand content | Check the demand classification field against the original feedback text, confirm that uncategorized items enter the classification branch, and that categorized items reference variables to record the classification result |
| Notification delivery | Whether the delivery status can be checked and whether it is consistent with the publication record | Check the delivery status against the publication record, confirm that undelivered items enter the resend branch, and that delivered items reference nodeId in subsequent nodes to locate the original text |
Three common errors
- Phenomenon: commitments receive no response in the reply. Cause: commitment items are not bound to the response time field, and the branch does not enter to-do processing.
- Phenomenon: descriptions of children's performance are inconsistent with observation records. Cause: the description source does not refer back to the original text, and the review branch is not triggered.
- Phenomenon: parents' demands are not categorized or are miscategorized. Cause: the demand classification field is not synchronized with the original feedback text, and the classification branch is not executed.
How to verify the setup
Acceptance of this feature: run trials option by option, check the branch directions and interaction status in the run records, confirm that each option corresponds to one branch, that the process continues after the interaction is completed, and that the same session does not repeatedly enter the interaction.
Business test: ask a cross-material evidence question, see whether the answer gives a source that can be referred back to, and check whether the source comes from this kindergarten's materials, whether the version is current, and whether the item matches the original text.
- Check the options and branch connections one by one in the node, confirm that each option corresponds to one branch, and check whether
variableshas been passed to subsequent nodes. - Trigger a user selection node once, view the node status and
nodeIdin the run records, and confirm that after the interaction is completed, execution continues along the branch corresponding to the selected option.