What this category's data looks like
This page focuses on Q&A intake and missing-item follow-up for student status changes and graduation eligibility review. The source materials include leave/resumption-of-study applications, major transfer applications, and graduation review checklists. Leave/resumption-of-study applications provide the reason for the change, date, and signature field; major transfer applications provide transfer-in/transfer-out information and approval opinions; graduation review checklists provide course, credit, and graduation conclusion fields. The materials are submitted in batches by the handling stage, and the update cadence advances with the intake window and review milestones. When entering this function, the three types of materials respectively serve the roles of reason explanation, basis for the status change, and eligibility checklist. Field names, dates, and signatures must be aligned item by item, and missing items are completed through follow-up questions before being forwarded to the handler.
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 completed question items" are parsed from the response by subsequent nodes, or handled by an external system according to the agreement to complete the rest. The request URL, path parameters, request headers, and request body can all reference the output of preceding nodes via variables. Authentication information is placed in Authorization according to the external system's requirements, and the returned content is carried in responseData.
| Object | Check | Verification action |
|---|---|---|
| Leave/resumption-of-study application | Whether the reason, date, and signature field are complete, and whether the name and date of the same record in the major transfer application are consistent | Check the application reason field and signature field, compare the date and name of the same record in the two materials, and record missing items as items to be followed up |
| Major transfer application | Whether the transfer-in/transfer-out information, approval opinions, and receipt are complete, and whether the version is in sync with the graduation review checklist | Check the transfer-in/transfer-out fields and approval opinions, check whether the receipt is missing, and compare the checklist version number and update date |
| Graduation review checklist | Whether the course, credit, and graduation conclusion fields correspond to the application materials, and whether the quantities and dates match | Compare the course quantities and credit records item by item, check the graduation conclusion date, and generate follow-up items when inconsistencies are found |
| HTTP request | Whether the placeholders in the path parameters, request headers, and request body can be resolved to actual values, and whether the authentication and field conventions are consistent | View the fully rendered URL in the request preview, check the source of the Authorization value and the request body fields, and use a sample request to compare the responseData return |
Three common errors
- Symptom: The name and date of the same record do not match between the leave/resumption-of-study application and the major transfer application. Cause: The two materials are entered separately, without field-level comparison and synchronization.
- Symptom: The graduation review checklist version is not synchronized, and differences appear in course quantities and credit records. Cause: The checklist was not resubmitted after updating, and the old version is still in circulation.
- Symptom: The major transfer application lacks a signature or receipt, and the intake record cannot be closed. Cause: The approval stage did not return the signed document, and the receipt was not filled in as agreed.
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 a sample; at the same time, check whether the source of variables, the Authorization value, and the responseData fields are consistent with the external interface agreement.
Business test: submit a question that lacks key information and see whether it asks a follow-up question before answering.
- In the variables panel, check the source of each placeholder and confirm that the variables in the path parameters, request headers, and request body can all be traced to global variables, system variables, or the output of preceding nodes.
- Use a sample request to compare the return, check whether the external system receives empty fields, and check whether the request header names and value sources meet the external system's requirements.