What this category's data looks like
This page addresses the kindergarten operation behavior and quality self-assessment scenario, and the materials include three types: self-assessment reports, issue lists, and rectification plans. Self-assessment reports are produced by semester or year and contain items such as operating conditions, safety and hygiene, care and education, and faculty and staff, with fields including indicator name, self-assessment conclusion, supporting material number, filing date, and responsible person's signature. Issue lists are compiled from routine supervision or special inspections, with fields including issue description, involved class or position, discovery date, rectification deadline, and responsible person. Rectification plans are prepared item by item corresponding to the issue list, with fields including rectification measures, completion date, acceptance person's signature, and receipt number. The three types of materials play different roles in question-and-answer intake: the self-assessment report serves as the factual draft, the issue list serves as the to-do index, and the rectification plan serves as the basis for progress. The material update rhythm is filing at the beginning of the semester, supplementation during the semester, and consolidation at the end of the semester. The same record often shows inconsistencies in names, quantities, and dates because versions are not synchronized, so missing items must first be identified during intake before follow-up questions are asked.
Configuration and implementation checks
This step is executed by workflow nodes (user selection and branching), outputting branch directions and interaction status records. "Intake records and completed question items" are continued and completed by subsequent nodes according to the branch. 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 |
|---|---|---|
| Self-assessment report | Whether the indicator name, self-assessment conclusion, filing date, and responsible person's signature are consistent with the corresponding items in the issue list | Check the options and branch connections one by one in the node, trigger one viewing of the node status in the run record, reference the selection result variable in variables, and run a trial |
| Issue list | Whether the issue description, involved class or position, discovery date, and rectification deadline correspond item by item to the rectification plan | Reference nodeId in subsequent nodes to locate the specific branch, and check whether the names, quantities, and dates of the same record match across the two materials |
| Rectification plan | Whether the rectification measures, completion date, acceptance person's signature, and receipt number are complete and version-synchronized | Check the options and branch connections one by one in the node, trigger one viewing of the node status in the run record, and check whether items missing signatures or receipts are followed up with questions |
| User selection node | Each option corresponds to one branch, the interaction status is recorded, and the selection result variable has been passed to subsequent nodes | Check the options and branch connections one by one in the node, trigger one viewing of the node status in the run record, reference this variable in subsequent nodes, and run one trial |
Three common errors
- Phenomenon: The names, quantities, and dates of the same record do not match between the self-assessment report and the issue list. Cause: The two materials are filed separately, no cross-check is performed, and versions are not synchronized.
- Phenomenon: The rectification plan lacks the acceptance person's signature or receipt number, and this is not identified during intake. Cause: The missing-item judgment does not reach the material fields, and the follow-up step is skipped.
- Phenomenon: After selecting an option, the default branch is still taken, and the process stops after the interaction is completed. Cause: The options and branch connections are not checked one by one, and the selection result variable is not passed to subsequent nodes.
How to verify the setup
Feature acceptance: run trials for each option one by one, check the branch direction and interaction status in the run record, confirm that each option corresponds to one branch and that the selection result variable has been passed to subsequent nodes, and reference variables and nodeId in subsequent nodes to run one trial.
Business test: submit a question missing key information and see whether it asks follow-up questions before answering, and whether the follow-up content points to the missing fields, dates, or signatures in the self-assessment report, issue list, or rectification plan.
- Check the options and branch connections one by one in the node, trigger one viewing of the node status in the run record, and confirm that the interaction status is recorded and that the selection result variable has been passed to subsequent nodes.
- Cross-check the names, quantities, and dates of the same record in the self-assessment report, issue list, and rectification plan, mark items with unsynchronized versions or missing signatures or receipts, and trigger follow-up questions.