What this category's data looks like
In material verification and discrepancy localization, university admissions physical examination organizations mainly handle three types of materials: physical examination forms, re-examination applications, and restricted major notifications. Sources are the school hospital, admissions office, and candidate submissions. The update cadence advances with examination batches and re-examination rounds. Field characteristics center on name, candidate number, examination item name, quantity, date, signature, and receipt. The physical examination form is the primary record carrier, the re-examination application is the change trigger voucher, and the restricted major notification is the conclusion output. When the three types of materials enter the workflow, each assumes the roles of comparison baseline, discrepancy source, and receipt confirmation. They must be compared on the same object for consistency in name, quantity, and date, and common inconsistencies such as unsynchronized versions, missing signatures, or missing receipts must be identified.
Configuration and implementation checks
This step is executed by workflow nodes (user selection and branching), outputting branch direction and interaction state records. The "discrepancy list" is completed by subsequent nodes continuing execution according to the branch. 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 | Whether the name, quantity, and date of the same record are consistent between the physical examination form and the ledger | In the user selection node, check the options and branch connections one by one, reference variables and nodeId, and after a trial run, view the node status in the run records |
| Re-examination application | Whether the re-examination application matches the physical examination form in date, item name, signature, and receipt | Trigger an interaction node once, check whether the re-examination application fields are correctly passed along the branch direction, and confirm that the selection result variable has been passed to subsequent nodes |
| Restricted major notification | Whether the restricted major notification is consistent with the physical examination form and re-examination application in conclusion date and signature | Check whether the notification receipt is complete, and check whether the branch points to the subsequent node of the discrepancy list when the version is not synchronized |
| Discrepancy list | Whether the discrepancy list covers field-level inconsistencies in name, quantity, date, signature, and receipt | Reference the selection result variable in the subsequent node and run a trial once to confirm that the discrepancy list is completed by the subsequent node continuing execution according to the branch |
Three common errors
- Symptom: After selecting an option, the default branch is still taken. Cause: The options and branch connections were not checked one by one, and after the interaction state was recorded, the branch judgment was not executed according to the selection result.
- Symptom: The name, quantity, and date of the same record do not match between the two materials. Cause: The versions are not synchronized, and the physical examination form and re-examination application were not compared by fields from the same batch.
- Symptom: The restricted major notification lacks a signature or receipt. Cause: After the interaction is completed, the process stops, and subsequent nodes do not continue execution according to the branch and write back the confirmation status.
How to verify the setup
Feature acceptance: Run trials for each option one by one, check the branch direction and interaction state in the run records, and confirm that variables, nodeId, and the selection result variable are correctly referenced in subsequent nodes.
Business testing: Use one real record to find fields inconsistent with the ledger, focusing on checking name, quantity, date, signature, and receipt, and confirm that the discrepancy list is completed by the subsequent node continuing execution according to the branch.
- In the user selection node, check the options and branch connections one by one, trigger an interaction once, and view the node status in the run records.
- Reference the selection result variable in the subsequent node and run a trial once to confirm that the discrepancy list is completed by the subsequent node continuing execution according to the branch.