What this category's data looks like
In authorized access and external services, the core materials of primary and secondary school admissions organizations include three types: admissions plans, application material checklists, and admission lists. Admissions plans come from the education authorities or the school admissions leadership group and are updated by academic year or batch. Their fields include admissions scope, application conditions, time nodes, signature fields, and dates. Application material checklists come from the admissions execution department and are updated with application batches and policy adjustments. Their fields include material name, number of copies, submission method, and receipt requirements. Admission lists come from the review group and are publicly announced and archived by batch. Their fields include student name, ID number, admission status, announcement date, and signature. When these three types of materials enter workflow orchestration, the admissions plans and application material checklists are used to generate external entry points and authorization scopes, while the admission lists are used to limit visible fields and open targets. Each plays a different role.
Configuration and implementation checks
This step is executed by workflow nodes (user selection and branching), outputting branch directions and interaction status records. The "external entry points and authorization scopes" are then completed by subsequent nodes continuing execution according to the branches.
| Object | Check | Verification action |
|---|---|---|
| Admissions plan | Whether the admissions scope, application conditions, time nodes, signature, and date are consistent with the application material checklist | Check the dates, names, and quantities in the plan and checklist; verify options and branch connections one by one in the node, and run a trial once to view the node status in the run record |
| Application material checklist | Whether the material name, number of copies, submission method, and receipt requirements correspond to the public announcement fields of the admission list | Reference the selection result variable variables in subsequent nodes and run a trial once, check the branch direction corresponding to nodeId, and confirm that receipts and signatures are not missing |
| Admission list | Whether student name, ID number, admission status, and announcement date are synchronized with the plan batch | Trigger a user selection node once, view the status of nodeId in the run record, and confirm that the names, quantities, and dates of the same record match in both materials |
| External entry points and authorization scopes | Whether visitor identity matches the visible scope, and whether unauthorized access is invisible | Access once with a restricted identity and check whether the visible scope matches the settings; verify options and branch connections one by one in the node |
Three common errors
- Symptom: The names, quantities, and dates of the same record do not match between the admissions plan and the application material checklist. Cause: The two types of materials are maintained by different nodes separately, versions are not synchronized, and unified signature and receipt verification is lacking.
- Symptom: The admission list version is not synchronized, and the announcement date is inconsistent with the plan batch. Cause: After the list is updated, the user selection node is not re-triggered, the branch direction still uses the old record, and the interaction status is not refreshed.
- Symptom: The application material checklist lacks signatures or receipts, but the external entry point is still open. Cause: The node only outputs branch directions and interaction status records, and subsequent nodes do not continue execution according to the branches to verify signatures and receipts.
How to verify the setup
Feature acceptance: Run trials for each option one by one, and check the branch directions and interaction status in the run record; verify options and branch connections one by one in the node, confirm that nodeId corresponds to the correct branch, and that the selection result variable variables has been passed to subsequent nodes.
Business testing: Access once with a restricted identity and see whether the visible scope matches the settings; unauthorized access is invisible, and the external entry points and authorization scopes are consistent with the fields, dates, and signatures of the admissions plan, application material checklist, and admission list.
- In the user selection node, verify options and branch connections one by one, trigger it once, and then view the node status in the run record to confirm that the process continues downward after the interaction is completed.
- Reference the selection result variable
variablesin subsequent nodes and run a trial once, check the branch direction corresponding tonodeId, and confirm that the names, quantities, dates, and signature receipts of the same record are consistent in the admissions plan, application material checklist, and admission list.