What this category's data looks like
Grade entry and credit recognition involves three types of materials: transcripts, deferred examination applications, and makeup examination arrangements. Transcripts come from exports of the academic affairs system and record course names, credits, grades, and signatures; deferred examination applications are submitted by students and reviewed by departments, and include application dates and receipts; makeup examination arrangements are published by examination affairs and include makeup examination dates, locations, and invigilator signatures. In terms of update cadence, transcripts are released centrally at the end of the semester, deferred examination applications are generated on a case-by-case basis at any time, and makeup examination arrangements are finalized one week before the examination. When materials enter scheduled tasks and automation, transcripts serve as the main record driving credit recognition, while deferred examination applications and makeup examination arrangements serve as change sources, triggering the reconstruction of the version ledger and change records to ensure that the current version is unique, old versions are traceable, and references are synchronized.
Configuration and implementation checks
This part is executed by trigger configuration and tool nodes (scheduling capability is not in the tool introduction), and outputs trigger records and execution results. The version ledger and change records are completed by business processing according to the records or by supplementary runs. Tool invocation is decided by the model based on the tool introduction whether to execute; when the model is not needed to summarize again, a tool invocation termination node can be connected at the end of the tool to end this invocation.
| Object | Check | Verification action |
|---|---|---|
| Transcript | Whether the fields, dates, and signatures are consistent with the deferred examination application and makeup examination arrangement | Compare course names, credits, grades, signatures, and dates, register discrepancies, and write them back to the ledger |
| Deferred examination application | Whether the application date and receipt are complete, and whether they match the same record as the transcript | Check the application date, review signature, and receipt, confirm that references are synchronized, and then update the knowledge base |
| Makeup examination arrangement | Whether the makeup examination date, location, and invigilator signature are aligned with the transcript and deferred examination application | Check the makeup examination date, location, and signature, and confirm that the version number and references are updated synchronously |
| 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 references are updated synchronously |
Three common errors
- Phenomenon: The course names, quantities, and dates of the same record do not match between the transcript and the deferred examination application. Cause: The two materials are maintained separately and are not aligned to the same record.
- Phenomenon: The makeup examination arrangement has been updated, but the transcript still references the old version, and the version is not synchronized. Cause: The change did not trigger ledger reconstruction, and the old version was not marked invalid.
- Phenomenon: The deferred examination application lacks a signature or receipt, and the makeup examination arrangement lacks an invigilator signature. Cause: The materials entered recognition before the vouchers were fully collected during the circulation process.
How to verify the setup
Acceptance of this feature: check the trigger records and execution time to confirm that execution occurs on time and only once.
Business test: change one piece of content and check whether the version number and references are updated synchronously.
- Check the process connections and trigger records to confirm that the trigger has been connected to the corresponding tool node and executes once on time.
- Check that the introduction field clearly states when execution should occur, and confirm that the termination node is connected at the end of steps that do not require summarization.