What this category's data looks like
This page addresses the kindergarten home-school co-education communication scenario. Materials include a one-week progress record table, statistical scope notes, a ledger of commitments and response times, child performance descriptions and observation records, a parent request classification list, and notification delivery receipts. Sources are daily class communication and the home-school contact book, with updates summarized weekly and reviewed monthly. When entering the workflow orchestration feature, the progress record table and statistical scope notes serve as the business deliverables to be verified, commitments and response times are used to check whether responses are closed-loop, child performance descriptions are used to compare whether the wording matches the observation records, parent request classification is used to check whether feedback is categorized, and notification delivery is used to confirm reach. Each material serves only as input basis for branch direction and interaction state records in nodes, and does not make choices for the user.
Configuration and implementation checks
This step is executed by workflow nodes (user selection and branching), outputting branch direction and interaction state records. The progress table and statistical scope notes are continued and completed by subsequent nodes according to the branch. When a 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 |
|---|---|---|
| Progress record table | Whether the record count matches the statistical count, and whether the scope is written in the header | Verify the header scope and total row item by item, use one week's records to verify the total, and check whether exceptions are clearly stated |
| Statistical scope notes | Whether the four dimensions—commitments and response times, child performance descriptions, parent request classification, and notification delivery—correspond one by one | Verify options and branch connections one by one in the node, and reference variables in a subsequent node to run a trial once |
| Ledger of commitments and response times | Whether every commitment has a response time, and whether unresponded items are listed separately | Compare response times item by item against commitments, and check whether unresponded items are included in the exception notes |
| Parent request classification list | Whether feedback is assigned to the corresponding category, and whether notification delivery is verifiable | Verify classification labels and delivery records, and check whether uncategorized feedback is listed separately |
Three common errors
- Phenomenon: A commitment has an entry in the record table but no response time. Cause: The response time was not written in sync with the commitment, and it was counted as responded in the total during statistics, causing the record count and statistical count to mismatch.
- Phenomenon: Child performance descriptions do not match the wording in the observation records. Cause: The description was taken from hearsay rather than the day's observation records, and the scope was not written in the header, so it cannot be determined which document prevails during verification.
- Phenomenon: Parent requests are not categorized, and notification delivery is not marked item by item. Cause: Feedback was not placed according to the classification list when entering statistics, and delivery status was not linked to records, resulting in gaps in the weekly report total.
How to verify the setup
Feature acceptance: Run trials option by option, check the branch direction and interaction state in the run records, and confirm that the node state corresponding to nodeId is recorded and that the selection result variable has been passed to subsequent nodes.
Business testing: Use one week's records to verify the total, see whether the scope and exceptions are clearly stated, and confirm that the record count matches the statistical count and that the scope is written in the header.
- Verify options and branch connections one by one in the node, confirm that each option corresponds to one branch, and avoid still following the default branch after selecting an option.
- Reference
variablesin a subsequent node and run a trial once to check whether the process continues downward after the interaction is completed, and whether the same session repeatedly enters the interaction.