What this category's data looks like
Materials for regular higher education institution admissions enrollment and filing include three categories: enrollment plans, filing rules, and admission rosters. Enrollment plans come from provincial examination institutes and submissions by higher education institutions, and are updated by batch; filing rules are based on annual documents and are slightly adjusted with policy changes; admission rosters are formed from receipts returned by higher education institutions and include candidate numbers, majors, and signature fields. When the three materials enter the workflow, their roles differ: enrollment plans provide major codes and planned numbers, filing rules provide filing ratios and tie-breaking sorting, and admission rosters provide the actual admission list and signature status. Multilingual materials and terminology processing require the same term to be written consistently in the plans, rules, and rosters, and translated names to be traceable back to the source text. The update rhythm advances according to the admissions year and batch nodes; fields include dates, quantities, signatures, and receipts, and versions must be synchronized.
Configuration and implementation checks
This step is executed by workflow nodes (user selection and branches), outputting branch directions and interaction status records. "Unified terminology glossary and comparison draft" is continued and completed by subsequent nodes according to the branches. When a node is triggered, the conversation enters an interactive 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 | Major codes and planned numbers are written consistently in the plan table and the comparison draft, and dates and signature fields are complete | Check major codes, planned numbers, and dates item by item, reference nodeId to locate the node, and view the option branch connections |
| Filing rules | The filing ratio and tie-breaking sorting statements have consistent translated names in the rules document and the terminology glossary, and version numbers are synchronized | Check the rule clauses and terminology glossary translated names, reference variables to retrieve the selection result variable and trial-run the branch |
| Admission roster | Candidate numbers, admitted majors, quantities, and dates correspond in the two materials, and receipts and signatures are not missing | Spot-check three records to compare names, quantities, and dates, and check the interaction status and branch direction in the run records |
| Unified terminology glossary and comparison draft | The same term is written consistently throughout, translated names can be traced back to the source text, and no version is unsynchronized | Spot-check three terms to see whether their writing is consistent throughout, and record the number of references and the quoteMaxToken budget |
Three common errors
- Phenomenon: The major name, quantity, and date for the same candidate do not match between the plan table and the admission roster. Cause: The versions of the two materials are not synchronized, or the source text was not traced back according to the unified terminology glossary during entry.
- Phenomenon: The filing rule clauses and the terminology glossary translated names are inconsistent, and two different written forms appear in the externally released draft. Cause: After the terminology glossary was updated, it was not synchronized to the comparison draft, and the branch direction was not executed according to the new version.
- Phenomenon: The admission roster lacks signatures or receipts, and the materials cannot enter external release. Cause: After the interaction is completed, the process stops, and subsequent nodes do not continue execution according to the branch and collect the missing signatures.
How to verify the setup
Acceptance of this function: trial-run each option one by one, check the branch direction and interaction status in the run records, confirm that each option corresponds to one branch, and that the selection result variable has been passed to subsequent nodes.
Business test: spot-check three terms to see whether their writing is consistent throughout, confirm that translated names can be traced back to the source text, record the number of references and the quoteMaxToken budget, and do not perform an equality comparison between the two.
- In the node, check the options and branch connections one by one, reference
nodeIdto locate them, and trigger once to view the node status in the run records. - In a subsequent node, reference the selection result variable and trial-run once, and check whether the value of that variable corresponds to the branch direction.