What this category's data looks like
In the drafting of materials and handover of responsibility for college admissions physical examination organization, three types of materials are involved: physical examination forms, re-examination applications, and notices of restricted majors. Physical examination forms are filled out and signed by the examination department, re-examination applications are initiated by the admissions office or the university hospital, and notices of restricted majors are issued by the admissions office based on the physical examination conclusions. Material sources are dispersed, and the update rhythm is synchronized with admissions batches and re-examination arrangements. Field characteristics include name, candidate number, physical examination items, conclusion, date, signature, and receipt. When these three types of materials enter workflow orchestration, the physical examination form serves as the basic record, the re-examination application serves as the process record, and the notice of restricted majors serves as the result notification; each assumes a different role, and names, quantities, dates, and versions must remain consistent during handover.
Configuration and implementation checks
This step is executed by workflow nodes (user selection and branching), outputting branch directions and interaction state records. The material drafts that can be issued and the handover records are completed by subsequent nodes continuing execution according to the branches. 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 |
|---|---|---|
| Physical examination form | Fields complete, responsible person clear, version and date consistent | Check name, candidate number, physical examination items, conclusion, date, and signature; verify options and branch connections one by one in the node, and view node status in the run records |
| Re-examination application | Fields complete, responsible person clear, version and date consistent | Check re-examination items, original physical examination conclusion, application date, and approval signature; reference the selection result variable in subsequent nodes and run a test once |
| Notice of restricted majors | Fields complete, responsible person clear, version and date consistent | Check restricted major names, basis clauses, notification date, and receipt signature; trigger once and view node status in the run records |
| Handover record | Responsible person clear, version and date consistent | Check both parties in the handover, handover time, material list, and receipt status; verify options and branch connections one by one in the node |
Three common errors
- Phenomenon: The name, quantity, and date of the same record do not match between the physical examination form and the notice of restricted majors. Cause: Field sources were not unified during material drafting, and versions were not synchronized.
- Phenomenon: The re-examination application and the physical examination form have inconsistent versions, and signatures or receipts are missing. Cause: The handover step did not continue execution according to the branch, and the responsible person did not confirm.
- Phenomenon: After selecting an option, the default branch is still followed, and the process stops after the interaction is completed. Cause: 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
This feature acceptance: test run each option one by one, and check the branch direction and interaction state in the run records; verify options and branch connections one by one in the node, reference the selection result variable in subsequent nodes and run a test once, and confirm that variables, nodeId, and the branch direction are consistent.
Business test: draft one according to the template and complete one handover, and see whether missing items are blocked.
- Verify options and branch connections one by one in the node, trigger once, and view node status in the run records.
- Reference the selection result variable in subsequent nodes and run a test once, and confirm that the branch direction is consistent with the interaction state records.