What this category's data looks like
This page addresses the enrollment plans, application material checklists, and admission lists of primary and secondary school enrollment organizations. These materials come from the daily submissions of school admissions offices, grade groups, and academic affairs offices, and are updated in batches according to enrollment batches and review cycles. Plans focus on process nodes and responsibility signatures, checklists focus on student names, ID numbers, number of materials, and submission dates, and admission lists focus on batches, admission conclusions, and signatures of responsible persons. When materials enter the exception tracing and manual review workflow, the plan serves as the basis for judgment and the version baseline, while the checklist and list serve as the comparison source and the object to be verified. Together, the three support the generation of the exception list and the finalization of review conclusions.
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 completed by subsequent nodes continuing execution according to the branches. Options and branches are checked one by one in the nodes, and interaction status is recorded in the run records.
| Object | Check | Verification action |
|---|---|---|
| Enrollment plan | Whether the version number, release date, and signature field are consistent with the current batch | Check the plan version and signature page, and confirm in the run records the nodeId and referenced variables when this material enters the branch |
| Application material checklist | Whether the same student's name, number of materials, and submission date are consistent between the checklist and the list | Extract one record and compare field by field; mark missing signatures or receipts as exceptions, and record the variables reference values |
| Admission list | Whether the batch, admission conclusion, and responsible person's signature are complete | Check the list batch and signature field, compare the names and quantities in the checklist, and write inconsistent items into the exception list for review |
| Exception record | Whether there is original record support and whether the reviewer has signed | Trace back along the branch to the source material, and confirm the original record identifier and signature information carried in variables |
Three common errors
- Symptom: The same student's name, number of materials, or date does not match between the checklist and the list. Cause: The two materials are entered separately by different nodes, and no field-level comparison is performed at the branch merge point.
- Symptom: The plan has already changed versions, but the checklist is still submitted according to the old version's fields. Cause: The version was not synchronized, and the branch judgment only recognizes options without verifying the material version identifier.
- Symptom: The review conclusion lacks a signature or receipt, and the exception record cannot be closed. Cause: The process stops after the interaction is completed, and subsequent nodes do not continue executing signature collection according to the branch.
How to verify the setup
This feature acceptance: trial-run each option, check the branch direction and interaction status in the run records, and confirm that each option corresponds to one branch and that the selection result variable has been passed to subsequent nodes.
Business test: create an exception record, see whether it can be traced to the source material, and check whether the exception list and review conclusions are completed by subsequent nodes continuing execution according to the branch.
- Check the options and branch connections one by one in the nodes, trigger once, and then view the node status and
nodeIdin the run records. - Reference the selection result variable in a subsequent node and trial-run once to confirm that the original record identifier carried in
variablescan be used to trace back to the source material.