What this category's data looks like
Undergraduate program setup and dynamic adjustment involve three types of materials: program setup application forms, talent cultivation plans, and expert review opinions. The application form provides the proposed program name, code, degree-granting category, length of study, and responsible person's signature; the cultivation plan provides the course structure, credit hour and credit allocation, practical components, and approval date; the expert review opinions provide the review conclusion, list of experts, signatures, and receipts. The materials come from academic affairs system exports, departmental submissions, and meeting archives, and are updated weekly or monthly. When entering the progress records and statistical verification function, the application form serves as the main record anchor, the cultivation plan and review opinions serve as attachments and status basis, and the three together support the alignment of record counts and statistical counts.
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 request URL and path parameters, request headers, and request body can all use variables placeholders, with variables coming from global variables, system variables, or outputs from preceding nodes, and authentication information placed in Authorization according to external system requirements. The "progress table and statistical scope description" is parsed by subsequent nodes from the response, or handled by the external system according to the agreement to complete the follow-up.
| Object | Check | Verification action |
|---|---|---|
| Program setup application form | Whether the name, code, date, and signature are consistent item by item with the talent cultivation plan and expert review opinions | Verification action: retrieve the application form and cultivation plan, compare the program name, quantity, date, and signature; check the source of each placeholder in the variable panel |
| Talent cultivation plan | Whether the course structure, credit hours and credits, and approval date match the application form and review opinions | Verification action: use a sample request to compare the response, and check whether the name, quantity, and date in the plan are consistent with the application form |
| Expert review opinions | Whether the review conclusion, list of experts, signatures, and receipts are complete and version-synchronized | Verification action: check whether signatures and receipts are missing, and check whether the review opinion version is synchronized with the application form and cultivation plan |
| Request and response | Whether the request URL, request headers, request body, and returned fields conform to the external interface agreement | Verification action: view the fully rendered URL in the request preview, and check the Authorization and responseData fields |
Three common errors
- Symptom: The name, quantity, or date of the same program do not match between the application form and the cultivation plan. Cause: The two materials are maintained separately, without field-level comparison and version synchronization.
- Symptom: The expert review opinions lack signatures or receipts, but the progress table still records them as complete. Cause: Signatures and receipts are not included in the verification items, and status updates only look at the submission time.
- Symptom: The request returns 401 or the external system receives empty fields. Cause: The source of the
Authorizationvalue is not verified, and thevariablesplaceholders are not parsed into actual values.
How to verify the setup
Acceptance for this function: preview the rendered request, check the status code and returned fields, then compare the result against a sample; check whether variables, Authorization, and responseData appear as agreed.
Business test: use one week of records to verify the totals, and see whether the scope and exceptions are clearly stated; the record count and statistical count should match, and the scope should be written in the header.
- Check the source of each placeholder in the variable panel, and confirm that global variables, system variables, and outputs from preceding nodes can be parsed into actual values.
- Use a sample request to compare the response, check that the request body fields are consistent with the external interface agreement, and record the number of array items and the tokens of the referenced text.