What this category's data looks like
Degree conferral and certificate information reporting involves three types of materials: degree application forms, thesis review forms, and defense resolutions. The degree application form records the degree applicant's basic information, course grades, and supervisor's comments; the thesis review form carries the reviewer's conclusion and review date; the defense resolution records the defense committee's voting results and signatures. When reporting, the three types of materials must keep the name, quantity, and date of the same record consistent, and signatures and receipts must be complete. The material sources are the university's various training units and degree management departments, and the update pace advances with links such as review, defense, and the degree committee meeting. When the materials enter this feature, the degree application form provides the application subject and qualification fields, the thesis review form provides the review conclusion and time anchor, and the defense resolution provides the final vote and approval information; together, the three form the business basis of 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 |
|---|---|---|
| Degree application form | Fields, dates, and signatures must be aligned item by item with the thesis review form and defense resolution | Check the name, student ID, date, and signature in the application form against the other two materials; verify the source of variables in the variable panel |
| Thesis review form | The review conclusion, review date, and reviewer signature must be complete and consistent with the application form | Compare the return with a sample request, and check the review conclusion field and date; check the source of the Authorization value in the request header |
| Defense resolution | The voting result, defense date, and committee signatures must be consistent with the application form and review form | Check the defense date and voting conclusion in the resolution against the other two materials; verify the corresponding content of responseData in the returned fields |
| Version ledger and change records | The current version is unique, old versions are traceable, and references are synchronized | After changing one piece of content, check whether the version number and references are updated in sync; verify that the request body fields are consistent with the external interface agreement |
Three common errors
- Symptom: The name or date of the same record does not match between the degree application form and the defense resolution. Cause: The two materials were entered separately, without field comparison based on the same version ledger.
- Symptom: The thesis review form has been updated, but the reporting material citing that review conclusion still points to the old version. Cause: The version was not synchronized, and the reference relationship was not refreshed along with the content change.
- Symptom: The defense resolution lacks a committee signature or receipt and is returned by the external system during reporting. Cause: Signatures and receipts were not included in the completeness check of the version ledger.
How to verify the setup
Feature acceptance: preview the rendered request, check the status code and returned fields, then compare the result against a sample; confirm that the request address and path parameter placeholder variables can be resolved into actual values, that the request header Authorization is passed in as required by the external system, that the request body fields are consistent with the external interface agreement, and that responseData in the returned fields can be parsed by subsequent nodes.
Business test: change one piece of content and see whether the version number and references are updated in sync.
- In the variable panel, check the source of each placeholder, confirm it comes from a global variable, system variable, or the output of a preceding node, and record the tokens and array length of the referenced text.
- Compare the return with a sample request, check the request header names and value sources, and verify whether the request body fields are consistent with the external interface agreement.