What this category's data looks like
Materials for kindergarten home-school co-education communication come from class notices, child observation records, parent request registrations, and commitment item lists. They are updated daily and summarized weekly, with fields including commitment items and response times, descriptions of child performance, parent request categories, and notice delivery status. When the materials enter workflow orchestration, the user first selects nodes to determine branches, and then subsequent nodes draft signable material drafts and handover records. The responsible person, version, and date are written in along with the branch, and missing items are blocked at the node.
Configuration and implementation checks
This stage is executed by workflow nodes (user selection and branching), outputting branch directions and interaction state records. The signable material drafts and handover records are then 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 |
|---|---|---|
| Commitment items and response times | Whether each commitment is responded to and the response time falls within the agreed interval | Check the options and branch connections one by one in the node, and reference the variables values to compare the commitment list with the response records |
| Descriptions of child performance | Whether the statements are consistent with the observation records and traceable to record entries | Reference the selection result variable in subsequent nodes and run a trial once, then check the description against the observation record fields |
| Parent request categories | Whether requests are classified into existing categories and the categories correspond to the notice delivery status | Trigger once and check the node status in the run records, then verify the category labels and delivery fields |
| Notice delivery | Whether the delivery status is written in along with the branch and the responsible person is clear | Check the options and branch connections in the node, and confirm that the branch corresponding to nodeId writes in the delivery and responsible person |
Three common errors
- Phenomenon: Commitment items are issued without being responded to. Cause: The options and branch connections do not cover the unresponded case, and after the interaction state is recorded, the default branch is still followed.
- Phenomenon: Descriptions of child performance do not match the observation records. Cause: Subsequent nodes do not reference the selection result variable, and the branch direction is disconnected from the material fields.
- Phenomenon: Parent requests are handed over without being categorized. Cause: The category field is not blocked at the node, and missing items do not trigger an interaction state review.
How to verify the setup
Acceptance of this feature: run trials for each option one by one, check the branch directions and interaction states in the run records, and confirm that variables and nodeId can be referenced in subsequent nodes.
Business test: draft one according to the template and complete one handover, and see whether missing items are blocked.
- Check the options and branch connections one by one in the node, and confirm that each option corresponds to one branch and the interaction state is recorded.
- Reference the selection result variable in subsequent nodes and run a trial once, then check whether the branch direction and interaction state records are consistent.