What this category's data looks like
This category's data covers three types of materials: thematic class meeting plans, comprehensive student quality records, and home visit records. Thematic class meeting plans include activity objectives, procedures, and signature fields; comprehensive student quality records include evaluation dimensions, dates, and homeroom teacher signatures; home visit records include home visit time, student name, and parent receipt. Material sources include grade group submissions, homeroom teacher entries, and moral education office archiving, with an update rhythm of planning at the start of the semester, adjustments during the semester, and consolidation at the end of the semester. When entering the scheduled tasks and automation feature, thematic class meeting plans serve as the template version source, comprehensive student quality records serve as the data reference source, and home visit records serve as the receipt verification source. In terms of field characteristics, three types of information—dates, quantities, and signatures—must be consistent across materials; the name and quantity of the same record in two materials may not match, versions not being synchronized leads to referencing an old version, and missing signatures or receipts make records incomplete.
Configuration and implementation checks
This step is executed by trigger configuration and tool nodes (scheduling capability is not in the tool introduction), outputting trigger records and execution results. The version ledger and change records are completed by business processing according to records or by supplementary runs.
| Object | Check | Verification action |
|---|---|---|
| Thematic class meeting plan | Whether the name, quantity, and date of the same plan are consistent in the two materials; whether the signature field is complete | Check the activity date and archive date in the plan; compare the signature field with the receipt; check whether the version number and reference are synchronized |
| Comprehensive student quality record | Whether the evaluation dimensions, date, and homeroom teacher signature correspond to the home visit record; whether the quantity is consistent | Check the date and signature in the record; compare the student name and quantity in the home visit record; check whether the old version is traceable |
| Home visit record | Whether the home visit time, student name, and parent receipt are consistent with the comprehensive quality record; missing signature or receipt | Check the receipt signature; compare the date and quantity; check whether the reference points to the current version |
| Version ledger and change records | The current version is unique, the old version is traceable, and references are synchronized; whether the trigger record and execution result are complete | View the trigger record and execution time; check the version number and reference relationships in the change records; confirm that it executes only once |
Three common errors
- Symptom: It did not execute at the scheduled time. Cause: The trigger configuration is not connected to the corresponding tool node, or the tool introduction does not clearly state when it should execute.
- Symptom: After execution, it is summarized again by the model. Cause: When summarization is not needed, a tool call termination node is not connected at the end of the tool.
- Symptom: The same task executes repeatedly. Cause: The name, quantity, and date of the same record in the two materials do not match, versions are not synchronized, and signatures or receipts are missing.
How to verify the setup
Acceptance of this feature: Check the trigger record and execution time to confirm that it executes at the scheduled time and only once; check the tool introduction fields and where the termination node is connected.
Business test: Change one piece of content and see whether the version number and reference are updated synchronously; check whether the old version is traceable and whether missing signatures or receipts are completed.
- Check the process connections and trigger records to confirm that the trigger has been connected to the corresponding tool node.
- Check the tool introduction fields and clearly state when it should execute; when summarization is not needed, connect a tool call termination node at the end of the tool.