What this category's data looks like
Kindergarten home-school co-education communication involves four types of materials: commitments and response times, descriptions of children's performance, classification of parents' requests, and notification delivery. Sources of these materials include teachers' daily observation records, requests and receipts submitted by parents, and kindergarten notification templates and delivery statuses. The update cadence is daily: observation records are generated with activities, requests and receipts are updated as parents submit them, and notifications are published according to activity cycles. When materials enter workflow orchestration, each plays a different role: commitments and response times serve as the source of visible content for the external entry point, descriptions of children's performance serve as the basis for determining the scope visible to parents, classification of parents' requests serves as input for branch directions, and notification delivery serves as the object of verification for interaction status records. Authorized access and external services require that visitor identity match the visible scope, and unauthorized content must not be visible.
Configuration and implementation checks
This stage is executed by workflow nodes (user selection and branching), outputting branch directions and interaction status records. The externally available entry point and authorization scope are completed by subsequent nodes continuing execution according to the branch. When the user selection node is triggered, the conversation enters an interaction state and records the workflow state; 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 commitments receive a response within the agreed time, and whether unresponded items enter the to-do branch | Check options and branch connections one by one in the user selection node; after a trial run, inspect the branch directions and interaction status in the run records |
| Descriptions of children's performance | Whether the statements are consistent with the observation records, and whether inconsistent items are flagged and routed to the review branch | Reference the selection result variable variables in subsequent nodes, and run a trial once to check whether the variable is passed in |
| Classification of parents' requests | Whether parents' requests enter the corresponding branch by classification, and whether unclassified items go to the default branch | Check options and branch connections one by one in the node, and confirm that each option corresponds to one branch |
| Notification delivery | Whether notifications are delivered according to the visible scope, and whether restricted identities see only authorized content | Access once with a restricted identity, and check the nodeId and interaction status in the run records |
Three common errors
- Symptom: Commitments do not receive a response within the agreed time, and are only seen after the parent submits again. Cause: Commitments do not enter the to-do branch, and response time is not used as a branch condition.
- Symptom: Descriptions of children's performance are inconsistent with the observation records, and the statements seen by parents differ from the teacher's records. Cause: Performance descriptions are not checked for consistency against observation records and directly enter the external entry point.
- Symptom: Parents' requests are not classified, all go to the default branch, and feedback does not flow by category. Cause: Request classification is not used as an option in the user selection node, and branch directions do not match request categories.
How to verify the setup
Feature acceptance: run trials option by option, and 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 enter the interaction repeatedly.
Business testing: access once with a restricted identity and see whether the visible scope matches the settings; unauthorized content must not be visible, and the notification delivery scope must be consistent with the authorization scope.
- In the user selection node, check options and branch connections one by one, confirm that each option corresponds to one branch, and run a trial once to inspect the branch directions and interaction status in the run records.
- In subsequent nodes, reference the selection result variable
variables, and run a trial once to confirm that the variable has been passed in; at the same time, check whether the interaction status record corresponding tonodeIdis complete.