What this category's data looks like
This page focuses on the degree conferral and certificate information reporting scenario. The source materials are degree application forms, thesis review forms, defense resolutions, and certificate reporting receipts, and the update cadence rolls forward by batch and defense cycle. The degree application form carries the applicant and degree category fields, the thesis review form carries the review conclusion and review date, the defense resolution carries the defense conclusion, voting result, and signature, and the receipt carries the reporting destination and confirmation information. When the materials enter workflow orchestration, each participates as an independent object in the branch decisions of the authorized access and external service nodes. The external entry point and authorization scope must match the visitor's identity and visibility scope, and unauthorized access must be invisible. Names, quantities, dates, and signatures across materials must be aligned item by item, and only after version synchronization may they enter the external service branch.
Configuration and implementation checks
This step is executed by workflow nodes (user selection and branching), outputting the branch direction and interaction state records. The externally available entry points and authorization scope are completed by subsequent nodes continuing execution along the branch. When a node is triggered, the conversation enters the interaction state and the workflow state is recorded; after the user completes the selection, execution continues along the branch corresponding to the selected option.
| Object | Check | Verification action |
|---|---|---|
| Degree application form | Names, quantities, dates, and signatures must be aligned item by item with the thesis review form and defense resolution; if fields are missing or versions are not synchronized, it must not enter the external service branch | Check the options and branch connections one by one in the node, reference variables and nodeId, and run a trial once to view the branch direction and interaction state records |
| Thesis review form | The review conclusion, review date, and signature must be consistent with the defense resolution; the name and date of the same record must not mismatch between the two materials | Trigger a user selection node once, and check in the run records whether the node state and selection result variables have been passed to subsequent nodes |
| Defense resolution | The defense conclusion, voting result, and signature must be complete; if the signature is missing or the receipt is absent, it must not enter the branch open to parents or superiors | Reference the selection result variable in subsequent nodes and run a trial, verifying whether unauthorized access is invisible and whether the visibility scope matches the settings |
| Certificate reporting receipt | The receipt confirmation information must be consistent with the reporting destinations of the degree application form, thesis review form, and defense resolution; if versions are not synchronized, it must not be exposed externally | Access once with a restricted identity, and verify whether the external entry point and authorization scope are correctly limited according to the branch direction |
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: Material versions are not synchronized, and each enters the branch independently, causing field misalignment.
- Symptom: The defense resolution lacks a signature or the receipt has not been returned, yet it still enters the external service branch. Cause: Node options and branch connections were not checked item by item, and the selection result variable was not passed correctly.
- Symptom: After selecting a certain option, it still follows the default branch, and the process stalls after the interaction completes. Cause: The same session repeatedly enters the interaction, and the node state in the run records is not read correctly.
How to verify the setup
This feature's acceptance: run trials for each option one by one, check the branch direction and interaction state in the run records, confirm that variables and nodeId are correctly referenced in subsequent nodes, and that the selection result variable has been passed.
Business test: access once with a restricted identity, see whether the visibility scope matches the settings, that unauthorized access is invisible, and that the external entry point and authorization scope match the visitor's identity.
- Check the options and branch connections one by one in the node, confirm that each option corresponds to one branch, and trigger once to view the node state in the run records.
- Reference the selection result variable in subsequent nodes and run a trial once, verifying whether the external entry point and authorization scope are correctly limited according to the branch direction, and that unauthorized access is invisible.