What this category's data looks like
The core materials for material drafting and responsibility handover in primary and secondary school enrollment organizations include three categories: enrollment plans, application material checklists, and admission lists. Enrollment plans come from the education authorities and the school enrollment leadership group, updated by academic year or batch, with fields including enrollment scope, planned number, time nodes, and signature fields; application material checklists come from the admissions office and the information collection post, updated by application stage, with fields including material name, number of copies, original/copy requirements, and submission date; admission lists come from the review group and the publicity post, updated by admission batch, with fields including student name, ID number, admission category, publicity date, and responsible person's signature. When the three types of materials enter the workflow, the enrollment plan serves as the master outline constraining subsequent branches, while the application material checklist and admission list serve as objects of signable drafts and handover records, flowing between nodes with fields, dates, and signatures checked item by item.
Configuration and implementation checks
This step is executed by workflow nodes (user selection and branching), outputting branch directions and interaction state records. "Signable material drafts and handover records" are continued and completed by subsequent nodes according to the branches. When the user selection node is triggered, the conversation enters the interaction state and records the workflow state; after the user completes the selection, execution continues along the branch corresponding to the selected option.
| Object | Check | Verification action |
|---|---|---|
| Enrollment plan | Fields complete, responsible person clear, version and date consistent | Check the options and branch connections one by one in the node, and confirm whether the plan version number, issuance date, and enrollment leadership group signature field are consistent with the references in the application material checklist |
| Application material checklist | Fields complete, responsible person clear, version and date consistent | Reference variables in a subsequent node and run a trial, and check whether the material name, number of copies, and submission date match the name, quantity, and date of the same record in the admission list |
| Admission list | Fields complete, responsible person clear, version and date consistent | Trigger a user selection node once, view the node status in the run record, check whether the signature field and receipt of the branch corresponding to nodeId are complete, and confirm that the publicity date is consistent with the time nodes in the plan |
| Handover record | Fields complete, responsible person clear, version and date consistent | Reference variables in a subsequent node and run a trial, and check whether the responsible persons of both parties in the handover, handover date, and version number are synchronized with the material draft of the previous step |
Three common errors
- Symptom: The name, ID number, or date of the same student does not match between the application material checklist and the admission list. Cause: The two materials are drafted separately, lacking cross-material field comparison and a unified version number.
- Symptom: The enrollment plan has been updated, but the application material checklist still references the old version's time nodes and planned number. Cause: The version was not synchronized, and the version number and date were not checked during handover.
- Symptom: The admission list lacks the responsible person's signature or receipt, and cannot proceed to the next step for signing acceptance. Cause: The signature field and receipt were not included in the handover record field checklist, and missing items were not blocked.
How to verify the setup
Feature acceptance: Run trials option by option, check the branch directions and interaction states in the run record, confirm that variables has been passed to subsequent nodes and that the branch corresponding to nodeId is correct, and that the process continues execution without stopping after the interaction is completed.
Business test: Draft one copy according to the template and complete one handover, and see whether missing items are blocked.
- Check the options and branch connections one by one in the user selection node, confirm that each option corresponds to one branch, and avoid still taking the default branch after selecting a certain option.
- Reference
variablesin a subsequent node and run a trial, and check whether the names, quantities, dates, and signatures of the enrollment plan, application material checklist, and admission list are consistent.