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 include the two-way specification table for question setting, exam papers, and grading rubrics, sourced from teaching and research groups and question-setting groups, with update cadence varying by exam batch and revision version. Field characteristics center on names, quantities, dates, and signatures, and the same record must be consistent across the three materials. When the materials enter the HTTP interface and external systems, the two-way specification table provides the knowledge points and score distribution, the exam paper carries the questions and scores, and the grading rubric gives the scoring points and review basis. Together, the three support exception tracing and manual review. The exception list and review conclusions must be supported by original records and signed by the reviewer, and are ultimately handed to the person in charge for disposition.
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 exception list and review conclusions are parsed from the response by subsequent nodes, or handled by the external system according to the agreement to complete the rest. The HTTP node does not replace the external system in writing to the database or approving.
| Object | Check | Verification action |
|---|---|---|
| Two-way specification table for question setting | Names, quantities, dates, and signatures are consistent across the three materials, and versions are synchronized | Check the complete rendered address in the request preview, use variables to check the placeholder sources, and compare the knowledge point names, quantities, and dates of the specification table and the exam paper |
| Exam paper | Question names, quantities, and dates match the specification table and grading rubric, with no missing signatures | Use a sample request to compare the response, check whether the responseData fields match the exam paper's questions and scores, and check the signatures and receipts |
| Grading rubric | Scoring point names, quantities, and dates are consistent with the exam paper, and versions are not misaligned | Check the source of the Authorization request header value, and compare the scoring point names, quantities, and dates of the grading rubric and the exam paper |
| Exception list and review conclusions | Exceptions are supported by original records, and reviewer signatures are complete | Check the source of each placeholder in the variables panel, and confirm that exception records can be traced back to the source materials |
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 revisions of the two materials are not synchronized, and the fields are not aligned to the same version.
- Symptom: The grading rubric version is not synchronized, and the scoring points are misaligned with the exam paper questions. Cause: After revision, the interface request body fields were not updated, and the external system received empty fields.
- Symptom: The review conclusion lacks a signature or receipt, and the exception cannot be handed to the person in charge for disposition. Cause: The request returns 401 or the request times out, and subsequent nodes do not parse the response.
How to verify the setup
This feature's acceptance: preview the rendered request, check the status code and returned fields, then compare the result against a sample to confirm that the sources of responseData and variables are traceable.
Business test: create an exception record, see whether it can be traced back to the source materials, and check whether the exception list and review conclusions are supported by original records and signed.
- Check in the request preview whether the complete rendered address and path parameter placeholders are parsed into actual values
- Check the source of each placeholder in the variables panel, and confirm that the value sources of
Authorizationandvariablesare correct