What this category's data looks like
This category's materials for primary and secondary school exam question setting and grading include the question-setting two-way specification table, exam papers, and grading rubrics. They come from subject question-setting groups and academic affairs management departments, and are updated with each exam batch. Fields include question number, question type, score, cognitive level, date, and signature column. When entering the authorized access and external services function, the question-setting two-way specification table serves as the structural baseline, the exam paper serves as the content body, and the grading rubric serves as the scoring basis; the fields, dates, and signatures of the three must be consistent before the external entry point and visibility scope can be determined.
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 external entry point and authorization scope can be parsed by subsequent nodes from the response, or handled by an external system according to the agreement to complete the next step.
| Object | Check | Verification action |
|---|---|---|
| Question-setting two-way specification table | Question number, question type, score, cognitive level, and date signature must correspond item by item with the exam paper | In the request preview, check the rendered complete address, confirm that the specification table fields are sent with the request body and that placeholder variables can be resolved into actual values |
| Exam paper | The question names, quantity, and date on the paper must be consistent with the specification table and grading rubric | Use one sample request to compare the return, check the request header names and value sources, and confirm that the exam paper fields are consistent with the external interface agreement |
| Grading rubric | Scoring points, scores, signatures, and receipts must be the same version as the exam paper | In the variables panel, check the source of each placeholder, and confirm that the grading rubric fields can be traced to a specific origin |
| External entry point and authorization scope | Visitor identity matches the visibility scope; unauthorized access must not be visible | Access once with a restricted identity, check the status code and returned fields, and see whether the visibility scope matches the setting |
Three common errors
- Symptom: The name, quantity, or date of the same question does not match between the specification table and the exam paper. Cause: The two materials are maintained separately and are not synchronized according to the same exam batch.
- Symptom: The grading rubric and exam paper versions are not synchronized, and the scoring basis does not match the paper. Cause: After revision, only one material was updated, while the other still uses the old version.
- Symptom: The external entry point lacks a signature or receipt, and the authorization scope cannot be traced. Cause: No confirmation record was left during the material circulation process, and the responsibility boundary is unclear.
How to verify the setup
Acceptance of this function: preview the rendered request, check the status code and returned fields, then compare the result against one sample; confirm that the three placeholders Authorization, variables, and responseData can all be resolved.
Business test: access once with a restricted identity and see whether the visibility scope matches the setting.
- Check the request header names and value sources, and confirm that the authentication information is passed in according to the external system's requirements.
- Use one sample request to compare the return, and confirm that the request body fields are consistent with the external interface agreement.