What this category's data looks like
Degree conferral and certificate information reporting involves three types of materials: degree application forms, thesis review forms, and defense resolutions. They carry application information, review conclusions, and defense voting fields, respectively, including dates, signatures, and receipts. The materials come from archiving at each training stage, and the update cadence advances with the review, defense, and degree committee milestones. The name, quantity, and date of the same record must remain consistent across different materials. When entering this function, the degree application form provides application and qualification fields, the thesis review form provides review opinion and result fields, and the defense resolution provides voting and conclusion fields. Together, the three form the basis for comparison in the version ledger and change records. The old version must be traceable, the current version must be unique, and references must be updated in sync.
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 the records or by catch-up runs. After changing one piece of content, check whether the version number and references are updated in sync.
| Object | Check | Verification action |
|---|---|---|
| Degree application form | Whether the fields, dates, and signatures are consistent with the review form and defense resolution | Check the application information fields, dates, and signature fields, verify whether the receipts are complete, and compare the name and quantity of records with the same name |
| Thesis review form | Whether the review conclusion fields and dates correspond to the application form and defense resolution | Check the review opinions, results, and dates, verify the signatures and receipts, and confirm that the version number and references point to the current version |
| Defense resolution | Whether the voting and conclusion fields, dates, and signatures match the other materials | Check the voting records, conclusions, and dates, verify the signatures and receipts, and confirm that the old version is traceable and references are in sync |
| Version ledger and change records | The current version is unique, the old version is traceable, and references are in sync | After changing one piece of content, check whether the version number and references are updated in sync, and record the trigger records and execution time |
Three common errors
- Symptom: The name, quantity, and date of the same record do not match between the degree application form and the defense resolution, and it is impossible to determine which one prevails during verification. Cause: The materials are archived separately, and changes are not written back to the ledger.
- Symptom: The thesis review form has been updated, but the defense resolution still references the old version, and the reference is not in sync. Cause: The version is not synchronized, and the old version and the current version coexist without being marked.
- Symptom: The defense resolution lacks a signature or receipt and is returned for correction during reporting. Cause: Signatures and receipts are not included in the change record verification items and are missed during catch-up runs.
How to verify the setup
This function's acceptance: check the trigger records and execution time, confirm that execution occurs on time and only once, and that there is no failure to execute on time or repeated execution of the same task.
Business test: change one piece of content, check whether the version number and references are updated in sync, whether the old version is still traceable, and record the number of references and the tokens of the reference text separately.
- Check the trigger records and execution results, confirm that the trigger has been connected to the corresponding tool node, and inspect the process connections and trigger records.
- Check the tool introduction fields, confirm that it clearly states when execution should occur; when no summary is needed, confirm that the tool call termination node is connected at the end of the tool.