What this category's data looks like
This category's data covers three types of materials: transcripts, deferred exam applications, and makeup exam arrangements. Transcripts are submitted by the course instructor and include the course name, credits, grade, date, and signature; deferred exam applications are submitted by students and include the course, reason, application date, and approval signature; makeup exam arrangements are generated by academic affairs and include the course, time, location, and receipt. When these three types of materials enter the HTTP interface and external systems, transcripts serve as the basis for grade writing, deferred exam applications serve as proof of status changes, and makeup exam arrangements serve as the source of exam notifications. The update cadence is one synchronization each after grade entry, deferred exam approval, and makeup exam scheduling per semester. Field characteristics: course name, credits, grade, date, signature, receipt. Common inconsistencies: the name, credits, and date of the same course do not match across two materials; versions are not synchronized; signatures or receipts are missing.
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 version ledger and change records are completed by subsequent nodes parsing the response, or by the external system handling it as agreed.
| Object | Check | Verification action |
|---|---|---|
| Transcript | Fields, date, and signature must be consistent with the deferred exam application and makeup exam arrangement | Check the course name, credits, grade, date, and signature; use responseData to compare the returned fields |
| Deferred exam application | Fields, date, and signature must be consistent with the transcript and makeup exam arrangement | Check the course, reason, application date, and approval signature; use variables to trace the source of placeholders |
| Makeup exam arrangement | Fields, date, and receipt must be consistent with the transcript and deferred exam application | Check the course, time, location, and receipt; use Authorization to check authentication information |
| HTTP node | The request URL, request headers, request body, and variable sources are verifiable | View the fully rendered URL and returned fields in the request preview |
Three common errors
- Symptom: the name, credits, and date of the same course do not match between the transcript and the makeup exam arrangement. Cause: the two materials are maintained separately, without field comparison and version synchronization.
- Symptom: the deferred exam application has been updated, but the transcript still references the old version, and the versions are not synchronized. Cause: after the change, the knowledge base or external documents were not updated, and references were not synchronized.
- Symptom: the transcript lacks a signature, and the makeup exam arrangement lacks a receipt. Cause: signatures and receipts were not fully collected during material circulation and went directly into the interface.
How to verify the setup
This feature's acceptance: 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: change one piece of content and see whether the version number and references are updated in sync
- In the variables panel, check the source of each placeholder and confirm that the placeholders in the request URL, request headers, and request body can be resolved into actual values.
- Use one sample request to compare the returned fields, check the request header names and value sources, and confirm that the fields are consistent with the external interface agreement.