What this category's data looks like
This category's data covers three types of materials: degree application forms, thesis review forms, and defense resolutions. The degree application form carries the applicant's basic information, course grades, and degree type fields; the thesis review form carries the reviewer, review conclusion, and review date; the defense resolution carries the defense committee roster, voting result, and resolution date. Before reporting, the three types of materials must be compared item by item for the name, quantity, date, and signature status of the same record. Material sources are scattered, and the update rhythm changes as the review and defense stages progress, with field characteristics concentrated in dates, signatures, and receipt completeness. When entering this feature, the degree application form serves as the main record anchor, while the thesis review form and defense resolution serve as cross-verification references, each taking on the role of field comparison and version traceability.
Configuration and implementation checks
This step is executed by workflow nodes (user selection and branching), outputting branch directions and interaction state records. The "version ledger and change records" are completed next by subsequent nodes continuing execution according to the branch. When the user selection node is triggered, the conversation enters an interactive 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 | Fields, dates, and signatures must be aligned item by item with the thesis review form and defense resolution; the same record must not have two sets of names and quantities | Check the options and branch connections one by one in the node, reference variables to read the selection result, and run a trial |
| Thesis review form | The review date and review conclusion must be consistent with the defense resolution date and voting result; a missing signature or receipt is regarded as not synchronized | Reference the selection result variable in a subsequent node and run a trial once, then check the node status in the run records |
| Defense resolution | The defense committee roster, voting result, and resolution date must be cross-consistent with the degree application form and thesis review form, and the version number must be synchronized with content changes | Check the branch connection corresponding to nodeId and confirm that the selection result has been passed to the subsequent node |
| Version ledger and change records | The current version is unique, old versions are traceable, and references are synchronized; after changing content in one place, the version number and references must be updated in sync | Trigger the user selection node once and check the branch direction and interaction state in the run records |
Three common errors
- Symptom: The name, quantity, and date of the same record do not match between the degree application form and the thesis review form. Cause: Materials are maintained in a scattered way, lacking an item-by-item cross-comparison step.
- Symptom: The thesis review form has been updated, but the defense resolution still references the old version's content. Cause: The version was not synchronized, and references were not updated with content changes.
- Symptom: The defense resolution is missing a signature or receipt but still enters the reporting process. Cause: Signature and receipt completeness were not used as branch judgment conditions.
How to verify the setup
Feature acceptance: run trials for each option one by one, check the branch direction and interaction state in the run records, and confirm that variables and nodeId correspond correctly.
Business test: change content in one place and see whether the version number and references are updated in sync.
- Check the options and branch connections one by one in the node, and confirm that each option corresponds to one branch.
- Reference the selection result variable in a subsequent node and run a trial once to confirm that the selection result has been passed to the subsequent node.