What this category's data looks like
The data for this category looks like this Primary and secondary school timetables and after-school service scheduling involve three types of materials: the master timetable, the teacher assignment table, and the after-school service project table. The master timetable comes from the academic affairs office's semester scheduling results and is updated by week and period; the teacher assignment table comes from the teaching and research group's summary and is labeled by teacher name and subject; the after-school service project table comes from the moral education office and external institution confirmation forms and is registered by project name, number of participants, and date. When these three types of materials enter the authorized access and external service function, the master timetable serves as the master data determining the class visibility scope, the teacher assignment table serves as the identity mapping determining the teacher visibility scope, and the after-school service project table serves as extended data determining the items visible to parents and superiors. Field characteristics center on names, quantities, dates, signatures, and receipts, and the update rhythm is centralized release at the beginning of the semester and rolling revision during the semester according to change orders. The external entry point returns the corresponding material fragments according to visitor identity, and unauthorized items are not visible.
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 "externally available entry points and authorization scope" are parsed by subsequent nodes from the response, or handled by the external system according to the agreement to complete the next step. The request URL, path parameters, request headers, and request body can all be placeholdered through variables, authentication information is placed in Authorization according to the external system's requirements, and the returned content is read in responseData.
| Object | Check | Verification action |
|---|---|---|
| Master timetable | The class, week, period, and teacher name are consistent in both materials, and signatures and receipts are complete | Check the names, quantities, and dates in the master timetable and teacher assignment table, and inspect the signature fields and receipt attachments |
| Teacher assignment table | The teacher identity matches the visibility scope, and there is no conflict between the name and date in the same record | Make one request with a restricted identity and compare the returned fields with the original records in the assignment table |
| After-school service project table | The project name, number of participants, and date are consistent in the project table and receipt, and the version has been synchronized | Check the dates and participant numbers in the project table and receipt, and confirm the version number and signature |
| Request headers and request body | Authentication information is passed in according to the external system's requirements, and the fields are consistent with the external interface agreement | Check the source of the Authorization value in the request preview, and use a sample request to compare the fields returned in responseData |
Three common errors
- Symptom: The name or date of the same student does not match between the master timetable and the after-school service project table. Cause: The two materials were entered separately, and no comparison of the name and date for the same record was performed.
- Symptom: The teacher assignment table has been revised, but the external entry point still returns the old version. Cause: The version was not synchronized, and the change order did not trigger republication.
- Symptom: The after-school service project table lacks a signature or receipt. Cause: The project confirmation form was not collected, and the materials entered external services before the loop was closed.
How to verify the setup
Acceptance for this function: preview the rendered request, check the status code and returned fields, then compare the result against one sample, and confirm that variables and Authorization are parsed correctly and that the responseData fields are consistent with the agreement.
Business test: access once with a restricted identity, and see whether the visibility scope matches the setting and unauthorized items are not visible.
- In the variables panel, check the source of each placeholder and confirm that the variables in the request URL, path parameters, request headers, and request body can be traced to global variables, system variables, or outputs from preceding nodes.
- Use one sample request to compare the returned fields and check whether the names, quantities, dates, signatures, and receipts in the master timetable, teacher assignment table, and after-school service project table are consistent.