What this category's data looks like
The materials for general higher education institution admissions enrollment and filing mainly come from the enrollment plans and filing rules issued by provincial admissions and examination institutions, as well as the admission rosters submitted by higher education institutions. Enrollment plans are published by batch and subject category, filing rules are updated with the policies of the current year, and admission rosters are returned after each round of filing. When these materials enter the form input node, each has a different role: the enrollment plan provides institution-major groups and planned numbers, the filing rules provide the filing ratio and same-score handling, and the admission roster provides candidate names, scores, majors, and signature fields. Field characteristics are concentrated in names, quantities, dates, signatures, and receipts. The same record often has mismatched names, quantities, and dates across two materials, versions are not synchronized, and signatures or receipts are missing.
Configuration and implementation checks
This step is executed by the form input node (interaction node) in the workflow, and outputs the field values filled in by the user (passed to subsequent nodes after submission). The externally available entry point and authorization scope are then completed by subsequent nodes or manually. After the form input node is triggered, the conversation enters an interaction state and records the workflow state. After the user fills in the required items and submits, the form information is passed to subsequent nodes for use.
| Object | Check | Verification action |
|---|---|---|
| Enrollment plan | Check whether the institution-major group names, planned numbers, publication dates, and signature fields in the enrollment plan are consistent item by item with the filing rules and admission roster | Check the field names one by one in the node configuration, confirm that the enrollment plan fields correspond one-to-one with the material fields to be collected; reference the fields with formInputResult and run a trial |
| Filing rules | Check whether the filing ratio, same-score handling, effective date, and version number in the filing rules are synchronized with the corresponding records in the enrollment plan and admission roster | Check the required settings one by one, confirm that key material fields are marked as required; use userSelect to select the version and run a trial, and see the field values obtained by subsequent nodes |
| Admission roster | Check whether the candidate names, scores, majors, signatures, and receipts in the admission roster match the names, quantities, and dates in the enrollment plan and filing rules | Reference this field in subsequent nodes and run a trial, confirm the field transfer after submission, and that subsequent nodes can obtain the corresponding field values |
Three common errors
- Symptom: The same candidate's major name, planned number, and date do not match between the enrollment plan and the admission roster. Cause: The two materials are entered separately by different steps, without item-by-item field comparison and version synchronization.
- Symptom: The filing rule version is not synchronized, and the old ratio is still referenced. Cause: After the rules were updated, they were not synchronously replaced in the form fields and subsequent nodes, and the field values still point to the old record.
- Symptom: The admission roster is still submitted when the signature or receipt is missing. Cause: Key material fields are not marked as required, so submission is possible even when required items are empty, and subsequent nodes cannot obtain complete field values.
How to verify the setup
Acceptance of this feature: fill it out once and submit, check the field values obtained by subsequent nodes, confirm that the form input node outputs the field values filled in by the user and passes them to subsequent nodes; check whether the formInputResult and selectResult references obtain the corresponding values.
Business test: access once with a restricted identity, see whether the visible scope matches the setting, and that unauthorized access is not visible; when opening it to parents or superiors, check the authorization scope and entry point.
- Check the field names and required settings one by one in the node configuration, confirm that the fields of the enrollment plan, filing rules, and admission roster correspond one-to-one, and that key material fields are marked as required.
- Reference the
formInputResultandselectResultfields in subsequent nodes and run a trial, confirm that after submission subsequent nodes can obtain the corresponding field values, and that the conversation does not remain in the interaction state.