What this category's data looks like
In the general higher education institution admissions enrollment and filing scenario, materials mainly come from three categories: enrollment plans, filing rules, and admission rosters. Enrollment plans are published by the provincial admissions office and updated by batch and subject category; their fields include institution code, major name, planned number, selected examination subjects, and remarks. Filing rules are published by the provincial admissions office before filing; their fields include filing ratio, tie-breaking ranking, volunteer grade difference, date, and signature/seal. Admission rosters are returned by higher education institutions after the admission of each batch is completed; their fields include candidate number, name, admitted major, admitted number, signature, and receipt. When these three categories of materials enter workflow orchestration, enrollment plans and filing rules serve as baseline materials, and admission rosters serve as materials to be verified; the name, quantity, date, and signature of the same record are compared item by item, discrepancy fields are located, and a discrepancy list is formed. In terms of update cadence, enrollment plans and filing rules are updated by batch node, while admission rosters are returned in batches according to admission progress; version synchronization and signature receipts are common verification points.
Configuration and implementation checks
This step is executed by workflow nodes (user selection and branching), outputting branch direction and interaction state records. The "discrepancy list" is then completed by subsequent nodes continuing execution according to the branch. When the user selection node is triggered, the conversation enters an 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 | Check whether the institution code, major name, planned number, selected examination subjects, and publication date are consistent with the filing rules | Check the options and branch connections one by one in the node, trigger once and then view the node status in the run record, and reference the selection result variable for a trial run |
| Filing rules | Check whether the filing ratio, tie-breaking ranking, volunteer grade difference, date, and signature are synchronized with the enrollment plan | Reference the selection result variable in a subsequent node and run a trial once to confirm the branch direction and interaction state record |
| Admission roster | Check whether the candidate number, name, admitted major, admitted number, date, and signature receipt are consistent with the ledger | Check the options and branch connections one by one in the node, trigger once and then view the node status in the run record |
| Discrepancy list | Check whether the name, quantity, and date of the same record do not match across the two materials, whether the versions are not synchronized, and whether the signature or receipt is missing | Reference the selection result variable in a subsequent node and run a trial once to confirm the branch direction and interaction state record |
Three common errors
- Symptom: The major name, admitted number, and date of the same candidate do not match between the admission roster and the enrollment plan. Cause: The versions of the two materials are not synchronized, and the return batch and publication batch are misaligned.
- Symptom: The signature or receipt in the filing rules is missing, but the roster still enters verification. Cause: The material receiving step does not validate the signature/seal and receipt fields, and missing items are not intercepted.
- Symptom: After selecting an option, the default branch is still taken, and the process stops after the interaction is completed. Cause: The options and branch connections were not checked one by one, and the selection result variable was not passed to subsequent nodes.
How to verify the setup
Feature acceptance: run trials for each option one by one, check the branch direction and interaction state in the run record, confirm that options and branches correspond one to one, that the selection result variable has been passed to subsequent nodes, and that variables and nodeId are queryable in the run record.
Business test: use one real record to find fields inconsistent with the ledger, and compare the name, quantity, date, and signature receipt across the three materials: enrollment plan, filing rules, and admission roster.
- Check the options and branch connections one by one in the node, trigger once and then view the node status in the run record, and confirm that the interaction state is recorded.
- Reference the selection result variable in a subsequent node and run a trial once to confirm the branch direction and interaction state record, and record the tokens and array length of the referenced text.