What this category's data looks like
Grade entry and credit recognition involve three types of materials: transcripts, deferred examination applications, and makeup examination arrangements. Sources are academic affairs system exports, instructor submissions, and application forms and receipts submitted by students. The update rhythm follows the semester: concentrated changes during the entry period, with additions around deferred and makeup examination milestones. Field characteristics center on course name, credit count, examination date, and signature and receipt fields. When materials enter this function, each plays a different role: the transcript carries the final recognition result, the deferred examination application triggers branch determination, and the makeup examination arrangement determines the subsequent visible scope. Across the three types of materials, it is common for the same record to have mismatched names, counts, and dates across two materials, with versions not synchronized, or missing signatures or receipts.
Configuration and implementation checks
This step is executed by workflow nodes (user selection and branching), outputting branch direction and interaction state records. "Externally available entry points and authorization scope" are then completed by subsequent nodes continuing execution according to the branch.
| Object | Check | Verification action |
|---|---|---|
| Transcript | Whether course name, credit count, examination date, and signature field match the deferred examination application and makeup examination arrangement item by item | Compare the course name, credit count, and examination date across the three materials one by one, and check whether signatures and receipts are complete |
| Deferred examination application | Whether the course name and date on the application form match the transcript and makeup examination arrangement, and whether the receipt is retained | Take the application form and transcript of the same record and check them side by side, checking the version number and receipt signature field |
| Makeup examination arrangement | Whether the course name, count, and date in the arrangement table are consistent with the transcript and deferred examination application | Check the fields row by row against the arrangement table and transcript, confirming there are no missing signatures or unreceipted items |
| User selection node | Each option corresponds to one branch, the interaction state is recorded, and the selection result variable has been passed to subsequent nodes | In the node, check the options and branch connections one by one, trigger once to view the node state in the run record, reference variables in subsequent nodes, and do a trial run |
Three common errors
- Symptom: The name and credit count of the same course do not match across two materials. Cause: The entry side and the application side each maintain fields separately, lacking unified comparison.
- Symptom: The deferred examination application and makeup examination arrangement versions are not synchronized, and dates deviate. Cause: Materials are updated in batches, and old versions are not withdrawn.
- Symptom: The transcript lacks a signature or the receipt field is blank, yet it still enters subsequent branches. Cause: After the interaction state is recorded, material completeness is not reviewed.
How to verify the setup
Acceptance for this function: run trial runs for each option one by one, check the branch direction and interaction state in the run record, and confirm that the node state corresponding to nodeId is consistent with the selection result variable.
Business test: access once with a restricted identity and see whether the visible scope matches the setting
- In the node, check the options and branch connections one by one, and trigger once to view the node state in the run record
- Reference
variablesin subsequent nodes and do a trial run once, confirming that the branch direction is consistent with the interaction state record