What this category's data looks like
This page addresses progress records and statistical verification for undergraduate program revision. The materials come from three types of documents: program plans, course syllabi, and credit structure tables, updated by revision batch or calendar week. Program plans provide the major direction, total credits, and module proportions; course syllabi provide course names, credits, class hours, and signature fields; credit structure tables provide the credits for each module and the total. When these three types of materials enter the progress table and the statistical scope description, they respectively take on the roles of the main record, detailed support, and total verification, and the fields, dates, and signatures must be aligned item by item.
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 description are parsed from the response by subsequent nodes, or handled externally by the external system according to the agreement to complete the rest.
| Object | Check | Verification action |
|---|---|---|
| Program plan | Whether the major direction, total credits, module proportions, and signature date are consistent with the revision batch | Check the plan version number and signature field, and compare the course attribution in the course syllabi |
| Course syllabus | Whether the course name, credits, class hours, and signature receipt correspond item by item | Extract one course record and check the name, quantity, and date in the syllabus against those in the structure table |
| Credit structure table | Whether the credits of each module and the total equal the total credits of the plan | Use one week's records to check the total, and check whether the scope and exceptions are clearly stated |
| Request address and path parameters | Whether the placeholder variables can be resolved into actual values | View the fully rendered address in the request preview, and check the source of variables |
Three common errors
- Symptom: The name, quantity, and date of the same course do not match between the syllabus and the structure table. Cause: The two materials are maintained separately and are not synchronized by the same record key.
- Symptom: After the plan version is updated, the syllabus is still the old version. Cause: The version was not synchronized, and the revision batch was not refreshed together with the materials.
- Symptom: Missing signatures or receipts make the progress record impossible to confirm. Cause: The signature page was not returned during the material circulation step, so there is no basis for verification.
How to verify the setup
This feature's acceptance: preview the rendered request, check the status code and returned fields, then compare the result against one sample, and confirm the value sources of responseData and Authorization.
Business test: use one week's records to check the total, and see whether the scope and exceptions are clearly stated.
- In the variables panel, check the source of each placeholder and confirm that
variablescan be traced to global variables, system variables, or the output of preceding nodes - Check the request header names and value sources, and confirm that
Authorizationis passed in according to the external system's requirements