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. The sources are academic affairs system exports, submissions by course instructors, and college summaries. The update cadence advances weekly, and the field characteristics include course name, credits, grade, date, and signature field. The transcript is the primary record, the deferred examination application is the exception source, and the make-up examination arrangement is the basis for subsequent corrections; when the three enter the progress records and statistical verification function, they respectively assume the roles of baseline, exception, and adjustment, and each needs to be positioned separately in the progress table and the statistical scope statement.
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 "progress table and statistical scope statement" is parsed from the response by subsequent nodes, or handled by an external system according to the agreement to complete the next step.
| Object | Check | Verification action |
|---|---|---|
| Transcript | Whether the course name, credits, grade, date, and signature match the deferred examination application and make-up examination arrangement | Compare the names, quantities, and dates in the three materials one by one, and mark those missing signatures or receipts |
| Deferred examination application | Whether the deferred examination course and the record in the transcript have the same name, same quantity, and same date | Check the application date and signature field, and confirm the version is synchronized with the current progress table |
| Make-up examination arrangement | Whether the grade after the make-up examination is written back to the transcript, and whether the date and signature are complete | Use the make-up examination arrangement to check the transcript update records one by one, and check whether the receipt is retained |
| HTTP request | Whether Authorization, variables, and responseData are passed in and returned according to the agreement | View the complete rendered address in the request preview, and check the request header names and value sources |
Three common errors
- Symptom: The name, quantity, and date of the same record do not match between the transcript and the deferred examination application. Cause: The two materials are entered separately, and the fields are not aligned according to the same scope.
- Symptom: The make-up examination arrangement has been updated, but the transcript is still the old version, and the versions are not synchronized. Cause: The update cadences differ, and there is a lack of a unified progress table and statistical scope statement.
- Symptom: The deferred examination application or make-up examination arrangement lacks a signature or receipt, making it impossible to verify the total. Cause: The material circulation step does not require a signature receipt, and the number of records does not match the statistical count.
How to verify the setup
This function'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 appear according to the agreement.
Business test: use one week of records to verify the total, see whether the scope and exceptions are clearly stated, and confirm that the number of records matches the statistical count.
- In the variables panel, check the source of each placeholder, and confirm that the variables in the request address, request headers, and request body can be resolved into actual values.
- Use one sample request to compare the return, and check whether the fields are consistent with the agreement of the external interface.