What this category's data looks like
This category's materials for undergraduate program setup and dynamic adjustment include three types: program setup application forms, talent cultivation plans, and expert review opinions. The program setup application form records the program name, code, length of study, and degree-granting category, including the person in charge and the date of the department/college seal; the talent cultivation plan states the cultivation objectives, curriculum system, credits and class hours, and graduation requirements, with the signature of the reviewer attached; the expert review opinions record the review conclusion, list of experts, review date, and expert signatures. The material sources are submissions from the school's teaching management department and departments/colleges, and the update rhythm changes with the application cycle, cultivation plan revisions, and the holding of review meetings. When entering this function, the program setup application form provides application data and date fields, the talent cultivation plan provides course and credit fields, and the expert review opinions provide review conclusion and signature information; together, the three support the version ledger and change records.
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 version ledger and change records are completed by subsequent nodes parsing the response, or by an external system handling it as agreed. The HTTP node 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 the output of preceding nodes.
| Object | Check | Verification action |
|---|---|---|
| Program setup application form | Fields, dates, and signatures must match the talent cultivation plan and expert review opinions | Check the program name, program code, length of study, degree-granting category, person-in-charge seal, and date, and compare the field values of the same record in the other two materials |
| Talent cultivation plan | The curriculum system, credits and class hours, and review signature must be consistent with the application form and review opinions | Check the cultivation objectives, course setup, credits and class hours, graduation requirements, and reviewer signature, and verify whether the name, quantity, and date of the same record are consistent |
| Expert review opinions | The review conclusion, expert list, and review date must be synchronized with the application form and cultivation plan | Check the review conclusion, expert names, review date, and expert signatures, and confirm that missing signatures or receipts are marked as pending supplementation |
| HTTP request configuration | Placeholder variables can be resolved into actual values, and fields are consistent with the external interface agreement | View the full rendered address in the request preview, check the source of the Authorization request header value, compare the return with a sample request, and check the sources of variables and responseData in the variables panel |
Three common errors
- Symptom: The name and length of study of the same program do not match between the application form and the cultivation plan. Cause: The two materials are maintained by different personnel, and no field-level comparison was performed during updates.
- Symptom: An old version of the cultivation plan is still referenced, and the current version is not unique. Cause: The version number was not synchronized with content changes, and the reference does not point to the current version.
- Symptom: The expert review opinions lack expert signatures or receipts. Cause: The review meeting records were not returned, and the signature pages were not archived with the materials.
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 one sample, and confirm that the responseData fields are consistent with the external interface agreement.
Business test: change one piece of content and see whether the version number and references are updated synchronously.
- 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 returned fields, and check whether the external system receives empty fields or a request timeout occurs.