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. Registration forms are filled out by candidates and preliminarily reviewed by registration points; fields include name, ID number, application level, subject category, registration date, and signature. Care bonus point materials are submitted by candidates and rechecked by the admissions office; fields include bonus item, certificate number, review date, and seal. Admission rosters are reported by admitting institutions and reviewed by the provincial admissions office; fields include candidate number, admitted major, admission date, and responsible person's signature. Materials enter intensively by registration season, with weekly and monthly reporting rhythms. When entering workflow orchestration, registration forms serve as the base record source, care bonus point materials serve as additional condition records, and admission rosters serve as final result records; the three are linked by candidate number and respectively assume the input roles of progress records and statistical verification.
Configuration and implementation checks
This step is executed by workflow nodes (user selection and branching), outputting branch direction and interaction status records. The "progress table and statistical scope description" is continued and completed by subsequent nodes according to the branch. When the user selection node is triggered, the dialogue 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 |
|---|---|---|
| Registration form | Whether fields, dates, and signature are consistent with the care bonus point materials | Check whether the name, ID number, and registration date of the same candidate in the registration form and care bonus point materials are consistent, and check whether the signature and receipt are complete; view the interaction status corresponding to nodeId in the run record |
| Care bonus point materials | Whether the bonus item, certificate number, and review date match the admission roster | Check whether the bonus item, quantity, and date of the same record in the care bonus point materials and admission roster are consistent, and check whether the versions are synchronized and whether seals are missing; reference variables to see whether the selection result variable is passed to subsequent nodes |
| Admission roster | Whether the candidate number, admitted major, admission date, and signature match the registration form | Check whether the candidate number, major, and date of the same candidate in the admission roster and registration form are consistent, and check whether the responsible person's signature and receipt are complete; trial-run each option one by one, and verify the branch direction of nodeId and variables |
| Progress table and statistical scope description | Whether the record count and statistical count match, and whether the scope is written in the header | Use one week of records to check the total, check whether the scope and exceptions are clearly stated, and confirm that the statistical count can be traced back to the registration form, care bonus point materials, and admission roster |
Three common errors
- Phenomenon: The name, quantity, and date of the same candidate in the registration form and care bonus point materials do not match. Cause: The two materials are entered in different steps, lacking unified candidate number association and cross-checking.
- Phenomenon: The admission roster and registration form versions are not synchronized, causing deviations in the statistical count. Cause: Updates to materials do not trigger re-verification, and the old version is still referenced.
- Phenomenon: Care bonus point materials lack a signature or receipt, and the admission roster lacks the responsible person's signature. Cause: The review step does not check seals item by item, and receipt archiving is omitted during material circulation.
How to verify the setup
This function's acceptance: trial-run each option one by one, check the branch direction and interaction status in the run record, confirm that the option corresponding to nodeId is consistent with the branch connection, and that variables has been passed to subsequent nodes.
Business test: use one week of records to check the total, see whether the scope and exceptions are clearly stated, and confirm that the record count and statistical count match and that the scope is written in the header.
- In the user selection node, check the options and branch connections one by one, and after triggering once, view the node status in the run record.
- Reference the selection result variable in a subsequent node and trial-run once to confirm that the process continues downward after the interaction is completed.