What this category's data looks like
Grade entry and credit recognition involves three types of materials: transcripts, deferred examination applications, and make-up examination arrangements. A transcript records the course name, credits, grade, and entry date, and is the basis for credit recognition; a deferred examination application contains the application reason, original examination date, and approval signature, and determines whether a deferred examination is granted; a make-up examination arrangement contains the make-up examination time, location, and invigilator signature, and is the basis for subsequent grade corrections. The materials come from the academic affairs system and department submissions, and are updated by semester or examination cycle. Field characteristics include course code, credit value, grade level, signature field, and receipt number. When entering the authorized access and external services function, the transcript serves as the core data of the visible scope, while the deferred examination application and make-up examination arrangement serve as associated materials; together the three determine the match between visitor identity and visible scope. External entry points must filter fields by role, and unauthorized access must not be visible.
Configuration and implementation checks
This step is executed by the HTTP node in the workflow, which outputs the response body, status code, and returned fields. The externally available entry points and authorization scope are determined by subsequent nodes parsing the response, or by an external system handling it as agreed to complete the rest. The HTTP node does not replace the external system in writing to the database or approving.
| Object | Check | Verification action |
|---|---|---|
| Transcript | Whether the course name, credits, grade, entry date, and signature are consistent with the deferred examination application and make-up examination arrangement | Check the course name, credits, and date of the same course across the three materials, and inspect the signature and receipt number |
| Deferred examination application | Whether the application reason, original examination date, and approval signature correspond to the transcript and make-up examination arrangement | Compare the examination dates in the deferred examination application and the make-up examination arrangement, and confirm the approval signature is complete |
| Make-up examination arrangement | Whether the make-up examination time, location, and invigilator signature are synchronized with the transcript and deferred examination application | Check whether the course code and credits in the make-up examination arrangement and the transcript are consistent, and whether the versions are synchronized |
| Request URL and path parameters | Placeholder variables can be resolved into actual values | View the rendered full URL in the request preview, and check the source of variables |
Three common errors
- Symptom: The name and credits of the same course do not match between the transcript and the make-up examination arrangement. Cause: The two materials are entered separately, versions are not synchronized, and there is no unified check.
- Symptom: The deferred examination application has an approval signature, but the make-up examination arrangement lacks an invigilator signature or receipt. Cause: A signature step was omitted, and the material flow was not closed-loop.
- Symptom: The request returns 401, and the external system receives empty fields. Cause: The source of the
Authorizationvalue is wrong, and the request body fields are inconsistent with the external interface agreement.
How to verify the setup
Preview the rendered request, check the status code and returned fields, then compare the result against one sample; check whether Authorization, variables, and responseData are traceable.
Business test: access once with a restricted identity and see whether the visible scope matches the setting.
- In the variables panel, check the source of each placeholder, and confirm the request header name and value source.
- Use one sample request to compare the response, and check whether the request body fields are consistent with the external interface agreement.