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 contains the candidate's basic information, application level and subject category, photo, signature, and date; the care bonus-point materials contain the certificate type, issuing unit, number, validity period, and review signature; the admission roster contains the candidate number, admitted major, study mode, admission date, and responsible person's signature. The materials come from candidate submissions, review departments, and admissions institutions, and are updated in batches along with registration, review, and admission batches. When entering workflow orchestration, the registration form serves as the basis for identity and application, the care bonus-point materials serve as the basis for branch judgment, and the admission roster serves as the final result record. The fields, dates, and signatures of the three types of materials must correspond item by item, names, quantities, and dates must remain consistent across materials, versions must be synchronized, and receipts must be retained.
Configuration and implementation checks
This stage is executed by workflow nodes (user selection and branches), outputting branch directions and interaction status records. The externally available entry points and authorization scope are completed by subsequent nodes continuing execution according to the branches. When the user selection node is triggered, the conversation enters an interactive 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 |
|---|---|---|
| User selection node | Each option corresponds to one branch, and options and branch connections correspond one by one | Check the options and branch connections one by one in the node, and after a trial run, view the branch direction in the run record |
| Registration form | Fields, dates, and signatures must correspond consistently with the care bonus-point materials and admission roster | Check the candidate name, candidate number, application level, signature, and date, and compare names and quantities across materials |
| Care bonus-point materials | Certificate type, number, validity period, and review signature must be complete and versions synchronized | Check the issuing unit, number, validity period, and review signature, and inspect whether signatures or receipts are missing |
| Admission roster | Admitted major, study mode, admission date, and signature must be consistent with the registration form | Check the candidate number, admitted major, admission date, and responsible person's signature, and confirm whether there are version synchronization issues |
Three common errors
- Symptom: The same candidate's name or candidate number does not match between the registration form and the admission roster. Cause: The two entries come from different sources, and cross-material field comparison and version synchronization were not performed.
- Symptom: The number or validity period of the care bonus-point materials is inconsistent with the date of the review record. Cause: After the materials were updated, they were not synchronized to the branch judgment basis, and the old version is still in circulation.
- Symptom: The admission roster lacks the responsible person's signature, or the candidate did not receive a receipt. Cause: The process stopped or did not continue execution after the interaction was completed, and the signature and receipt steps were skipped.
How to verify the setup
Acceptance of this feature: run trials for each option one by one, and check the branch direction and interaction status in the run record; reference the selection result variable in subsequent nodes to confirm it has been passed to subsequent nodes; check the correspondence between nodeId and variables in the run record.
Business test: access once with a restricted identity, see whether the visible scope matches the setting, and confirm that unauthorized content is not visible.
- In the user selection node, check the options and branch connections one by one, and confirm that each option corresponds to one branch.
- Reference the selection result variable in a subsequent node and run a trial once, then view the transfer of
nodeIdandvariablesin the run record.