What this category's data looks like
The materials for self-taught examination records and graduation review mainly come from provincial examination office record archives, course qualification certificates, graduation application forms, and their receipts. Record archives are updated by examination session and admission ticket number; course qualification certificates are supplemented on a rolling basis with each batch of score releases; graduation application forms are submitted centrally during the application window; receipts and signatures are completed after the review node. Field characteristics center on name, ID number, course code, course name, credits, qualification date, application batch, signature, and receipt status. The same record often exists in two forms: paper scan and typed draft. After entering workflow orchestration, record archives assume the role of the master copy for identity and historical scores, course qualification certificates assume the role of single-subject qualification evidence, and graduation application forms assume the role of current application and approval. The three are routed through user selection nodes to the terminology unification and comparison draft generation path.
Configuration and implementation checks
This stage is executed by workflow nodes (user selection and branching), outputting branch direction and interaction status records. The unified terminology table and comparison draft are completed by subsequent nodes continuing execution along the branch. When a node is triggered, the dialogue enters an interactive state and records the workflow status; after the user completes the selection, execution continues along the branch corresponding to the selected option.
| Object | Check | Verification action |
|---|---|---|
| Record archives | The name, ID number, course code, and qualification date in the record archive fields must correspond item by item with the course qualification certificates, and dates must not be inverted | Check the options and branch connections one by one in the node, reference variables and nodeId, and after a trial run check the node status in the run records |
| Course qualification certificates | The course name, credits, and qualification date on the course qualification certificates must be consistent with the same course records in the record archives, and the quantity and batch must not be misaligned | Sample three course names and check their wording throughout the document, and compare whether the names, quantities, and dates on the qualification certificates and archives match |
| Graduation application forms | The application batch, signature, and receipt status of the graduation application form must be consistent with the summary results of the record archives and course qualification certificates; if signature or receipt is missing, it must not enter publication | Reference the selection result variable in subsequent nodes and run a trial once, and check whether the application form signature and receipt are complete |
| User selection node | Each option corresponds to one branch, the interaction status is recorded when entering the node, and the selection result variable has been passed to subsequent nodes | Trigger once, check the node status and branch direction in the run records, and confirm that the default branch was not taken |
Three common errors
- Symptom: The name, quantity, and date of the same course do not match in the two materials. Cause: The typed draft and scanned copy were not updated synchronously, and the versions were not synchronized, causing the old draft to overwrite the new draft.
- Symptom: The graduation application form is missing a signature or receipt but is still pushed into the publication path. Cause: The review node did not write back the signature and receipt status, and the branch judgment lacks this field.
- Symptom: After selecting an option, the default branch is still taken, and the process stops after the interaction is completed. Cause: The options and branch connections were not checked one by one, and the selection result variable was not referenced in subsequent nodes.
How to verify the setup
Acceptance of this feature: run trials for each option one by one, check the branch direction and interaction status in the run records, confirm that each option corresponds to one branch, that the selection result variable has been passed to subsequent nodes, and record the tokens of variables, nodeId, and the referenced text, with the array count recorded separately.
Business testing: sample three terms and check whether their wording is consistent throughout the document, verify that the same term is consistent throughout the document and that the translated name can refer back to the original text, and confirm that the names, quantities, dates, and signature receipts of the record archives, course qualification certificates, and graduation application forms match.
- Check the options and branch connections one by one in the node, and trigger once to check the node status in the run records
- Reference the selection result variable in subsequent nodes and run a trial once, and check the situation where the same session repeatedly enters the interaction