What this category's data looks like
This category's materials for technical college academic education management include three types: student registration forms, teaching plans, and skills training records. Student registration forms are entered by the admissions department per semester, containing name, student ID, registration date, and homeroom teacher signature; teaching plans are maintained by the academic affairs office per major version, containing course name, class hours, and teaching and research office receipt; skills training records are filled in by practical training teachers per week, containing workstation number, training item, quantity, and training signature. The three types of materials update at different rhythms: registration forms follow admissions batches, plans follow major revisions, and training records follow weeks. When entering the exception tracing and manual review function, registration forms serve as the identity source, teaching plans serve as the course baseline, training records serve as process evidence, and the HTTP interface is responsible for sending the three to an external system for comparison according to agreed fields.
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, path parameters, request headers, and request body can all use variable placeholders; variables come from global variables, system variables, or outputs of preceding nodes, and authentication information is placed in Authorization according to the external system's requirements. The exception list and review conclusions are parsed from the response by subsequent nodes, or the external system handles them as agreed and then completes the process.
| Object | Check | Verification action |
|---|---|---|
| Student registration form | Fields, dates, and signatures: whether name, student ID, registration date, and homeroom teacher signature are complete and consistent with the training records | Take one registration record, check the rendered URL and variables values in the request preview, and confirm that the fields returned by responseData include the registration number and signature status |
| Teaching plan | Fields, dates, and signatures: whether course name, class hours, version number, and teaching and research office receipt match the training records | Use a sample request to compare the response, check whether the plan version number and the version referenced by the training records come from the same source, and if the receipt is missing, record it in the exception list |
| Skills training record | Fields, dates, and signatures: whether workstation number, training item, quantity, and training signature are consistent with the registration form and plan | Create a record with mismatched quantity or date, see whether the request body fields are sent as agreed, and whether the response can be traced back to the source material |
Three common errors
- Symptom: the name or quantity of the same record does not match between the registration form and the training record. Cause: the two were entered at different times, were not backfilled by student ID, and cross-table checking is missing.
- Symptom: the teaching plan version is not synchronized, and the training record still references the old class hours. Cause: after the major revision, the referenced version was not updated, and the receipt was not archived with the version.
- Symptom: the request returns 401 or the external system receives empty fields. Cause: the source of the
Authorizationvalue is incorrect, or the request body fields are inconsistent with the interface agreement.
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; confirm that variables and responseData can be traced to specific sources.
Business test: create an exception record, see whether it can be traced back to the source material, and check whether the review conclusion is accompanied by the original record and signature.
- In the variables panel, check the source of each placeholder and confirm that the variables in the request URL, request headers, and request body can all be resolved into actual values.
- Use one sample request to compare the response, check whether the fields are consistent with the external interface agreement, and record the number of array items and the tokens of the referenced text.