What this category's data looks like
This category's data involves three core types of materials: registration records, course qualification certificates, and graduation application forms. Registration records are generated by the provincial examination office after registration and updated as the examination process progresses; fields include name, examination registration number, ID number, major code, course name, credits, score, examination date, and review status. Course qualification certificates are supplemented by the main examining institution after each score release; fields include course code, qualification certificate number, issuance date, and the main examining institution's seal. Graduation application forms are submitted by candidates when applying for graduation; fields include name, major, number of courses, total credits, application date, employer's opinion, and reviewer's signature. When these three types of materials enter workflow orchestration, registration records serve as the baseline ledger, course qualification certificates serve as the item-by-item comparison source, and graduation application forms serve as the summary verification object; each assumes a different role, forming a complete chain for material verification and discrepancy location.
Configuration and implementation checks
This step is executed by workflow nodes (user selection and branching), outputting branch directions and interaction state records. The "discrepancy list" is completed by subsequent nodes continuing execution according to the branch. 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 records | Name, examination registration number, and ID number match the course qualification certificates field by field | In the node, check the options and branch connections one by one, reference variables and nodeId, and trigger once to view the node status in the run records |
| Course qualification certificates | Course code, qualification certificate number, and issuance date match the registration record entries | Trigger once, view the node status in the run records, and check whether the date and seal fields are synchronized |
| Graduation application forms | Number of courses, total credits, and application date match the summary of registration records and course qualification certificates | In subsequent nodes, reference the selection result variable and run a trial once, and check whether the signature and receipt are complete |
| Discrepancy list | Inconsistent items in name, quantity, and date have been located and annotated with the source material | In subsequent nodes, reference this variable and run a trial once, outputting branch directions and interaction state records |
Three common errors
- Symptom: The course name or credits of the same record do not match between the registration records and the course qualification certificates. Cause: Versions are not synchronized; after the qualification certificate is supplemented, it is not written back to the registration records, resulting in inconsistent fields in the two places.
- Symptom: The number of courses on the graduation application form is inconsistent with the summary quantity of the course qualification certificates. Cause: Some qualification certificates lack signatures or receipts and are not included in the summary, resulting in a quantity discrepancy.
- Symptom: After selecting an option, the default branch is still followed, and the discrepancy list is not generated as expected. Cause: The options and branch connections were not checked one by one, and the process stalls after the interaction is completed.
How to verify the setup
Acceptance of this feature: run trials for each option one by one, check the branch directions and interaction states in the run records, and confirm that variables, nodeId, and the selection result variable have been passed to subsequent nodes.
Business test: use one real record to find fields inconsistent with the ledger, locate discrepancies in name, quantity, and date, and submit them to the reviewer to confirm write-back.
- In the node, check the options and branch connections one by one, and trigger once to view the node status and branch directions in the run records.
- In subsequent nodes, reference the selection result variable and run a trial once, and check whether the discrepancy list is generated by continuing execution according to the branch.