What this category's data looks like
Self-taught examination records and graduation review materials mainly consist of examination registration archives, course pass certificates, and graduation application forms. They originate from successive archiving by provincial examination offices and main examining institutions, and their update cadence advances with each examination registration, exemption, transfer, and graduation application batch. Examination registration archives record name, examination registration number, ID number, and enrollment status; course pass certificates record course name, pass date, and score; graduation application forms record major name, intended graduation date, and signature field. When materials enter workflow orchestration, examination registration archives serve as the entry point for identity and enrollment verification, course pass certificates serve as the basis for comparing course counts and dates, and graduation application forms serve as the confirmation of final approval and signature receipt. The field definitions of the three types of materials must be aligned item by item during deployment handover; only when version, connection, and task records are consistent can they be handed over to operations or the next shift.
Configuration and implementation checks
This step is executed by workflow nodes (user selection and branching), outputting branch directions and interaction status records. "Handover-ready deployment status and operation records" are then completed by subsequent nodes continuing execution according to the branches. When a node is triggered, the conversation enters an interaction 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 |
|---|---|---|
| User selection node | Each option corresponds to one branch; options and branch connections must correspond one by one | Check options and branch connections one by one in the node, and after a trial run inspect the branch direction in the run records |
| Examination registration archive | Name, examination registration number, and enrollment status are consistent item by item with the course pass certificate and graduation application form | Compare the name, examination registration number, date, and signature field in the two materials, and record inconsistent items |
| Course pass certificate | Course name, pass date, and quantity are consistent with the course list in the graduation application form | Check the name and date course by course, count differences in the number of courses, and annotate the version source |
| Graduation application form | Major name, intended graduation date, signature, and receipt are complete | Check the signature field and receipt, confirm version synchronization, then reference variables and nodeId to locate the record |
Three common errors
- Symptom: The name and date of the same record do not match between the examination registration archive and the graduation application form. Cause: The versions of the two materials are not synchronized, and the archiving batches differ.
- Symptom: The course count and names in the course pass certificate and the graduation application form are inconsistent. Cause: Exemption or transfer records were not written back, and the quantity definitions are not unified.
- Symptom: After selecting an option, the default branch is still followed, and the process stops after the interaction is completed. Cause: Branch connections were not checked one by one, and the selection result variable was not passed to subsequent nodes.
How to verify the setup
Feature acceptance: Run a trial for each option one by one, check the branch direction and interaction status in the run records, confirm that the selection result variable has been passed to subsequent nodes, and run a trial once in a subsequent node referencing variables and nodeId.
Business testing: Check item by item according to the handover form, see which record is missing, and confirm that version, connection, and task records are consistent.
- Check options and branch connections one by one in the node, and trigger once to inspect the node status in the run records
- Reference the selection result variable in a subsequent node and run a trial once to confirm that the branch direction is consistent with the interaction status record