What this category's data looks like
Materials in the grade entry and credit recognition scenario are mainly transcripts, deferred examination applications, and makeup examination arrangements. Sources are exports from the academic affairs system and submissions from departments, and the update cadence advances by semester batches. Field characteristics center on course name, credit count, examination date, and signature field. The transcript serves as the primary record for grades and credit recognition, the deferred examination application serves as the special-status explanation, and the makeup examination arrangement serves as the supplement for time and examination venue. When materials enter the Q&A intake and missing-item follow-up function, each serves as an object to be verified: first identify whether fields are complete, then decide whether to follow up.
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 intake record and the completed follow-up items 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 a request to the target address. Path parameters, request body, and request headers can all use variable placeholders, and the variables come from global variables, system variables, or outputs of preceding nodes.
| Object | Check | Verification action |
|---|---|---|
| Transcript | Whether course name, credit count, examination date, and signature field correspond item by item with the deferred examination application and makeup examination arrangement | Check whether the name, count, and date of the same record are consistent across the two materials, and check whether the signature or receipt is complete |
| Deferred examination application | Whether the deferred course, deferred date, and approval signature corroborate each other with the transcript and makeup examination arrangement | Compare the date and name of the same course across the two materials, and confirm which one prevails when versions are not synchronized |
| Makeup examination arrangement | Whether the makeup course, makeup date, and examination venue information match the fields of the transcript and deferred examination application | Check whether the course count and date of the makeup examination arrangement and the transcript correspond; when a signature or receipt is missing, mark it for follow-up |
| Request address and path parameters | Placeholder variables can be resolved into actual values | View the rendered full address in the request preview, and check the source of variables |
Three common errors
- Symptom: The name and count of the same course do not match between the transcript and the makeup examination arrangement. Cause: The two materials' versions are not synchronized, and the entry batches differ.
- Symptom: The deferred examination application lacks an approval signature or receipt, so the status cannot be confirmed at intake. Cause: A signature was omitted or a receipt was not archived during material circulation.
- Symptom: The request returns 401 or the external system receives empty fields. Cause: The source of the
Authorizationvalue was not checked, or the request body fields are inconsistent with the external interface agreement.
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 one sample to confirm that the fields in responseData are consistent with the external interface agreement.
Business test: submit a question missing key information and see whether it follows up first before answering.
- In the variables panel, check the source of each placeholder and confirm that the values of
variablesandAuthorizationare traceable. - Use one sample request to compare the return, check that the request body fields are consistent with the external interface agreement, and check that the tokens of the referenced text and the array item count are recorded separately.