What this category's data looks like
This category of data involves three types of materials: training notices, credit recognition forms, and attendance rosters. Training notices come from education authorities or training organizers and contain the training name, start and end dates, class hours, and credit value; credit recognition forms are filled out by the teacher's school or training unit and contain the teacher's name, ID number, training program, recognized credits, and signature field; attendance rosters are provided by the training organizer and contain name, unit, attendance date, sign-in, and receipt. The three types of materials play different roles in version and change maintenance: the training notice is the source of the version, the credit recognition form is the business result, and the attendance roster is the process evidence. In terms of update rhythm, notices are issued with training batches, recognition forms are summarized by semester or year, and rosters are generated by class session. In terms of field characteristics, the name, quantity, and date of the same record in the three materials must be consistent, the version number and reference relationships must be maintained in sync, and signatures and receipts must not be missing.
Configuration and implementation checks
This step is executed by the trigger configuration and tool node (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 catch-up runs. Whether the tool call is executed is decided by the model based on the tool introduction; when the model does not need to summarize again, a tool call termination node can be connected at the end of the tool to end this call.
| Object | Check | Verification action |
|---|---|---|
| Training notice | Field completeness: training name, start and end dates, class hours, credit value, signature field; whether dates and signatures are complete | Check the fields and signatures of the original notice, compare whether the version number is consistent with the current version, and check whether the recognition forms and rosters referencing this notice are updated in sync |
| Credit recognition form | Field consistency: teacher name, ID number, training program, recognized credits, signature; whether the name, quantity, and date match the training notice and attendance roster | Extract recognition form records, compare name, credits, and date item by item with the notice and roster, check whether signatures and receipts are missing, and confirm whether a catch-up update has been run when the version was not synced |
| Attendance roster | Process evidence: name, unit, attendance date, sign-in, receipt; whether the date and quantity match the notice and recognition form | Check the roster sign-in and receipt, compare the notice date and recognized credits, check whether the name, quantity, and date of the same record in the three materials are consistent, and whether the version references are in sync |
Three common errors
- Symptom: the name, quantity, and date of the same record do not match between the training notice and the credit recognition form. Cause: the version is not synced, old-version materials are still referenced, and changes are not written back to the ledger.
- Symptom: the attendance roster lacks signatures or receipts, and the signature field of the credit recognition form is blank. Cause: the material collection step is not closed-loop, catch-up runs are not executed according to records, and evidence is omitted.
- Symptom: execution does not occur at the scheduled time, or after execution the model summarizes it again, causing the same task to be executed repeatedly. Cause: the trigger configuration is not connected to the corresponding tool node, and the termination node is not connected at the end of the tool.
How to verify the setup
This feature acceptance: check the trigger records and execution time, and confirm execution occurs at the scheduled time and only once.
Business test: change one piece of content and see whether the version number and references are updated in sync.
- Check the process connections and trigger records, confirm the trigger is connected to the corresponding tool node, and check whether the introduction field clearly states when it should execute.
- Check which step the termination node is connected to, confirm that when no summary is needed it is connected at the end of the tool; compare the version ledger and change records, and confirm the current version is unique, old versions are traceable, and references are in sync.