What this category's data looks like
This page focuses on exception tracing and manual review in degree conferral and certificate information reporting. The materials involved are degree application forms, thesis review forms, defense resolutions, and certificate information reporting receipts. The material sources are the original records submitted by each training unit within the degree conferral batch, and the update cadence rolls forward as the batch progresses. Field characteristics include name, degree type, thesis title, defense date, review conclusion, signature field, and receipt number. The degree application form carries personal and degree basic information, the thesis review form carries the review conclusion and expert signature, the defense resolution carries the defense conclusion and committee member signatures, and the receipt carries reporting confirmation. When materials enter workflow orchestration, each role provides the basis for comparison for subsequent nodes, exception clues are extracted from field differences, and review conclusions need to be traced back to the specific material page.
Configuration and implementation checks
This step is executed by workflow nodes (user selection and branches), outputting branch direction and interaction state records. The "exception list and review conclusion" is completed by subsequent nodes continuing execution according to the branch. When the user selection node is triggered, the conversation enters the 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 the name, degree type, thesis title, and defense date are consistent with the thesis review form, and whether the signature field is complete | Compare the two materials field by field, check the date and signature, and record the location of differences |
| Thesis review form | Whether the review conclusion, review date, and expert signature are consistent with the defense resolution, and whether the version is synchronized | Check the review conclusion against the resolution wording, and inspect the version number and signature receipt |
| Defense resolution | Whether the defense conclusion, defense date, and committee member signatures are consistent with the reporting receipt, and whether the receipt number exists | Compare the resolution and receipt fields, and confirm the receipt number and signature field |
| User selection node | Each option corresponds to one branch, and whether the selection result variable is passed to subsequent nodes | Check the options and branch connections one by one in the node, reference variables, and run a trial once |
Three common errors
- Phenomenon: The name or date for the same record does not match between the degree application form and the thesis review form. Cause: The two materials are filled in at different stages, and reporting proceeds without field-level comparison.
- Phenomenon: The thesis review form version is not synchronized, and the defense resolution cites an old review conclusion. Cause: After the version update, it was not re-associated, and the workflow still continues execution based on the old material.
- Phenomenon: The defense resolution lacks committee member signatures or the reporting receipt is missing. Cause: The signature and receipt steps were not included in the verification checklist, and exception records cannot be traced to the source material.
How to verify the setup
This feature acceptance: run a trial for each option, check the branch direction and interaction state in the run record, and confirm that the node state corresponding to nodeId is recorded.
Business test: create an exception record, see whether it can be traced to the source material, and check whether the fields referenced in variables point to the specific material page.
- In the user selection node, check the options and branch connections one by one, confirming that each option corresponds to one branch and that the selection result variable has been passed to subsequent nodes.
- Trigger an interaction, view the node state and
nodeIdin the run record, and confirm that the conversation enters the interaction state and continues execution according to the corresponding option after completion.