What this category's data looks like
This page is intended for primary and secondary school admissions organizations. Materials come from three categories: admissions plans, application material checklists, and admission lists. The admissions plan provides batches, dates, and signature fields; the application material checklist records student names, ID numbers, number of material copies, and receipts; the admission list records admission sequence numbers, names, dates, and approval signatures. The three types of materials are updated centrally by admissions season, with one round of versions each for application deadline, qualification review, and admission announcement. Fields are mainly names, quantities, dates, and signatures, and the same student often appears multiple times across different materials. When entering this function, the admissions plan serves as the basis for judgment, the application material checklist serves as the object to be verified, and the admission list serves as the comparison benchmark. Together, the three support discrepancy localization.
Configuration and implementation checks
This step is executed by workflow nodes (user selection and branching), outputting branch directions and interaction state records. When the user selection node is triggered, the conversation enters an interactive state and records the workflow state. After the user completes the selection, execution continues along the branch corresponding to the selected option. The discrepancy list is then completed by subsequent nodes continuing execution according to the branch.
| Object | Check | Verification action |
|---|---|---|
| Admissions plan | Check whether the batch, date, and signature fields are consistent with the application material checklist | Compare the time nodes and signature requirements in the plan item by item, and check the options and branch connections one by one in the node |
| Application material checklist | Check whether the name, ID number, number of material copies, and receipt are consistent with the admission list | Compare the fields of the two materials student by student, and reference variables to record discrepancy items |
| Admission list | Check whether the admission sequence number, name, date, and approval signature are complete | Check records missing signatures or receipts, and reference nodeId in subsequent nodes to locate the source |
| User selection node | Check whether the branch corresponding to each option is consistent with the expected direction | Trigger once to view the node status in the run record, and confirm that the selection result variable has been passed to subsequent nodes |
Three common errors
- Phenomenon: The name or date of the same student does not match between the application material checklist and the admission list. Cause: The two materials are entered separately, and no field-level comparison has been performed.
- Phenomenon: After the admissions plan is updated, the application material checklist still uses the old version. Cause: The versions are not synchronized, and there is a lack of unified version marking and write-back.
- Phenomenon: The admission list contains records missing signatures or receipts. Cause: The signature fields and receipt fields have not been included in the verification scope.
How to verify the setup
In the user selection node, check the options and branch connections one by one, and confirm that each option corresponds to one branch.
Trigger an interaction once, view the node status in the run record, and confirm that the selection result variable has been passed to subsequent nodes.
- This function's acceptance: trial-run each option one by one, check the branch direction and interaction state in the run record, and confirm that
variablesandnodeIdare correctly referenced in subsequent nodes. - Business test: use one real record to find fields inconsistent with the ledger, form a discrepancy list, submit it to the reviewer for confirmation, and write it back.