What this category's data looks like
During the admissions season, university admissions physical examination organizations centrally process three types of materials: physical examination forms, re-examination applications, and notices of restricted majors. Physical examination forms come from examination stations and school hospitals and are updated by batch; their fields include name, subject category, conclusion, date, and chief examiner signature. Re-examination applications are submitted by candidates or parents; their fields include application reason, original conclusion, re-examination date, and acceptance receipt. Notices of restricted majors are issued by the admissions office; their fields include the name of the restricted major, the clause on which it is based, the notification date, and the candidate's acknowledgment. When these three types of materials enter the authorized access and external services function, the physical examination form serves as the primary record for determining the visible scope, the re-examination application serves as the interaction credential that triggers branches, and the notice of restricted majors serves as the display content for the external entry point. Materials are updated by admissions batch and re-examination round, and signatures and receipts are the key fields for version synchronization.
Configuration and implementation checks
This step is executed by workflow nodes (user selection and branching), outputting branch directions and interaction status records. "External entry points and authorization scope" 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 status; after the user completes the selection, execution continues along the branch corresponding to the selected option.
| Object | Check | Verification action |
|---|---|---|
| Physical examination form | Name, subject category, conclusion, date, and chief examiner signature are consistent across the two materials, and versions are synchronized | Compare the names, quantities, and dates in the physical examination form and the re-examination application, and check whether signatures are complete |
| Re-examination application | The application reason, original conclusion, re-examination date, and acceptance receipt fields are complete and correspond to the physical examination form | Check the options and branch connections one by one in the node, and check whether the receipt is missing |
| Notice of restricted majors | The name of the restricted major, the clause on which it is based, the notification date, and the candidate's acknowledgment match the physical examination conclusion | Reference variables and nodeId for a trial run, and check whether the notice version is synchronized |
| Authorized access entry point | The visitor's identity matches the visible scope, and unauthorized access is not visible | Trigger once with a restricted identity, and check the node status in the run record |
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 entered separately and are not compared against the same primary record.
- Symptom: The version of the notice of restricted majors is not synchronized, and old clauses are still displayed externally. Cause: After the notice is updated, the branch is not re-run, and the interaction status is not refreshed.
- Symptom: The re-examination application lacks a signature or receipt, but the external entry point still allows passage. Cause: The visible scope determination does not list signatures and receipts as prerequisites.
How to verify the setup
Acceptance of this function: run trials option by option, check the branch directions and interaction status in the run record, and confirm that the selection result variable has been passed to subsequent nodes.
Business test: access once with a restricted identity and see whether the visible scope matches the setting.
- Check the options and branch connections one by one in the node, and confirm that each option corresponds to one branch.
- Reference
variablesandnodeIdin subsequent nodes for one trial run, and check whether the process continues after the interaction is completed.