What this category's data looks like
The material sources for Q&A intake and missing-item follow-up in undergraduate program revision are the program, course syllabi, the credit structure table, and their revised versions. The program provides the major direction and the overall credit framework, the course syllabi give course names, class hours, and assessment methods, and the credit structure table lists the credits and proportions of each module. The update cadence advances with revision batches, and common fields include course name, credit count, effective date, signature, and receipt. When materials enter the intake stage, the program serves as the anchor master record, while the course syllabi and credit structure table serve as the basis for comparison; together the three support missing-item identification and follow-up questions.
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 items to be completed" are parsed from the response by subsequent nodes, or handled by an external system according to the agreement to finish the process.
| Object | Check | Verification action |
|---|---|---|
| Program | Whether the course name, credit count, effective date, and signature are complete | Check the fields item by item against the revision batch, and mark missing items |
| Course syllabi | Whether the name, count, and date of the same course match across the two materials | Extract courses with the same name, compare credits and class hours, and record inconsistencies |
| Credit structure table | Whether the module credits and total credits are in sync with the program version | Check the version number and date, and confirm whether the signature or receipt is attached |
| HTTP request | Whether the path parameters, request body, and request header placeholders can be parsed into actual values | Check the source of variables in the request preview, and compare the returned responseData |
Three common errors
- Symptom: the name and credits of the same course do not match between the program and the course syllabi. Cause: the two materials were revised separately, and no cross-comparison was performed.
- Symptom: the credit structure table still uses an old version, and the total credits are inconsistent with the program. Cause: the versions were not synchronized, and the revision batches were not registered uniformly.
- Symptom: the intake record lacks a signature or receipt, and it still cannot be completed after follow-up. Cause: the material circulation step left no trace, and the responsible person and date are missing.
How to verify the setup
Acceptance of this feature: preview the rendered request, check the status code and returned fields, then compare the result against one sample; check whether the request header Authorization and the request body fields are consistent with the external interface agreement, and confirm that the intake record and question item fields in responseData are complete.
Business test: submit a question that lacks key information, and see whether it asks a follow-up question before answering.
- In the variable panel, check the source of each placeholder, and confirm that
variablescan be traced to a global variable, a system variable, or the output of a preceding node. - Use one sample request to compare the response, check the request header names and the source of their values, and troubleshoot 401 and empty fields.