What this category's data looks like
Materials in the graduate admissions re-examination and admission stage include the re-examination plan, candidate score sheets, adjustment lists, admission receipts, and signature pages. The re-examination plan specifies the process, timing, and scoring criteria; the candidate score sheets carry the preliminary examination, re-examination, and total score fields; the adjustment lists record adjustment batches, preferences, and proposed admission status; the receipts and signature pages confirm the confirmation actions of candidates and reviewers. Materials come from admissions system exports, college submissions, and manual supplementary entry, with update rhythms concentrated before the re-examination, after the re-examination, and during the adjustment window, and there may be multiple revisions on the same day. When entering the scheduled tasks and automation feature, the re-examination plan serves as the rule draft that determines the version number generation criteria, the score sheets and adjustment lists serve as the record subjects participating in version comparison, and the receipts and signature pages serve as completeness attachments participating in missing-item checks. Field verification is concentrated in four categories: name, quantity, date, and signature, and the same record must be consistent across two materials.
Configuration and implementation checks
This step is executed by the trigger configuration and tool nodes (scheduled capability is not in the tool introduction), outputting trigger records and execution results. The "version ledger and change records" are completed by business processing executing by record or supplementary runs. Tool invocation is decided by the model based on the tool introduction whether to execute; when the model does not need 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 |
|---|---|---|
| Re-examination plan | The process, dates, and scoring criteria within the plan are consistent in the score sheets and adjustment lists, and the current version is unique | Compare the date and name fields of the plan and the lists, and check the trigger records and execution results |
| Candidate score sheets | The quantity and date fields of the preliminary examination, re-examination, and total scores within the score sheets have no conflicts, and old versions are traceable | Check whether the name, quantity, and date of the same record in the score sheet fields and the adjustment lists match |
| Adjustment lists | The adjustment batches, preferences, and proposed admission status within the lists are consistent with the score sheets and the plan, and missing signatures or receipts are marked | Check the lists and the receipt signature pages, and confirm that references are synchronized and old versions are traceable |
| Version ledger and change records | The ledger records a unique current version, 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
- Symptom: It did not execute at the scheduled time, and the ledger was not generated. Cause: The trigger was not connected to the corresponding tool node, the process connection was missing, and scheduled capability is not in the tool introduction.
- Symptom: The name, quantity, and date of the same record do not match across two materials. Cause: The re-examination plan, score sheets, and adjustment lists were revised separately, and versions were not synchronized.
- Symptom: After execution, the model summarized it again, or the same task was executed repeatedly. Cause: The tool invocation termination node was not connected at the end of the tool, and trigger records were duplicated.
How to verify the setup
This feature acceptance: check the trigger records and execution time, and confirm that it executes at the scheduled time and only once.
Business test: change one piece of content, and see whether the version number and references are updated synchronously.
- Check the process connections and trigger records, and confirm that the trigger has been connected to the corresponding tool node, executes at the scheduled time, and only once.
- Check the tool introduction fields, and clearly state when it should execute; when no summary is needed, confirm that the termination node has been connected at the end of the tool.