What this category's data looks like
Kindergarten operation behavior and quality self-assessment materials include three types: self-assessment reports, issue lists, and rectification plans. The self-assessment report is used to provide an overall statement of the kindergarten's operation behavior and quality status; the issue list enumerates items to be improved one by one; the rectification plan specifies responsibilities, measures, and deadlines. The three types of materials come from the kindergarten's daily records, inspection records, and meeting minutes, and their update cadence typically advances by semester or rectification cycle. Field characteristics center on names, quantities, dates, and signatures: whether the name of the same item is consistent between the self-assessment report and the issue list, whether the quantities match, whether the dates connect, and whether the rectification plan has signatures or acknowledgments. When materials enter workflow orchestration, the self-assessment report assumes the role of overall summary and basis, the issue list assumes the role of item verification, and the rectification plan assumes the role of measures and deadlines. The version ledger and change records need to map the version numbers, change times, change contents, and reference locations of the three types of materials, ensuring that the current version is unique, old versions are traceable, and references are synchronized.
Configuration and implementation checks
This step is executed by workflow nodes (user selection and branches), outputting branch directions and interaction state records. The "version ledger and change records" are then completed by subsequent nodes continuing execution along the branch. When the user selection 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 |
|---|---|---|
| Self-assessment report | Whether the name, date, and signature are consistent with the issue list | Check the item names, dates, and signature fields in the report, and verify the options and branch connections one by one in the node |
| Issue list | Whether the quantity and dates match the rectification plan | Compare the issue quantity, rectification dates, and acknowledgments one by one, and trigger one check of the node status in the run records |
| Rectification plan | Whether responsibilities, measures, deadlines, and signatures are complete | Check the responsible persons and deadlines in the plan, reference the selection result variable in subsequent nodes, and run a trial once |
| Version ledger and change records | The current version is unique, old versions are traceable, and references are synchronized | After changing one piece of content, check whether the version number and reference locations are updated synchronously |
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 types of materials are maintained separately, without field-level comparison and unification.
- Symptom: The version is not synchronized, and the old version is still referenced. Cause: After changes, the version ledger and reference locations were not updated, so the current version is not unique.
- Symptom: The rectification plan lacks signatures or acknowledgments. Cause: The material circulation step did not set up signature confirmation and acknowledgment retention.
How to verify the setup
This feature acceptance: run trials option by option, check the branch directions and interaction states in the run records, and confirm that variables, nodeId, and the selection result variable have been passed to subsequent nodes.
Business test: change one piece of content and see whether the version number and references are updated synchronously
- Verify the options and branch connections one by one in the node, and trigger one check of 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 directions are consistent with the recorded interaction states