What this category's data looks like
Kindergarten operation behavior and quality self-assessment materials usually include a self-assessment report, an issue list, and a rectification plan, sourced from daily inspections within the kindergarten, class records, and weekly/monthly summaries. The update cadence advances weekly or monthly, and the fields cover activity name, date, quantity, responsible person, signature, and receipt. When entering workflow orchestration, the self-assessment report carries the overall conclusion and the explanation of statistical criteria, the issue list carries item-by-item issues and exception annotations, and the rectification plan carries follow-up actions and deadlines. The three types of materials each serve as objects of judgment and verification in the nodes, and the user's choice determines which type to verify first and whether to enter the next branch; the interaction state and branch direction are recorded for subsequent nodes to continue processing.
Configuration and implementation checks
This stage is executed by workflow nodes (user selection and branching), outputting branch direction and interaction state records. The progress table and the explanation of statistical criteria are completed by subsequent nodes continuing execution according to the branch. When a node is triggered, the conversation enters an interaction state and the workflow state is recorded; after the user completes the selection, execution continues along the branch corresponding to the chosen option.
| Object | Check | Verification action |
|---|---|---|
| Self-assessment report | Whether the name, quantity, date, and signature are consistent with the weekly records | Check the options and branch connections one by one in the node, run a trial and then view the node status in the run records, and pass the selection result variable to subsequent nodes for reference |
| Issue list | Whether the name, quantity, and date of the same record match across the two materials | Reference variables and nodeId to run a trial once, and check whether the exception items state the criteria in the header |
| Rectification plan | Whether the version is synchronized, and whether missing signatures or receipts are annotated | Reference the selection result variable in subsequent nodes and run a trial, and check the branch direction and interaction state records |
| Progress table and explanation of statistical criteria | Whether the record count and the statistical count match, and whether the criteria are written in the header | Use one week of records to verify the totals, and check whether the criteria and exceptions are clearly stated |
Three common errors
- Symptom: The name, quantity, and date of the same record do not match between the self-assessment report and the issue list. Cause: The two materials are entered separately and are not aligned using the same record number.
- Symptom: The rectification plan version is not synchronized, and the old version is still in circulation. Cause: After updating, the branch and state records were not re-checked in the node.
- Symptom: The self-assessment report is missing signatures or receipts, yet the statistical totals are still adopted. Cause: The criteria explanation was not written in the header, and exceptions were not annotated separately.
How to verify the setup
Acceptance of this feature: run trials option by option, check the branch direction and interaction state in the run records, confirm that the selection result variable has been passed to subsequent nodes, and check whether the references to variables and nodeId take effect.
Business test: use one week of records to verify the totals, and see whether the criteria and exceptions are clearly stated.
- Check the options and branch connections one by one in the node, trigger once, and then view the node status in the run records.
- Reference the selection result variable in subsequent nodes and run a trial once to confirm that the branch direction is consistent with the interaction state records.