What this category's data looks like
This page focuses on Q&A intake materials for primary and secondary school timetables and after-school service scheduling, including three types: the master timetable, the teacher assignment table, and the after-school service project table. The master timetable records class, day of the week, period, and course name; the teacher assignment table records teacher, class, subject, and weekly class hours; the after-school service project table records project name, participating students, date, and signature. The materials are updated by the academic affairs office or the person in charge on a semester and monthly basis, and fields often show inconsistencies in the same record name, quantity, and date, unsynchronized versions, and missing signatures or receipts. When entering this function, the three types of materials serve as the source of request body fields for the external system interface, used to identify missing items and generate follow-up questions.
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 "intake records and items to be completed" are parsed from the response by subsequent nodes, or the external system handles them as agreed and then completes them.
| Object | Check | Verification action |
|---|---|---|
| Master timetable | Whether class, day of the week, period, course name, and date are complete, and whether a signature or receipt exists | Check that the request body fields match the master timetable records, and view the rendered complete address in the request preview |
| Teacher assignment table | Whether teacher, class, subject, weekly class hours, and date match the master timetable | Check the request header names and the source of their values, and verify whether Authorization and variables are passed in as required by the external system |
| After-school service project table | Whether project name, participating students, quantity, date, and signature are consistent with the other two materials | Use a sample request to compare the response, and confirm that the responseData fields match the external interface agreement |
| Variable sources | Every placeholder can be traced to a specific origin, and missing items can be identified and followed up | Check the source of each placeholder in the variable panel, and confirm there are no empty fields and no timeouts |
Three common errors
- Symptom: The course names for the same class do not match between the master timetable and the teacher assignment table. Cause: The two materials are maintained by different handlers, and the versions are not synchronized.
- Symptom: The number of participating students in the after-school service project table is inconsistent with the number of students in the master timetable. Cause: The date was not updated across months, and the signature or receipt is missing.
- Symptom: The request returns 401 or the external system receives empty fields. Cause: The request header authentication information was not passed in as required by the external system, and the variables were not parsed.
How to verify the setup
This function's acceptance: preview the rendered request, check the status code and returned fields, then compare the result against a sample; confirm that the sources of the three placeholders Authorization, variables, and responseData can be traced.
Business test: submit a question missing key information, and see whether it asks a follow-up question before answering.
- In the request preview, check the rendered complete address and request header names, and confirm that the variables come from global variables, system variables, or the output of preceding nodes.
- Use a sample request to compare the returned fields, check that the request body matches the external interface agreement, and then forward it to the person in charge for handling.