What this category's data looks like
The materials for student status changes and graduation qualification review fall into three categories: leave/resumption applications, major transfer applications, and graduation review checklists. Leave/resumption applications record changes in student status and effective dates; major transfer applications record major adjustments and approval chains; graduation review checklists summarize courses, credits, and graduation conclusions. The three types of materials play different roles in exception tracing and manual review: the first two are source evidence for status changes, while the latter is the basis for determining graduation qualification. Materials are updated by semester batch, and fields include name, student ID, change type, date, signature or receipt. The same record often has mismatched names, quantities, or dates across two materials, versions are not synchronized, and signatures or receipts are missing.
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 exception list and review conclusions are parsed from the response by subsequent nodes, or handled externally according to an agreement. The HTTP module sends requests to the target address. Variables can be used as placeholders in three places: path parameters, request body, and request headers. Variables come from global variables, system variables, or outputs of preceding nodes.
| Object | Check | Verification action |
|---|---|---|
| Leave/resumption application | Fields, dates, and signatures must match the original records; the change type and effective date must not conflict with the major transfer application | Check the name, student ID, change type, effective date, signature or receipt on the application form; check the source of each placeholder in the variable panel |
| Major transfer application | The major name, quantity, and approval date must match the graduation review checklist, and versions must be synchronized | Compare the major name, course quantity, and approval date in the major transfer application and the graduation review checklist; compare the response using a sample request |
| Graduation review checklist | The graduation conclusion field must be supported by original records, and the reviewer's signature must not be missing | Trace back to the source materials and check whether the conclusion in the checklist is consistent with the leave/resumption and major transfer records; view the fully rendered address in the request preview |
| HTTP request | The request address, request headers, and request body are rendered according to the external interface agreement, and authentication information is passed in according to the external system's requirements | View the fully rendered address in the request preview, check the request header names and value sources, and use Authorization to pass authentication; check the sources of variables and responseData in the variable panel |
Three common errors
- Symptom: The name or student ID of the same record does not match between the leave/resumption application and the graduation review checklist. Cause: The two materials are entered separately and are not checked against the same source material.
- Symptom: The course quantity or date in the major transfer application and the graduation review checklist is inconsistent. Cause: Versions are not synchronized, and old versions of materials are still in circulation.
- Symptom: The review conclusion lacks a signature or receipt, and the exception list cannot be handed to the responsible person for handling. Cause: The signature step is not included in the material circulation record.
How to verify the setup
Acceptance for this feature: preview the rendered request, check the status code and returned fields, then compare the result against a sample; check the sources of variables and responseData in the variable panel, and use Authorization for authentication.
Business test: create an exception record and see whether it can be traced back to the source material.
- In the request preview, view the fully rendered address, check the request header names and value sources, and confirm that
Authorizationis passed in according to the external system's requirements. - In the variable panel, check the source of each placeholder and confirm that
variablesandresponseDatacan be traced back to global variables, system variables, or outputs of preceding nodes.