What this category's data looks like
The raw materials for self-taught examination registration records and graduation audits include registration archives, course pass certificates, and graduation application forms. The sources are the historical archives of provincial examination offices and current-period applications. The update cadence rolls with examination batches. The field characteristics are name, course name, course count, examination date, review date, handler signature, and receipt number. Registration archives carry the historical registration and grade ledgers, course pass certificates carry the single-subject pass evidence, and graduation application forms carry the graduation application and review opinions. When these three types of materials enter workflow orchestration, the registration archive serves as the source comparison baseline, the course pass certificate serves as the basis for subject-by-subject verification, and the graduation application form serves as the carrier for application and approval, jointly supporting exception tracing and manual review.
Configuration and implementation checks
This step is executed by workflow nodes (user selection and branches), outputting branch directions and interaction state records. The "exception list and review conclusions" are then completed by subsequent nodes continuing execution according to the branches. When the user selection node is triggered, the conversation enters an 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 |
|---|---|---|
| Registration archive | Whether fields, dates, and signatures correspond item by item with the course pass certificate | Check name, course name, course count, and examination date, compare handler signature and receipt, and record differences item by item |
| Course pass certificate | Whether the name, count, and date of the same record are consistent across the registration archive and the graduation application form | Extract course name, course count, and examination date, cross-compare with the other two materials, and mark mismatched items |
| Graduation application form | Whether the version is synchronized and whether signatures or receipts are complete | Check the application version number and review date, inspect the handler signature and receipt number, and list missing items as exceptions |
| Workflow node | Whether options and branch connections correspond one by one | Check options and branch connections one by one in the node, and reference variables and nodeId in subsequent nodes for a trial run |
Three common errors
- Symptom: The course name, count, and date of the same record do not match between the registration archive and the course pass certificate. Cause: The two materials are entered in different steps, and no cross-comparison was performed.
- Symptom: The version of the graduation application form is not synchronized, and the review opinions are inconsistent with the registration archive ledger. Cause: After the version update, the source material was not written back, and the archived copy remained at the old version.
- Symptom: The graduation application form lacks a handler signature or receipt, and the exception cannot be traced to the source material. Cause: Signatures and receipts were not archived together with the materials, and the reviewer cannot sign to confirm.
How to verify the setup
This feature's acceptance: run trial executions option by option, check the branch directions and interaction states in the run records, confirm that options and branch connections correspond one by one, and check whether variables and nodeId are correctly referenced by subsequent nodes.
Business test: create an exception record, see whether it can be traced to the source material, and compare the fields, dates, and signatures of the registration archive, course pass certificate, and graduation application form item by item.
- Check options and branch connections one by one in the node, trigger one run to view the node status in the run records, and confirm that the process continues downward after the interaction is completed.
- Reference the selection result variable in a subsequent node and run a trial execution once, and check whether the exception list and review conclusions are completed by the subsequent node continuing execution according to the branch.