What this category's data looks like
This page addresses the scenario of exam question setting and marking in primary and secondary schools. The materials include three types: the question-setting two-way specification table, the exam paper, and the marking rubric. The specification table records knowledge points, question types, scores, difficulty, and the question setter's signature; the exam paper carries the question text, question numbers, scores, exam date, and review signature; the marking rubric records scoring points, score bands, reference answers, and review signature. The materials come from the question-setting group, the question-review group, and the marking group, and are updated on a rolling basis by exam batch. The fields are mainly names, quantities, dates, signatures, and receipts. When entering workflow orchestration, the specification table serves as the branching basis for question-setting tasks, the exam paper serves as the verification object for review and handover, and the marking rubric serves as the branching basis for marking tasks. Together, the three support a handover-ready deployment state and operation records.
Configuration and implementation checks
This step is executed by workflow nodes (user selection and branching), outputting branch directions and interaction state records. "Handover-ready deployment state and operation records" are completed by subsequent nodes continuing execution according to the branches. When triggered, the conversation enters an interaction state and records the workflow state; after the selection is completed, execution continues along the branch corresponding to the selected option.
| Object | Check | Verification action |
|---|---|---|
| Question-setting two-way specification table | Names, quantities, dates, and signatures are consistent across the three materials | Check item by item the question numbers, scores, and exam date in the specification table and the exam paper, and check whether the question setter's and reviewer's signatures are complete |
| Exam paper | The version is synchronized with the marking rubric, and no receipt is missing | Compare the question numbers, scores, and reference answer names in the exam paper and the marking rubric, and check whether the version number corresponds to the receipt record |
| Marking rubric | Scoring points, score bands, and review signature are traceable | Check the number of scoring points against the number of questions in the exam paper, check the review signature and marking receipt, and confirm that the date matches the exam batch |
| User selection node | Options correspond one by one to branches, and the interaction state is recorded | In the node, check the options and branch connections one by one; after triggering once, view the node state and selection result variable in the run record |
Three common errors
- Symptom: The names, quantities, and dates of the same record do not match between the specification table and the exam paper. Cause: The two materials were entered by different personnel, and the fields were not compared item by item according to the same batch.
- Symptom: The versions of the exam paper and the marking rubric are not synchronized, and deviations appear in question numbers and scores. Cause: After revision, only one material was updated, while the other continued to use the old version and had no version marker.
- Symptom: The handover form lacks a signature or receipt, making it impossible to confirm the responsible person and time. Cause: Signatures and receipts were not included in the material fields, and during handover only the content was checked, not the credentials.
How to verify the setup
This function's acceptance: try running each option one by one, and check the branch direction and interaction state in the run record; reference variables in subsequent nodes, and check whether the node state corresponding to nodeId is consistent with the selection result variable.
Business test: check item by item once according to the handover form to see which record is missing; compare the names, quantities, dates, and signatures of the specification table, exam paper, and marking rubric, and confirm that the version, connection, and task record are consistent.
- In the user selection node, check the options and branch connections one by one; after triggering once, view the node state and branch direction in the run record.
- Reference the selection result variable in subsequent nodes and run a trial once; compare the names, quantities, dates, and signatures of the specification table, exam paper, and marking rubric, and fill in any missing receipts.