What this category's data looks like
The common materials for kindergarten operation behavior and quality self-assessment include self-assessment reports, issue lists, and rectification plans. Self-assessment reports are produced by semester or academic year and contain sections such as operating conditions, safety and hygiene, care and education, and faculty and staff. The issue list itemizes issue descriptions, responsible persons, and discovery dates one by one. The rectification plan provides measures, completion deadlines, and signature fields corresponding to the issues. After the three types of materials enter the workflow, their roles differ: the self-assessment report serves as the source material providing original records, the issue list is responsible for aggregating anomalous items, and the rectification plan carries the disposition destination and receipt. Material versions are updated with inspection batches, and names, quantities, dates, and signatures in the fields must be aligned across materials; any inconsistency in any one place creates an anomaly pending review.
Configuration and implementation checks
This step is executed by workflow nodes (user selection and branching), outputting branch directions and interaction state records. When the user selection node is triggered, the conversation enters an interactive state and records the workflow state; after the user completes the selection, execution continues along the branch corresponding to the selected option. The "anomaly list and review conclusion" is then completed by subsequent nodes continuing execution according to the branch.
| Object | Check | Verification action |
|---|---|---|
| Self-assessment report | The names, quantities, and dates of the original records in the report must correspond item by item with the issue list, and the signature fields must be complete. | Within the node, reference variables and nodeId, pair the report entries with the issue list entries in a trial run, and check the branch direction in the run record. |
| Issue list | The list entries must be traceable to the specific page or entry in the self-assessment report, and the responsible person, discovery date, and rectification plan must be consistent. | Run trials option by option, and check whether the node status and selection result variables in the run record are passed to subsequent nodes. |
| Rectification plan | The measures, completion deadlines, signatures, and receipts in the plan must align with the same entry in the issue list, and the version number must be consistent. | Reference the selection result variable in a subsequent node and run a trial once, and check whether the plan entries continue execution along the branch. |
Three common errors
- Symptom: The names and quantities of the same record do not match between the self-assessment report and the issue list. Cause: The two materials were filled in by different people and were not backfilled according to the same original record.
- Symptom: The rectification plan has been updated, but the issue list is still the old version, and the date and signature fields are missing. Cause: The versions were not synchronized, and the receipt was not collected.
- Symptom: After selecting an option, the default branch is still followed, and the process stops after the interaction is completed. Cause: The options and branch connections were not checked one by one, or the same session repeatedly entered the interaction.
How to verify the setup
Acceptance for this feature: run trials option by option, check the branch direction and interaction state in the run record, and confirm that each option corresponds to one branch and that the selection result variable has been passed to subsequent nodes.
Business test: create an anomaly record, see whether it can be traced to the source material, and check that the anomaly is supported by original records and has the reviewer's signature.
- In the node, check the options and branch connections one by one, trigger once, and view the node status in the run record.
- Reference the selection result variable in a subsequent node and run a trial once, and check whether the plan entries continue execution along the branch.