What this category's data looks like
The data for this category looks like this: University admissions physical examination organization involves three types of materials: physical examination forms, re-examination applications, and restricted major notifications. The physical examination form contains past medical history, internal medicine, surgery, ophthalmology, and otolaryngology examination fields, the signature of the chief examining physician, and the physical examination date; the re-examination application contains the reason for application, the original physical examination conclusion, the re-examination items, the signatures of the candidate and parent, and the acceptance receipt; the restricted major notification contains the major name, restricted clauses, notification date, candidate acknowledgment, and admissions office seal. The material sources are the school hospital, admissions office, and departments, and the update rhythm is batch entry during the concentrated physical examination period, with re-examination results and notification receipts supplemented before admission. When entering workflow orchestration, the physical examination form serves as the main record anchor, and the re-examination application and restricted major notification serve as related materials, each carrying name, quantity, date, and signature fields, so that basis entries can refer back to the original text.
Configuration and implementation checks
Configuration and implementation checks: This step is executed by workflow nodes (user selection and branching), outputting branch direction and interaction status records. "Basis entries that can refer back to the original text" are completed by subsequent nodes continuing execution according to the branch. When this node is triggered, the conversation 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 |
|---|---|---|
| Physical examination form | Fields include examination columns, chief examiner signature, and physical examination date, and must be consistent with the original conclusion date in the re-examination application | Check the options and branch connections one by one in the node, use variables to reference the selection result and do a trial run, and view the nodeId status in the run record |
| Re-examination application | The application reason, re-examination items, and acceptance receipt signature must be complete, and the version must be current | Trigger an interaction once, check the node status in the run record, and confirm that the selection result variable has been passed to subsequent nodes |
| Restricted major notification | The major name, restricted clauses, and notification date must match the physical examination conclusion; if acknowledgment is missing, return it | Reference the selection result variable in subsequent nodes and do a trial run to check whether the notification entry can refer back to the original source |
| Basis entry | The entry comes from the institution’s materials, the version is current, and it can match the original text | Compare material name, quantity, date, and signature one by one, and record the tokens and array count of the referenced text |
Three common errors
- Phenomenon: 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 places were entered separately, and no cross-material field comparison was performed.
- Phenomenon: The version of the physical examination conclusion referenced by the restricted major notification has not been synchronized. Cause: The notification was generated based on an old version of the conclusion and was not written back after supplementation.
- Phenomenon: The re-examination application lacks the acceptance receipt signature, and the notification lacks the candidate acknowledgment. Cause: After the interaction was completed, the signature fields and receipt fields were not checked.
How to verify the setup
Acceptance of this function: Run trial executions option by option, check the branch direction and interaction status in the run record, confirm that the nodeId status is consistent with the option, and that the selection result variable has been passed to subsequent nodes.
Business test: Ask a cross-material basis question and see whether the answer provides a source that can be referred back to.
- Check the options and branch connections one by one in the node, and after triggering an interaction once, view the node status in the run record.
- Reference
variablesin subsequent nodes and do a trial run once to confirm that the branch direction and interaction status records are correct.