What this category's data looks like
Grade entry and credit recognition involve three types of materials: transcripts, deferred examination applications, and make-up examination arrangements. Transcripts are generated by the course instructor or the academic affairs system, recording the course name, credits, grade, and entry date; deferred examination applications are submitted by students and approved, containing the application reason, approval signature, and receipt; make-up examination arrangements are published by the academic affairs department, containing the make-up examination time, location, and invigilator signature. When the materials enter the exception tracing and manual review function, the transcript serves as the baseline record, while the deferred examination application and make-up examination arrangement serve as supporting evidence and adjustment basis. The update rhythm advances with the semester, with make-up and deferred examinations concentrated at the end of the term and the beginning of the school year. The field characteristics are that the same record must be aligned across materials in name, quantity, and date, signatures and receipts must not be missing, and versions must be synchronized.
Configuration and implementation checks
This step is executed by the HTTP node in the workflow, outputting the response body, status code, and returned fields. The exception list and review conclusions are parsed from the response by subsequent nodes, or handled by an external system according to the agreement to complete the rest. The HTTP module sends requests to the target address; path parameters, request body, and request headers can all use variable placeholders, with variables coming from global variables, system variables, or the output of preceding nodes.
| Object | Check | Verification action |
|---|---|---|
| Transcript | The course name, credits, grade, and entry date must be aligned item by item with the deferred examination application and make-up examination arrangement | Check the source of each placeholder in the variable panel, and confirm that the request body fields are consistent with the external interface agreement |
| Deferred examination application | The application reason, approval signature, and receipt must be complete, and the date must connect with the transcript entry date | Check the request header names and value sources, and compare the response with a sample request |
| Make-up examination arrangement | The make-up examination time, location, and invigilator signature must be synchronized with the versions of the transcript and deferred examination application | View the fully rendered address in the request preview, and confirm that the path parameters are parsed into actual values |
| HTTP node output | The response body, status code, and returned fields must be able to support exception tracing | Check the correspondence between responseData and variables, and confirm that Authorization is passed in according to the external system's requirements |
Three common errors
- Symptom: The course name and credit quantity of the same record do not match between the transcript and the deferred examination application. Cause: The two materials are entered separately, without cross-material field comparison.
- Symptom: The make-up examination arrangement has been updated, but the transcript still references the old version. Cause: The versions are not synchronized, and there is no receipt confirming that the update is complete.
- Symptom: The deferred examination application lacks an approval signature or receipt. Cause: The approval step is not closed-loop, and the source cannot be traced when the material enters review.
How to verify the setup
Acceptance of this function: preview the rendered request, check the status code and returned fields, then compare the result against a sample to confirm that responseData and variables are traceable.
Business test: create an exception record and see whether the source material can be traced.
- Check the request address and path parameters, confirm that the placeholder variables can be parsed into actual values, and view the fully rendered address in the request preview.
- Check the request headers and request body, confirm that the authentication information is passed in according to the external system's requirements, and that the fields are consistent with the external interface agreement.