What this category's data looks like
Degree conferral and certificate information reporting involves three core types of materials: degree application forms, thesis review forms, and defense resolutions. Degree application forms come from training units and degree offices, and are filled in centrally by batch; fields include applicant information, course grades, thesis title, supervisor signature, and date. Thesis review forms are submitted by review experts; fields include review comments, score, reviewer signature, and review date. Defense resolutions are formed by the defense committee; fields include resolution conclusion, committee member signatures, and defense date. When the three types of materials enter workflow orchestration, their roles differ: the degree application form serves as the main record driving branches, while the thesis review form and defense resolution participate in judgment as attachment conditions. The update rhythm is synchronized with degree batches, and it is common for the name, quantity, and date of the same record to mismatch across two materials, for versions to be out of sync, or for signatures or receipts to be missing.
Configuration and implementation checks
This step is executed by workflow nodes (user selection and branches), outputting branch directions and interaction state records. "Handover-ready deployment status and operation records" are completed by subsequent nodes continuing execution according to the branches. When the user selection node is triggered, the conversation enters an interaction state and records the workflow state; after the user completes the selection, execution continues along the branch corresponding to the selected option.
| Object | Check | Verification action |
|---|---|---|
| Degree application form | Whether fields, dates, and signatures are consistent with the thesis review form and defense resolution | Check the applicant name, thesis title, date, and signature item by item, inspect for missing signatures or receipts, and reference variables and nodeId in the user selection node to trial-run the branch |
| Thesis review form | Whether review comments, score, reviewer signature, and review date match the defense resolution | Check the name, quantity, and date of the same record across the two materials, trigger the user selection node once, and inspect the node status and branch direction in the run records |
| Defense resolution | Whether the resolution conclusion, committee member signatures, and defense date are consistent with the degree application form | Check whether versions are synchronized, inspect for missing signatures or receipts, reference the selection result variable in a subsequent node and trial-run once, and confirm that the corresponding branch is taken |
| User selection node | Each option corresponds to one branch, and the interaction state is recorded | Check the options and branch connections one by one in the node, trigger once and inspect the node status in the run records, and confirm that the selection result variable has been passed to subsequent nodes |
Three common errors
- Symptom: after selecting an option, the default branch is still taken. Cause: the options and branch connections were not checked one by one, and the selection result variable was not referenced correctly.
- Symptom: the name, quantity, and date of the same record mismatch across the two materials. Cause: field-level comparison was not performed between the degree application form and the thesis review form or defense resolution.
- Symptom: the process stops after the interaction is completed. Cause: the interaction state was not recorded or subsequent nodes did not continue execution according to the branch, and missing signatures or receipts were not completed.
How to verify the setup
Feature acceptance: trial-run each option one by one, check the branch direction and interaction state in the run records, confirm that each option corresponds to one branch and that the selection result variable has been passed to subsequent nodes, and check the references to variables and nodeId.
Business testing: check item by item once according to the handover sheet, see which record is missing, and confirm that the version, connection, and task record are consistent.
- Check the options and branch connections one by one in the node, trigger the user selection node once, and inspect the node status in the run records.
- Reference the selection result variable in a subsequent node and trial-run once, and check the fields, dates, and signatures of the degree application form, thesis review form, and defense resolution.