What this category's data looks like
This page addresses the scenario of degree conferral and certificate information reporting. Materials include degree application forms, thesis review reports, defense resolutions, as well as multilingual parallel drafts and a unified terminology glossary. The material sources are submissions from training institutions and historical archives, and the update cadence varies with batches and degree committee cycles. Field characteristics center on names, degree categories, thesis titles, dates, signatures, and receipts; multilingual materials also contain terminology translations and back-references to the source text. When entering this feature, the degree application form serves as the primary record, the thesis review report and defense resolution serve as cross-check materials, and the terminology glossary and parallel drafts serve as the basis for translation-name consistency, each entering subsequent processing along their respective branches.
Configuration and implementation checks
This step is executed by workflow nodes (user selection and branching), outputting branch directions and interaction state records. "Unified terminology glossary and parallel drafts" is then completed by subsequent nodes continuing execution along the branch. When a node is triggered, the conversation enters an interactive state and the workflow state is recorded; after the user completes the selection, execution continues along the branch corresponding to the chosen option.
| Object | Check | Verification action |
|---|---|---|
| Degree application form | Whether fields, dates, and signatures are consistent with the thesis review report and defense resolution | Compare name, degree category, thesis title, date, and signature item by item, check the option branch direction, and reference variables and nodeId in subsequent nodes for a trial run |
| Thesis review report | Whether the name, quantity, and date of the same record match the defense resolution | Extract three terms and check their spelling throughout the document, check the review opinion date against the defense resolution date, and inspect branch connections and option correspondence |
| Defense resolution | Whether the version is synchronized and whether signatures or receipts are missing | Check the resolution version number and receipt signature, trigger a user selection node once, and view the node status and branch direction in the run record |
| Unified terminology glossary and parallel drafts | Whether the same term is consistent throughout the document and whether translations can back-reference the source text | Extract three terms and check whether their spelling is consistent throughout the document, check the correspondence between translations and source text, and confirm that subsequent nodes continue execution along the branch |
Three common errors
- Symptom: The name and date of the same record do not match between the degree application form and the defense resolution. Cause: The two materials' versions are not synchronized, and different reporting batches lead to inconsistent field values.
- Symptom: The quantity and date do not match between the thesis review report and the defense resolution. Cause: After the interaction completes, the process stalls, the branch does not continue execution according to the selection result, and subsequent nodes are not updated.
- Symptom: The defense resolution is missing a signature or receipt. Cause: An option was selected but the default branch was still taken, the interaction state was not correctly recorded, and the subsequent node did not trigger the supplementary signing process.
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 record, confirm that each option corresponds to one branch, and check that variables and nodeId are correctly referenced in subsequent nodes.
Business testing: Extract three terms and check whether their spelling is consistent throughout the document, verify that translations can back-reference the source text, and confirm that the name, quantity, and date of the same record are consistent across the degree application form, thesis review report, and defense resolution.
- In the node, check the options and branch connections one by one, trigger a user selection node once, and view the node status and branch direction in the run record.
- Reference the selection result variable in a subsequent node and run a trial once to confirm that the process continues execution after the interaction completes, and that the unified terminology glossary and parallel drafts are completed by the subsequent node.