What this category's data looks like
This page focuses on the graduate admissions re-examination and admission category. Materials include the re-examination plan, candidate score sheets, and adjustment lists. The re-examination plan comes from the graduate school of the admitting unit and is updated by annual admissions cycle; its fields include specialty direction, re-examination subjects, weights, time and location, and signature fields. Candidate score sheets come from the preliminary and re-examination scoring stages and are updated by batch; their fields include candidate number, name, scores for each subject, total score, and signature. Adjustment lists come from the adjustment system and departmental confirmation and are updated by round; their fields include adjustment preference, candidate number, score, proposed admission opinion, and receipt. When these three types of materials enter workflow orchestration, the re-examination plan serves as the basis for branch decisions, the candidate score sheets serve as the object of data verification, and the adjustment lists serve as the source of handover records, respectively taking on the roles of rules, data, and evidence.
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 along the branches.
| Object | Check | Verification action |
|---|---|---|
| Re-examination plan | Whether the specialty direction, re-examination subjects, weights, time and location, and signature fields are consistent with the dates and names in the candidate score sheets and adjustment lists | Check the options and branch connections one by one in the node, reference variables to view the plan fields, trigger a user selection node once, and view the node status and branch direction in the run records |
| Candidate score sheets | Whether the candidate number, name, scores for each subject, total score, and signature match the name, quantity, and date of the same record in the adjustment lists | Reference the selection result variable in a subsequent node and run a trial once, check the branch direction corresponding to nodeId, and check the fields and signatures of the score sheets and adjustment lists |
| Adjustment lists | Whether the adjustment preference, candidate number, score, proposed admission opinion, and receipt are synchronized with the versions of the re-examination plan and candidate score sheets | Check the options and branch connections one by one in the node, view the interaction status in the run records, check the receipt and signature, and confirm version synchronization |
Three common errors
- Symptom: The specialty name and date for the same candidate do not match between the re-examination plan and the adjustment list. Cause: The two materials are updated on different schedules, and fields and signatures were not checked item by item against the handover form.
- Symptom: The quantity and total score are inconsistent between the candidate score sheets and the adjustment lists. Cause: Versions are not synchronized; one material has been updated while the other is still the old version, and receipt confirmation is missing.
- 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 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, and confirm the correspondence among variables, nodeId, and the options.
Business testing: check item by item once against the handover form, see which record is missing, and focus on checking the fields, dates, and signatures of the re-examination plan, candidate score sheets, and adjustment lists.
- Check the options and branch connections one by one in the node, trigger a user selection node once, and view the node status and branch direction in the run records.
- Reference the selection result variable in a subsequent node and run a trial once, check
variablesandnodeId, and confirm that the process continues execution after the interaction is completed.