What this category's data looks like
This category's data looks like this: Self-taught examination registration records and graduation review involve three types of core materials: the registration record file records the candidate's basic information, the course pass certificate marks the score and date for each subject, and the graduation application form summarizes the courses and signatures. The registration record file is updated by the provincial examination office after each registration, the course pass certificate is generated synchronously with the release of single-subject scores, and the graduation application form is filled out jointly by the candidate and the study assistance center after all courses are passed. The three types of materials have different roles when entering the workflow: the registration record file serves as the master data source providing identity and major information, the course pass certificate serves as the basis for course completion and is compared item by item, and the graduation application form serves as the summary output carrying signatures and receipts. Field characteristics are concentrated in name, examination registration number, course code, score, pass date, major name, signature, and seal position. The update rhythm is based on examination sessions; within the same examination session, the course names, quantities, and dates in the pass certificates and registration record file must remain consistent, and the version is synchronized with each review action.
Configuration and implementation checks
Configuration and implementation checks: This step is executed by workflow nodes (user selection and branching), outputting branch directions and interaction state records. The material drafts that can be issued and the handover records are continued and completed by subsequent nodes according to the branches. When a 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 record file | Whether the name, examination registration number, and major name are character-for-character consistent with the course pass certificate and graduation application form, and whether the dates fall within the same examination session | Check the options and branch connections one by one in the node, compare the course names, quantities, and dates in the registration record file and the pass certificate; reference variables to pass registration record fields, and run a trial to see the values retrieved by subsequent nodes |
| Course pass certificate | Whether the course code, score, and pass date are consistent with the records in the registration record file, and whether the version is synchronized | Trigger a user selection node once and check the node status in the run record; reference nodeId in subsequent nodes to locate the pass certificate branch, and verify the name, quantity, and date of the same record in the two materials |
| Graduation application form | Whether the signature and receipt are complete, and whether the version and date are consistent with the registration record file and pass certificate | Check the options and branch connections one by one in the node, inspect the signature field and receipt field of the graduation application form; reference variables to pass application form fields, and run a trial to see whether missing signatures are blocked |
| Handover record | Whether the responsible person is clear, whether the version and date are consistent, and whether the receipt is returned | Trigger a user selection node once and check the node status in the run record; reference nodeId in subsequent nodes to locate the handover branch, and verify the version, date, and signature of the handover record and the graduation application form |
Three common errors
- Symptom: The name, quantity, and date of the same course do not match between the registration record file and the course pass certificate. Cause: The two materials are entered separately, and the fields are not compared item by item in the node.
- Symptom: The version of the graduation application form is not synchronized, and signatures or receipts are missing. Cause: After the version is updated, the user selection node is not triggered to reconfirm the branch.
- Symptom: After selecting an option, the default branch is still followed, and the process stops after the interaction is completed. Cause: The options and branch connections are not checked one by one, and the interaction state is not recorded correctly.
How to verify the setup
How to verify the setup: Acceptance of this feature: run trials for each option one by one, and check the branch direction and interaction state in the run record; check the options and branch connections one by one in the node, and reference variables and nodeId to locate the values retrieved by subsequent nodes.
Business test: draft one according to the template and complete one handover, and see whether missing items are blocked.
- Check the options and branch connections one by one in the node, and confirm that each option corresponds to one branch.
- Trigger a user selection node once and check the node status in the run record, confirming that the interaction state is recorded and the selection result variable has been passed to subsequent nodes.