What this category's data looks like
In the scenario of general higher education institution admissions enrollment and filing, the materials include three categories: enrollment plans, filing rules, and admission rosters. Enrollment plans come from provincial admissions and examination institutions and university admissions offices, and are updated by batch, subject category, and major; filing rules come from provincial admissions office documents and are adjusted with batches; admission rosters are generated by university admissions offices and contain candidate name, candidate number, major, admission date, and signature. When the three categories of materials enter Q&A intake and missing-item follow-up, their roles differ: enrollment plans provide planned numbers and major codes, filing rules provide filing ratios and sorting bases, and admission rosters provide actual admission results and signed receipts. Field characteristics are concentrated in four items: name, quantity, date, and signature. It is common for the name, quantity, or date of the same record to fail to match across two materials, for versions not to be synchronized, or for signatures or receipts to be missing. Intake records need to correspond question items with material sources, and missing-item follow-up asks item by item according to fields.
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 "intake record and completed question items" 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 | Correspond item by item with the planned number, major code, and batch date in the filing rules; if the names are inconsistent, it is a missing item | Check the field names one by one in the node configuration, confirm that the enrollment plan fields correspond one-to-one with the filing rule fields, and test-run the references |
| Filing rules | The rule version is consistent with the version used by the admission roster, and signatures and receipts are complete | Check the version date of the rule document and the version referenced by the roster, and check whether the signature column and receipt field are marked as required |
| Admission roster | The candidate name, candidate number, major, and admission date in the roster are consistent with the enrollment plan and filing rule records | Reference the roster fields in subsequent nodes and test-run to confirm that the corresponding field values can be obtained after submission |
| Form fields | Field names correspond one-to-one with material fields, and required markers cover key material fields | Check field names and required settings one by one in the node configuration, and use formInputResult and selectResult to verify field passing |
Three common errors
- Symptom: The name or quantity of the same candidate fails to match across two materials. Cause: The fields of the enrollment plan and admission roster do not correspond item by item, and missing items are not identified and followed up.
- Symptom: The filing rule version is inconsistent with the version referenced by the admission roster. Cause: The versions are not synchronized, the form does not collect the version date field, and subsequent nodes cannot obtain the value.
- Symptom: The roster still enters intake when signatures or receipts are missing. Cause: Key material fields are not marked as required, submission is possible even when required items are empty, and the conversation stops in the interaction state.
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 formInputResult and selectResult field passing is correct, and that submission is not possible when required items are empty.
Business test: submit a question that lacks key information and see whether it follows up first before answering.
- Check field names and required settings one by one in the node configuration, and confirm that they correspond one-to-one with the fields of the enrollment plan, filing rules, and admission roster.
- Reference the
formInputResultandselectResultfields in subsequent nodes and test-run to confirm that the corresponding field values can be obtained after submission.