What this category's data looks like
Kindergarten home-school co-education communication materials come from class notices, child observation records, parent request registrations, and multilingual parallel texts, with an update rhythm that rolls along with weekly plans and activity notices. When materials enter the workflow, each has a different role: notices and observation records provide terminology sources, parent request registrations provide classification clues, and multilingual parallel texts handle the verification of translated names referring back to the original text. The unified terminology list and parallel text are finished products formed after subsequent nodes continue execution along branches, and are used for external release. Field characteristics include committed matters and response times, descriptions of child performance, parent request classifications, and notice delivery status. Multilingual materials and terminology processing require first fixing terminology wording, then referring back to the original text item by item, to avoid the same term appearing with multiple translated names in different notices.
Configuration and implementation checks
This stage is executed by workflow nodes (user selection and branches), outputting branch directions and interaction status records. The "unified terminology list and parallel text" is then completed by subsequent nodes continuing execution along branches. 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 |
|---|---|---|
| Unified terminology list and parallel text | The same term is consistent throughout, and translated names can refer back to the original text | Check options and branch connections one by one in the node, use variables to reference the selection result variable and run a trial once, and check the branch direction and interaction status in the run record |
| Class notices and child observation records | Whether committed matters and response times, and descriptions of child performance, match the observation records | Extract committed matters from notices and compare them item by item with observation records, and check the node status and branch direction corresponding to nodeId |
| Parent request registrations and multilingual parallel texts | Whether parent request classifications and notice delivery cover all languages | Check item by item according to request classification whether the translated names in the parallel text can refer back to the original text, record the number of array items and the tokens of the referenced text; for the reference limit, check only the tokens of the referenced text |
Three common errors
- Phenomenon: A committed matter appears in a notice but no response time is seen. Cause: Parent request classifications are not associated with committed matters, feedback is not categorized, and the workflow branch does not cover that request type.
- Phenomenon: Descriptions of child performance are inconsistent with observation records. Cause: When translated names in the multilingual parallel text refer back to the original text, they were not checked item by item, and the terminology list did not fix a single wording.
- Phenomenon: After selecting an option, the default branch is still followed. Cause: Options and branch connections were not checked one by one, and the selection result variable was not correctly referenced in subsequent nodes.
How to verify the setup
Acceptance of this feature: run trials for each option one by one, check the branch direction and interaction status in the run record, and confirm that variables and nodeId correspond consistently with the records.
Business test: sample three terms to check whether their wording is consistent throughout, and verify whether the translated names can refer back to the original text.
- Check options and branch connections one by one in the node, and confirm that each option corresponds to one branch.
- Reference the selection result variable in subsequent nodes and run a trial once, then check the node status and branch direction in the run record.