What this category's data looks like
In the regular higher education institution admissions enrollment filing scenario, before entering the function, three types of materials need to be organized: the admissions plan (including institution major groups, planned numbers, batches, and selected subject requirements), filing rules (including transfer ratio, tie-breaking sorting, volunteer grade difference, and withdrawal conditions), and the admission roster (including candidate number, name, score, major, admission status, signature, and receipt). The three types of materials are usually updated by year or batch, and field names, quantities, dates, and signatures are prone to inconsistency across different sources. In this function, the admissions plan is used to determine the eligible filing scope and remaining plan balance, the filing rules are used to determine filing order and tie-breaking handling, and the admission roster is used to refer back to admission results and signature receipts. After the materials enter the workflow, the user first selects a node to confirm the basis source and version, and then proceeds to subsequent nodes to compare the original text item by item.
Configuration and implementation checks
This step is executed by workflow nodes (user selection and branching), outputting branch direction and interaction status records. "Basis items that can be traced back to the original text" are completed by subsequent nodes continuing execution according to the branch.
| Object | Check | Verification action |
|---|---|---|
| Admissions plan | Check whether the institution major group name, planned number, batch, and selected subject requirements are consistent with the transfer ratio and tie-breaking sorting in the filing rules; whether the version is current | Compare the fields, dates, and signatures in the admissions plan and filing rules item by item, record discrepancies, and refer back to the original text location |
| Filing rules | Check whether the transfer ratio, tie-breaking sorting, volunteer grade difference, and withdrawal conditions correspond to the filing results and admission status in the admission roster; whether the versions are synchronized | At the user selection node, check the options and branch connections one by one, and use variables and nodeId to record the branch direction |
| Admission roster | Check whether the candidate number, name, score, major, admission status, signature, and receipt are consistent with the records in the admissions plan and filing rules; whether the dates match | Trigger the user selection node once, and check in the run record whether the interaction status and selection result variables are passed to subsequent nodes |
| Version and signature | Check whether the name, quantity, and date of the same record are consistent in the two materials; whether signatures or receipts are complete; whether the versions are not synchronized | Refer back to the original text item by item, mark items with missing signatures, receipts, or unsynchronized versions, and leave them for subsequent nodes to continue execution |
Three common errors
- Phenomenon: The name or candidate number of the same candidate does not match in the two materials. Cause: Fields were not unified during entry, or the versions of the admissions plan and admission roster were not synchronized.
- Phenomenon: The planned number and the number of filing results are inconsistent. Cause: After the admissions plan was updated, it was not synchronized to the filing rules, or the batch adjustment was not receipted.
- Phenomenon: The admission roster lacks signatures or receipts. Cause: The process was not completed, or after the user selection node the branch stopped and subsequent nodes did not continue execution.
How to verify the setup
This function acceptance: run trials option by option, and check the branch direction and interaction status in the run record; confirm that each option corresponds to one branch, the selection result variable has been passed to subsequent nodes, and variables and nodeId are used to record.
Business test: ask a cross-material basis question, see whether the answer gives a traceable source, and check whether the fields, dates, and signatures of the admissions plan, filing rules, and admission roster match.
- In the user selection node, check the options and branch connections one by one, and after triggering once, check the interaction status and branch direction in the run record.
- Reference the selection result variable in subsequent nodes and run a trial once to confirm that the basis items that can be traced back to the original text are completed by subsequent nodes continuing execution according to the branch.