What this category's data looks like
This page addresses the scenario of exam question setting and grading in primary and secondary schools; the materials come from the question-setting two-way specification table, exam papers, scoring rubrics, and progress record sheets. The two-way specification table gives the assessed content and question-type distribution, the exam paper carries the question statements and score values, the scoring rubric gives the scoring points and deduction explanations, and the progress record sheet registers by date the completion status of each subject and each stage. When the materials enter the HTTP interface and external systems, the two-way specification table and scoring rubric serve as sources of request body fields, the exam paper information serves as a path parameter or request body identifier, and the progress record sheet serves as the base table for verifying the statistical criteria. The update rhythm advances weekly, and question setting, paper review, grading, and re-checking each have their own milestones. Field characteristics center on names, quantities, dates, signatures, and receipts, and the same record must remain consistent across multiple materials.
Configuration and implementation checks
This step is executed by the HTTP node in the workflow, which outputs the response body, status code, and returned fields. The "progress sheet and statistical criteria description" is parsed from the response by subsequent nodes, or handled by the external system according to the agreement to complete the next step. The HTTP module sends a request to the target address; path parameters, request body, and request headers can all use variable placeholders, and the variables come from global variables, system variables, or the output of preceding nodes.
| Object | Check | Verification action |
|---|---|---|
| Question-setting two-way specification table | Names, quantities, and dates must be consistent with the exam paper and scoring rubric, and the signature column must be complete | Compare the number of specification table entries with the number of exam paper questions in the request body fields, and verify the dates and signatures |
| Exam paper | Question numbers, score values, dates, and receipts must match the scoring rubric and progress record sheet | View the fully rendered address and request body in the request preview, and compare against the sample response |
| Scoring rubric | Scoring point names, quantities, and version dates must be synchronized with the exam paper and progress record sheet | Verify the request header names and value sources, and confirm the version dates and signature receipts |
| Progress record sheet | The number of records must match the statistical counts, the criteria must be written in the header, and exceptions must be marked separately | Use one week of records to verify the totals, and check whether the criteria and exceptions are clearly written |
Three common errors
- Symptom: the names and quantities of the same record do not match between the specification table and the exam paper. Cause: the two materials are maintained separately, the same identifier is not used for alignment, and the sources of request body fields are not unified.
- Symptom: the scoring rubric version is not synchronized, and the grading criteria are inconsistent with the exam paper date. Cause: after the version update, it was not written back to the progress record sheet, and the external system still processes according to the old version.
- Symptom: the progress record lacks a signature or receipt, and the statistical totals do not match the number of records. Cause: the node does not return confirmation information, and subsequent nodes have no evidence to verify against when parsing the response.
How to verify the setup
This feature acceptance: preview the rendered request, verify the status code and returned fields, then compare the result against one sample; in the variables panel, verify the source of each placeholder, and confirm that Authorization, variables, and responseData can be traced to their origins.
Business test: use one week of records to verify the totals, and check whether the criteria and exceptions are clearly written.
- In the request preview, view the fully rendered address and verify whether the path parameter placeholders are parsed into actual values.
- Verify the request header names and value sources, and confirm that the authentication information is passed in according to the external system's requirements.