What this category's data looks like
General higher education institution admissions enrollment and filing materials mainly consist of enrollment plans, filing rules, and admission rosters. Their sources are provincial admissions examination institutions and university admissions offices. The update cadence advances with batches. Fields include candidate number, institution-major group, planned number, filing cutoff line, admission status, signature, and receipt date. When enrollment plans enter authorized access and external services, they serve as the baseline for visibility scope and authorization granularity; filing rules determine branch directions and the conditions for opening external entry points; admission rosters are the restricted data ultimately presented externally and must be aligned item by item with plans and rules. After materials enter workflow orchestration, their respective roles are: plans define scope, rules define branches, and rosters define content. Together, the three support restricted opening to parents or higher authorities.
Configuration and implementation checks
This stage is executed by workflow nodes (user selection and branching), outputting branch directions and interaction status records. "External entry points and authorization scope" are completed by subsequent nodes continuing execution according to the branch. When 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 |
|---|---|---|
| Enrollment plan | Whether the plan name, quantity, date, and signature are consistent with the filing rules | Check the options and branch connections one by one in the node, and run a trial with a restricted identity to view the node status in the run records |
| Filing rules | Whether the rule version and effective date are synchronized with the admission roster | Reference the selection result variable in a subsequent node and run a trial once, checking the branch direction and interaction status records |
| Admission roster | Whether the name, quantity, and date in the roster match the plan and rules, and whether signatures and receipts are complete | Trigger a user selection node once, view the node status in the run records, and check the options and branch connections |
Three common errors
- Symptom: The same candidate's name, quantity, and date do not match across two materials. Cause: The enrollment plan and admission roster were not synchronized to the same version, and field sources are out of sync.
- Symptom: The filing rule version was not synchronized, and the external entry point is still open according to the old rules. Cause: After the rules were updated, the workflow node was not re-triggered, and the branch direction continued to use the old records.
- Symptom: The admission roster lacks a signature or receipt, but the external service is still accessible. Cause: The authorization scope was not bound to the signature and receipt status, and the interaction status records were not included in verification.
How to verify the setup
This feature acceptance: run trials option by option, check the branch direction and interaction status in the run records, and check whether variables, nodeId, and the selection result variable have been passed to subsequent nodes.
Business test: access once with a restricted identity, see whether the visibility scope matches the setting, and confirm that unauthorized content is not visible.
- Check the options and branch connections one by one in the node, and confirm that each option corresponds to one branch.
- Reference
variablesin a subsequent node and run a trial once, checking the interaction status record corresponding tonodeId.