What this category's data looks like
This page centers on kindergarten operation behavior and quality self-assessment, placing three types of materials—self-assessment reports, issue lists, and rectification plans—into the same workflow. Self-assessment reports are formed by semester and contain indicator scores, factual descriptions, and signature pages; issue lists are numbered by item and record name, quantity, date, and responsible person; rectification plans correspond to issue numbers and list measures, completion deadlines, and receipts. The three types of materials update at different rhythms: self-assessment reports are replaced as a whole with the assessment cycle, while issue lists and rectification plans update on a rolling basis with rectification progress. When materials enter this feature, the self-assessment report takes the role of the overall basis repository, the issue list takes the role of item index, and the rectification plan takes the role of status and receipt. Field characteristics are concentrated in name, quantity, date, signature, and receipt; when referencing across materials, the number and version of the same record must first be aligned, then it is judged whether the basis comes from this kindergarten's materials, whether it is the current version, and whether it can point back to the original text.
Configuration and implementation checks
This step is executed by workflow nodes (user selection and branches), outputting branch directions and interaction state records. "Basis items that can point back to the original text" are continued and completed by subsequent nodes according to the branches. When the user selection node is triggered, the conversation enters the 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 | Fields, dates, and signatures must be consistent with the assessment cycle, and names and quantities must match the original text | Check the report cover date, indicator item numbers, and signature page, and confirm whether it is the current version |
| Issue list | Item numbers, names, quantities, dates, and responsible persons must correspond to the self-assessment report | Compare the same record in the list and the report item by item, and mark inconsistencies in name, quantity, and date |
| Rectification plan | Measures, completion deadlines, and receipts must correspond to the issue list items and must not lack signatures | Check the receipt and signature of each measure in the plan, and confirm that the version is synchronized with the list |
| User selection node | Each option corresponds to one branch, and the selection result variable has been passed to subsequent nodes | Check the options and branch connections one by one in the node, run a test and then view the branch directions and interaction state in the run record, and reference variables and nodeId in subsequent nodes to verify the passing |
Three common errors
- Symptom: The name, quantity, or date of the same record does not match between the self-assessment report and the issue list. Cause: The two materials are entered separately, lacking unified numbering and version alignment.
- Symptom: An item referenced by the rectification plan has already changed in the latest self-assessment report, but the answer is still given according to the old version. Cause: The version is not synchronized, and the materials were not re-entered into the workflow after updating.
- Symptom: The issue list or rectification plan lacks a signature or receipt, and the basis item cannot point back to the original text. Cause: The signature page and receipt record were not completed during the material circulation step.
How to verify the setup
Feature acceptance: run a test for each option one by one, check the branch directions 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: ask a cross-material basis question, see whether the answer gives a traceable source, and check that the tokens of the quoted text and the number of array items are recorded separately.
- In the user selection node, check the options and branch connections one by one; after running a test, view the node status and branch directions in the run record.
- Reference
variablesandnodeIdin subsequent nodes and run a test once to confirm that the selection result variable has been passed correctly.