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. Transcripts are entered by the course instructor and include the course name, credits, grade, entry date, and instructor signature; deferred examination applications are submitted by students and include the course, reason for deferral, application date, and approval signature; makeup examination arrangements are scheduled by academic affairs and include the course, makeup examination time, examination room, and responsible person's signature. Materials are updated centrally by semester, and makeup examination arrangements are adjusted along with the examination process. After entering the workflow, the transcript serves as the primary record, while deferred examination applications and makeup examination arrangements serve as supporting evidence and triggering basis. The fields, dates, and signatures of the three must be cross-compared, and any inconsistency enters exception tracing.
Configuration and implementation checks
This step is executed by workflow nodes (user selection and branching), outputting branch directions and interaction state records. The "exception list and review conclusions" are continued and completed by subsequent nodes according to the branches. When the user selection node is triggered, the conversation enters an interactive state and records the workflow state. After the user completes the selection, execution continues along the branch corresponding to the selected option.
| Object | Check | Verification action |
|---|---|---|
| Transcript | Course name, credits, grade, entry date, instructor signature are consistent item by item with the deferred examination application and makeup examination arrangement | Check the name, quantity, and date of the same course in the two materials; check whether signatures and receipts are complete; reference variables to record the comparison result |
| Deferred examination application | Applied course, reason for deferral, application date, approval signature correspond to the transcript and makeup examination arrangement | Check whether the deferred course is marked in the transcript and whether the makeup examination arrangement covers it; check the approval signature and receipt; reference nodeId in subsequent nodes to locate the branch |
| Makeup examination arrangement | Makeup examination course, time, examination room, responsible person's signature match the transcript and deferred examination application | Check that the makeup examination course is consistent with the deferred examination application and that the time does not conflict with the transcript; check the responsible person's signature; do a trial run to see variables passed |
| Exception list | Each exception is supported by the original record and has the reviewer's signature | Trace each item back to the original text of the transcript, deferred examination application, or makeup examination arrangement; confirm signatures and receipts; record branch directions |
Three common errors
- Phenomenon: The name and credits of the same course do not match between the transcript and the makeup examination arrangement. Cause: The two materials are entered by different roles, and no field-level comparison and version synchronization were performed.
- Phenomenon: The deferred examination application has been approved, but the transcript still shows absence, and the makeup examination arrangement does not cover it. Cause: The materials are updated at different paces, the approval receipt was not written back, and the versions were not synchronized.
- Phenomenon: The exception list has records but lacks the reviewer's signature or the original receipt. Cause: The review step did not mandatorily attach the source materials, and the signature process was skipped.
How to verify the setup
Acceptance of this feature: run trials option by option, check the branch directions and interaction states in the run records, confirm that each option corresponds to one branch, and reference variables and nodeId in subsequent nodes to verify that the selection result variable has been passed.
Business test: create an exception record, see whether it can be traced to the source material, confirm that the exception is supported by the original record and has the reviewer's signature, and then hand it over to the responsible person for handling.
- In the user selection node, check the options and branch connections one by one, trigger once, and view the node status and interaction state in the run records.
- Reference the selection result variable in a subsequent node and do a trial run once to confirm that after selecting an option, the corresponding branch is taken, and after the interaction is completed, the process continues to execute downward.