What this category's data looks like
This category involves three types of materials: physical examination forms, re-examination applications, and restricted-major notifications. Physical examination form fields include name, ID number, past medical history, examination conclusion, date, and physician signature; re-examination applications include the original examination conclusion, re-examination items, application date, and receipt; restricted-major notifications include the restricted major name, basis clause, notification date, and candidate signature. The material sources are the campus hospital, admissions office, and departments. The update cadence is concentrated in the physical examination season and re-examination window, and revisions are often triggered by conclusion adjustments or policy changes. When these three types of materials enter workflow orchestration, the physical examination form serves as the main record, while the re-examination application and restricted-major notification serve as related materials, each taking on the roles of field verification, date comparison, and signature receipt checks, and the version ledger is generated accordingly.
Configuration and implementation checks
This step is executed by workflow nodes (user selection and branching), outputting branch directions and interaction state records. The "version ledger and change records" are completed by subsequent nodes continuing execution according to the branch. When the user selection node is triggered, the conversation enters an interactive state and records the workflow state; after the selection is completed, execution continues along the branch corresponding to the selected option.
| Object | Check | Verification action |
|---|---|---|
| Physical examination form | Whether fields, dates, and signatures are complete, and whether the names, quantities, and dates are consistent with the re-examination application and restricted-major notification | Check the options and branch connections one by one in the node, trigger once to view the node status in the run records, and reference the selection result variable in a subsequent node and do a trial run |
| Re-examination application | Whether the re-examination items, application date, and receipt correspond to the physical examination form conclusion, and whether signatures are missing | Check the correspondence between options and branches, check whether the interaction state is recorded, and confirm that the selection result variable has been passed to subsequent nodes |
| Restricted-major notification | Whether the restricted major name, basis clause, notification date, and candidate signature are consistent with the physical examination form and re-examination application | Compare the names, quantities, and dates of the three materials item by item, view the branch direction and interaction state records, and do a trial run to verify reference synchronization |
| Version ledger and change records | Whether the current version is unique, whether old versions are traceable, and whether references are updated synchronously | After changing one piece of content, check whether the version number and references are updated synchronously, and verify the branch direction and interaction state records |
Three common errors
- Symptom: The name, quantity, and date of the same record do not match between the physical examination form and the re-examination application. Cause: The two materials are maintained separately, without field comparison and reference synchronization.
- Symptom: The restricted-major notification has been revised, but the physical examination form still references the old clause. Cause: The version was not synchronized, the ledger did not record the change, and the reference was not updated with the version.
- Symptom: The re-examination application lacks the candidate signature or receipt, but the physical examination form conclusion has already been circulated. Cause: Signatures and receipts were not included in the check, and the process continued after the interaction was completed.
How to verify the setup
This feature acceptance: run trials option by option, check the branch direction and interaction state in the run records, confirm that the selection result variable has been passed to subsequent nodes, and check whether the variables and nodeId references are correct.
Business test: change one piece of content and see whether the version number and references are updated synchronously.
- Check the options and branch connections one by one in the node, and trigger once to view the node status in the run records.
- Reference the selection result variable in a subsequent node and do a trial run to confirm that
variablesandnodeIdpoint correctly.