What this category's data looks like
The data in this category looks like this: College admissions physical examination organization involves three types of materials: physical examination forms, re-examination applications, and restricted major notifications. The sources are the school hospital and the admissions office, and the update rhythm advances by batch. Physical examination forms record basic items and the chief examiner's conclusion; re-examination applications carry review requests and approval traces; restricted major notifications reflect restricted major conclusions and receipts. After the three types of materials enter the workflow, each has a different role: the physical examination form is the starting point for progress records, the re-examination application is the basis for branch triggering, and the restricted major notification is the endpoint for statistical verification. Field characteristics are concentrated in name, number, date, conclusion, and signature, and the same record must be aligned item by item across the three materials. Before a weekly or monthly report, one week's records need to be summarized and verified, the statistical criteria written in the header, and exceptions marked separately.
Configuration and implementation checks
Configuration and implementation checks: This step is executed by workflow nodes (user selection and branches), outputting branch direction and interaction status records. The "progress table and statistical criteria description" is continued and completed by subsequent nodes according to the branch.
| Object | Check | Verification action |
|---|---|---|
| Physical examination form | Whether name, number, physical examination date, chief examiner's conclusion, and signature are complete, and whether they are aligned item by item with the re-examination application and restricted major notification | Extract one week's physical examination forms, sort by number and date, and verify node status and branch direction in the run records |
| Re-examination application | Whether the re-examination items, application date, approval signature, and receipt correspond to the conclusion of the physical examination form | Check options and branch connections one by one in the node, reference variables and run a trial to see whether the selection result is passed in |
| Restricted major notification | Whether the restricted major name, notification date, receipt signature are consistent with the physical examination conclusion and re-examination result | Reference nodeId in subsequent nodes to locate records, and verify whether the number of notifications equals the total of physical examination forms and re-examination applications |
| Statistical criteria description | Whether the header states the number of records, statistical count, exception items, and date range | Use one week's records to verify the total, check whether the criteria and exceptions are clearly written, and record the number of array entries separately |
Three common errors
- Phenomenon: The name or number of the same student does not match between the physical examination form and the restricted major notification. Cause: The two materials were entered separately, and cross-checking was not performed using the same record key.
- Phenomenon: The re-examination application has been updated, but the physical examination form is still the old version. Cause: The versions were not synchronized, and the node branch continued executing according to the old status.
- Phenomenon: The restricted major notification lacks a receipt signature, but it is included in the total during statistics. Cause: The receipt was not collected, and the criteria did not list items missing signatures as exceptions.
How to verify the setup
How to verify the setup: Acceptance for this function: run trials option by option, check the branch direction and interaction status in the run records, and confirm that variables has been passed to subsequent nodes and that nodeId can locate the corresponding record.
Business test: Use one week's records to verify the total, check whether the criteria and exceptions are clearly written, and whether the number of records matches the statistical count.
- Check 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 subsequent nodes and run a trial once, verifying the branch direction and interaction status records