What this category's data looks like
This page is for primary and secondary school exam question setting and grading scenarios. The materials include three types: the question-setting two-way specification table, the exam paper, and the grading rubric. The question-setting two-way specification table carries the test points, question types, score values, cognitive levels, and the question setter's signature; the exam paper carries the question numbers, question stems, answers, and exam date; the grading rubric carries the scoring points, scoring basis, grader's signature, and receipt. When these three types of materials enter the HTTP interface and external system functions, each has a different role: the two-way specification table serves as the question-setting basis and version source, the exam paper serves as the content subject and referenced object, and the grading rubric serves as the grading execution standard and receipt credential. The source is the final draft from the teaching and research department and the school exam administration archive. The update rhythm changes with exam arrangements and revision notices. The field characteristics are concentrated in four categories: name, quantity, date, and signature.
Configuration and implementation checks
This step is executed by the HTTP node in the workflow, outputting the response body, status code, and returned fields. The version ledger and change records are completed by subsequent nodes parsing the response, or by the external system handling them according to the agreement. The request URL, path parameters, request headers, and request body can all use variable placeholders. The variables come from global variables, system variables, or the output of preceding nodes.
| Object | Check | Verification action |
|---|---|---|
| Question-setting two-way specification table | The test point names, question type quantities, total score values, and question-setting date must be aligned item by item with the exam paper, and the signature column must have the question setter's signature | Reference the specification table fields in the request body, use one sample request to compare the returned test point names and total score values, and check the request header names and value sources |
| Exam paper | The question numbers, question stems, answers, and exam date must correspond to the scoring points in the grading rubric, and the version number must be the current unique one | View the complete rendered URL in the request preview, check whether the variables placeholders are parsed into actual values, and compare whether the exam paper version number is synchronized with the reference location |
| Grading rubric | The scoring points, scoring basis, grader's signature, and receipt must be complete, and the date must be consistent with the exam paper's exam date | Check the source of each placeholder in the variables panel, check that the Authorization authentication information is passed in according to the external system's requirements, and compare the rubric scoring points with the exam paper question numbers |
| Version ledger and change records | The current version is unique, old versions are traceable, references are synchronized, and change records must include the change date and changer | Use one sample request to compare the returned fields, and check whether the version number in responseData is synchronized with the reference location |
Three common errors
- Symptom: The name or quantity of the same test point does not match between the two-way specification table and the exam paper. Cause: The two materials are maintained separately, and the same field is not referenced in the request body.
- Symptom: The exam paper has been revised, but the grading rubric still references the old question numbers. Cause: The version is not synchronized, and the reference location is not updated with the change records.
- Symptom: The grading rubric lacks the grader's signature or receipt. Cause: The external system does not return the signature status according to the agreement, and the request return fields are missing.
How to verify the setup
This function's acceptance: preview the rendered request, check the status code and returned fields, then compare the result against one sample to confirm that the version number in responseData is consistent with the reference location.
Business test: change one piece of content and see whether the version number and reference are updated synchronously.
- In the request preview, check whether the complete rendered URL and path parameter placeholders are parsed into actual values.
- In the variables panel, check the source of each placeholder and confirm whether it comes from a global variable, system variable, or the output of a preceding node.