What this category's data looks like
Materials for regular higher education institution admissions enrollment and filing mainly consist of enrollment plans, filing rules, and admission rosters published by provincial admissions and examination institutions. The sources are admissions management departments and university admissions offices. The update cadence rolls forward as batches progress. Fields include institution-major groups, planned numbers, filing cutoff scores, admission order, signature fields, and receipt dates. When enrollment plans enter the workflow, they serve as the plan baseline; filing rules serve as the basis for decision branches; admission rosters serve as result records. Together, the three support exception tracing and manual review.
Configuration and implementation checks
This step is executed by workflow nodes (user selection and branching), outputting branch directions and interaction status records. The "exception list and review conclusions" are then completed by subsequent nodes continuing execution according to the branches.
| Object | Check | Verification action |
|---|---|---|
| Enrollment plan | Whether the institution-major group name, planned number, batch date, and signature field are consistent with the filing rules | Check options and branch connections one by one in the node, reference variables to record plan fields, and view the run record after a trial run |
| Filing rules | Whether the filing ratio, tie-breaking ranking, withdrawal conditions, and plan version are synchronized | Trigger a user selection node once, check whether the interaction status is recorded, and use nodeId to locate the branch direction |
| Admission roster | Whether the candidate number, admitted major, date, and receipt signature correspond to the plan and rules | Reference the selection result variable in subsequent nodes and run a trial once, checking roster fields against the original records |
| Exception record | Whether the name, quantity, and date of the same record in the plan and roster do not match | Create an exception record, trace it back to the source materials along variables and nodeId, and check the signature and receipt |
Three common errors
- Symptom: The same candidate's major name, planned number, and date do not match between the plan and the roster. Cause: The two material versions are not synchronized, and field definitions are inconsistent.
- Symptom: The review conclusion lacks a signature or receipt, and the responsible person cannot process it. Cause: The manual review step leaves no trace, and the signature field and receipt date are not filled in.
- 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
Acceptance for this feature: Run trials for each option one by one, check the branch direction and interaction status in the run record, and confirm that variables and nodeId are correctly referenced in subsequent nodes.
Business test: Create an exception record, see whether it can be traced back to the source materials, and check the names, quantities, dates, and signatures of the enrollment plan, filing rules, and admission roster.
- In the user selection node, check options and branch connections one by one, trigger it once, and then view the node status and branch direction in the run record.
- Reference the selection result variable in subsequent nodes and run a trial once to confirm that the exception list and review conclusions are completed by subsequent nodes continuing execution according to the branches.