What this category's data looks like
This page addresses progress records and statistics verification materials for primary and secondary school timetables and after-school service scheduling, covering three types of sources: the master timetable, the teacher assignment table, and the after-school service project table. The master timetable provides the baseline for classes and periods, the teacher assignment table provides the basis for assigned teachers and teaching hours, and the after-school service project table provides project names, participant counts, and dates. Materials are updated weekly and summarized at month-end, with fields including course name, assigned teacher, class, date, period, project name, participant count, signature, and receipt. When materials enter the HTTP interface and external systems, each assumes its own data source role: the master timetable is used to verify weekly totals, the teacher assignment table is used to verify assignment consistency, and the after-school service project table is used to verify the statistical criteria for projects.
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 table and statistical criteria description" is parsed by subsequent nodes, or handled by the external system according to the agreement to complete the rest.
| Object | Check | Verification action |
|---|---|---|
| Master timetable | Whether the fields include class, period, date, and signature, and whether the date is consistent with the teacher assignment table | Extract one week of the master timetable, verify the class, period, and date fields, and check whether signatures and receipts are complete |
| Teacher assignment table | Whether the names and counts of assigned teachers match the same records in the master timetable, and whether versions are synchronized | Use one week of records to verify the names and teaching hour counts in the teacher assignment table against the master timetable, and flag inconsistent items |
| After-school service project table | Whether project names, participant counts, dates, and signatures are consistent with the headers of the statistical criteria description | Verify the totals of the project table against the progress table, and check whether exception items are stated in the criteria description |
| HTTP node request | Whether the request URL and path parameter placeholder variables can be resolved into actual values, and whether the request header and request body fields are consistent with the external interface agreement | View the fully rendered URL in the request preview, verify Authorization and variables, and use one sample request to compare the fields returned in responseData |
Three common errors
- Symptom: The course name and teaching hour count for the same record do not match between the master timetable and the teacher assignment table. Cause: The two materials are updated on different schedules, versions are not synchronized, and there is no unified verification node.
- Symptom: The dates and participant counts in the after-school service project table and the statistical criteria description are inconsistent. Cause: The criteria are not written into the headers, exception items are not marked, and subsequent nodes directly take default field values during parsing.
- Symptom: Signatures or receipts are missing from weekly or monthly reports, and the statistical totals do not match the record counts. Cause: The signature field is not checked during material circulation, and the external system receipt is not returned according to the agreement.
How to verify the setup
Feature acceptance: preview the rendered request, verify the status code and returned fields, then compare the result against one sample to confirm that the fields in responseData are consistent with the external interface agreement.
Business testing: use one week of records to verify the totals, check whether the criteria and exceptions are clearly stated, and check whether the record counts and statistical counts of the master timetable, teacher assignment table, and after-school service project table match.
- In the variable panel, verify the source of each placeholder and confirm that
Authorizationandvariablescan be traced to global variables, system variables, or outputs from preceding nodes. - Use one sample request to compare the response, check that the request body fields are consistent with the external interface agreement, and prevent the external system from receiving empty fields.