What this category's data looks like
This category's data involves three core types of materials: registration forms, care bonus-point materials, and admission rosters. The registration form is filled in by the candidate and verified by the confirmation point, and contains name, ID number, application level, examination subjects, signature, and date; the care bonus-point materials are submitted by the candidate and stamped by the reviewing department, and contain the bonus-point item, certificate number, reviewer signature, and receipt; the admission roster is generated by the admitting institution by batch, and contains the candidate number, admitted major, admission date, and responsible person's signature. The materials are updated monthly and by batch; the registration stage collects them centrally, the review stage supplements bonus-point certificates, and the admission stage generates and archives the roster. When entering the exception tracing and manual review workflow, the registration form serves as the baseline original record, the bonus-point materials serve as supporting evidence and a source of discrepancies, and the admission roster serves as the object for result verification; the three are aligned by candidate number and batch on fields, dates, and signatures.
Configuration and implementation checks
This step is executed by workflow nodes (user selection and branching), outputting branch directions and interaction state records. The "exception list and review conclusion" is 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 |
|---|---|---|
| Adult college entrance examination registration form | Compare field by field with the care bonus-point materials and the admission roster; check whether name, ID number, application level, date, and signature are consistent | Check the options and branch connections one by one in the node, reference variables and nodeId to locate the record, and trigger one check of the node status in the run records |
| Care bonus-point materials | Check whether the bonus-point item, certificate number, reviewer signature, and receipt are complete, and whether the name, quantity, and date match the same record in the registration form | Reference the selection result variable in a subsequent node and run a trial once, comparing the fields and dates of the two materials |
| Admission roster | Check the candidate number, admitted major, admission date, and responsible person's signature, and whether the name, quantity, and date are consistent with the same record in the registration form and bonus-point materials | Trigger the user selection node once and view the node status and branch direction in the run records |
| Exception list and review conclusion | The exception has original record support and a reviewer signature, and its destination is handed to the responsible person for handling | Create one exception record and see whether it can be traced back to the source material |
Three common errors
- Symptom: The name or ID number of the same candidate does not match between the registration form and the admission roster. Cause: The two forms were entered at different times, versions were not synchronized, and receipt verification was missing.
- Symptom: The care bonus-point materials show as reviewed, but the registration form has no corresponding bonus-point item or date. Cause: The review result was not written back, and the signature or receipt is missing.
- Symptom: The quantity in the admission roster is inconsistent with the batch headcount in the registration form. Cause: The roster was not regenerated after the batch adjustment, and the old version is still in use.
How to verify the setup
Feature acceptance: run a trial for each option, check the branch direction and interaction state in the run records, confirm that each option corresponds to one branch, that the selection result variable has been passed to subsequent nodes, and use variables and nodeId to locate the node.
Business test: create one exception record, see whether it can be traced back to the source material, and check whether the fields, dates, and signatures of the registration form, care bonus-point materials, and admission roster are traceable.
- Check the options and branch connections one by one in the node, trigger the user selection node once, and view the node status and branch direction in the run records.
- Reference the selection result variable in a subsequent node and run a trial once, confirming that the exception list and review conclusion are completed by subsequent nodes continuing execution according to the branch.