What this category's data looks like
This page addresses exception tracing and manual review for primary and secondary school timetables and after-school service scheduling. The materials include the master timetable, the teacher assignment table, and the after-school service project table. The sources are the academic affairs system export, grade-level group reports, and the after-school service project ledger, with an update cadence of weekly or per-adjustment. The master timetable provides the class and period baseline, the teacher assignment table provides the correspondence between assigned teachers and subjects, and the after-school service project table provides project names, participant counts, and venues. When these three types of materials enter this feature, they serve respectively as the comparison source and review basis for the exception list. The fields cover names, quantities, dates, and signatures, and are used to locate discrepancies in the same record across different 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 exception list and review conclusions are parsed from the response by subsequent nodes, or handled by an 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 |
|---|---|---|
| Master timetable | Whether the class, period, date, and signature are consistent with the teacher assignment table | In the request preview, view the full rendered URL, and check the master timetable fields against the returned fields |
| Teacher assignment table | Whether the assigned teacher, subject, and quantity correspond to the after-school service project table | Check the request header names and the source of their values, and compare the response using one sample request |
| After-school service project table | Whether the project name, participant count, venue, and receipt are missing a signature | In the variables panel, check the source of each placeholder, and confirm that variables and responseData are traceable |
| HTTP node | Whether the placeholder variables in the three places—path parameters, request body, and request headers—can be resolved into actual values | Check how Authorization is passed in, and in the request preview view the full rendered URL |
Three common errors
- Symptom: The name, quantity, and date of the same record do not match between the master timetable and the teacher assignment table. Cause: The two materials are maintained by different stages and are not compared under a unified standard.
- Symptom: The version of the after-school service project table is not synchronized, and the old version is still referenced. Cause: The update cadence is inconsistent, and version checking and receipt confirmation are lacking.
- Symptom: The review conclusion lacks a signature or receipt and cannot be handed to the responsible person for handling. Cause: The exception list does not include the original records, and the signature step is skipped.
How to verify the setup
Feature acceptance: preview the rendered request, check the status code and returned fields, then compare the result against one sample, and confirm that responseData and variables are traceable.
Business test: create one exception record, see whether the source material can be traced, and check the dates and signatures of the master timetable, teacher assignment table, and after-school service project table.
- In the variables panel, check the source of each placeholder, and confirm that the variables in the three places—path parameters, request body, and request headers—come from global variables, system variables, or the output of preceding nodes.
- Compare the response using one sample request, check the request header names and the source of their values, and confirm that
Authorizationis passed in according to the external system's requirements.