What this category's data looks like
Admissions enrollment and filing materials for general higher education institutions contain three categories: enrollment plans, filing rules, and admission rosters. Enrollment plans come from provincial admissions offices' issuances and institutions' submissions, and are updated with batch adjustments; fields include institution code, major group, planned number, subject selection requirements, and batch date. Filing rules come from admissions regulations and filing measures, and are revised annually; fields include filing ratio, tie-breaking ranking, voluntary preference grade difference, and withdrawal conditions. Admission rosters come from the admissions site and are generated by round; fields include candidate number, name, filing score, major, admission status, signature, and receipt. When these three categories of materials enter workflow orchestration, their roles differ: enrollment plans and filing rules serve as the basis for branch decisions, while admission rosters serve as the output object for continued execution after interaction. The update rhythm rolls forward by batch and round, and field dates and signatures must be aligned item by item.
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 branch. When a user selection 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 |
|---|---|---|
| Enrollment plan | Institution code, major group, planned number, subject selection requirements, and batch date must be consistent across the two materials, and signatures and receipts must be complete | Check options and branch connections one by one in the node, compare plan fields and dates, and see which signature is missing |
| Filing rules | The versions of filing ratio, tie-breaking ranking, voluntary preference grade difference, and withdrawal conditions must be synchronized, and the rule text must match the dates in the execution records | Trigger once, check the node status in the run records, and verify the rule version and execution date |
| Admission roster | Candidate number, name, filing score, major, and admission status must have consistent names and quantities across the two materials, and receipts must not be missing | Reference variables in subsequent nodes and do a trial run, then compare roster fields and receipts |
| Workflow node | Each option corresponds to one branch, the interaction status is recorded, and the selection result variable has been passed to subsequent nodes | Check nodeId and branch connections, and see whether variables take effect in subsequent nodes |
Three common errors
- Symptom: after selecting a certain option, the default branch is still taken. Cause: options and branch connections were not checked item by item, and the
nodeIdreference does not match expectations. - Symptom: the name, quantity, and date of the same record do not match between the plan and the roster. Cause: versions were not synchronized, and signatures or receipts are missing.
- Symptom: the process stops after the interaction is completed. Cause: the selection result variable was not passed to subsequent nodes, and subsequent nodes did not continue execution according to the branch.
How to verify the setup
Acceptance of this feature: run trials for each option one by one, check the branch directions and interaction status in the run records, and confirm that nodeId and variables take effect in subsequent nodes.
Business testing: check once item by item according to the handover sheet, see which record is missing, and compare the fields, dates, and signatures of the enrollment plan, filing rules, and admission roster.
- Check options and branch connections one by one in the node, and record the branch direction corresponding to each option.
- Trigger an interaction once, check the node status in the run records, and verify whether the selection result variable has been passed to subsequent nodes.