What this category's data looks like
This category's data looks like this: The material drafting and responsibility handover for general higher education institution admissions enrollment and filing involves three types of materials: enrollment plans, filing rules, and admission rosters. Enrollment plans come from the institution-specific and major-specific plans issued by the provincial admissions authority and are updated by batch and subject category; filing rules come from admissions documents and institutional charters and are adjusted by batch and preference model; admission rosters are generated by round and include candidate number, name, score, major, and admission status. When the three types of materials enter the workflow, enrollment plans and filing rules serve as the drafting basis, and admission rosters serve as the verification draft, jointly supporting signable material drafts and handover records. Field characteristics center on names, quantities, dates, and signatures: the same candidate's name and major name must be consistent across the two materials, the planned number and admitted number must correspond, the filing date and admission date must fall within the same batch cycle, and signatures and receipts must be complete. Materials are initiated by batch and updated by round; at handover they are locked by version and date, and missing items are intercepted by nodes.
Configuration and implementation checks
Configuration and implementation checks: This step is executed by workflow nodes (user selection and branching), outputting branch directions and interaction status records. Signable material drafts and handover records are completed by subsequent nodes continuing execution according to the branch. When a 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 | Whether the name, quantity, date, and signature are consistent with the filing rules | Check the options and branch connections one by one in the node, compare the plan name, planned number, and filing date, and inspect the signature field |
| Filing rules | Whether the batch, preference model, and filing ratio correspond to the admission roster | Trigger a user selection node once, view the node status in the run record, and verify the rule version and roster round |
| Admission roster | Whether the candidate name, major name, admitted number, and planned number match | Reference the selection result variable in a subsequent node and run a trial once, and compare the names and quantities among the roster, plan, and rules |
| Handover record | Whether the responsible person, version, date, and receipt are complete | Verify the signature and receipt in the handover record, confirm that the version and date are consistent, and missing items are intercepted by the node |
Three common errors
- Symptom: The same candidate's name or major name does not match across the two materials. Cause: During drafting, the admission roster was not used as the draft for field-by-field comparison, and names and quantities were not locked.
- Symptom: The filing rule version and the admission roster round are out of sync, and the dates do not match. Cause: When materials were updated by batch, the version was not synchronized, and the old rules were still referenced.
- Symptom: The handover record lacks a signature or receipt, and the next step cannot sign for acceptance. Cause: The responsible person was not specified in the node, and the signature field and receipt field were not checked during handover.
How to verify the setup
How to verify the setup: Acceptance for this feature: run trials option by option, check the branch direction and interaction status in the run record, confirm that the selection result variable has been passed to subsequent nodes, and that nodeId and variables are queryable in the run record.
Business test: Draft one copy according to the template and complete one handover, and see whether missing items are intercepted.
- Check the options and branch connections one by one in the node to ensure each option corresponds to one branch.
- Reference the selection result variable in a subsequent node and run a trial once to confirm that
variablesandnodeIdare referenced correctly.