What this category's data looks like
This page addresses data versions and change maintenance in primary and secondary school timetable and after-school service scheduling scenarios, involving three types of materials: the master timetable, the teacher assignment table, and the after-school service program table. The master timetable records class, course, week, and venue; the teacher assignment table records teacher, subject, class, and number of class hours; the after-school service program table records program name, number of participants, date, and receipt signature. All three types of materials generate new versions at the start of the semester, when classes are adjusted, and when programs are added or removed; old versions must be retained and traceable, and references must be updated to point to the current version in sync. When the materials enter the HTTP interface and external system feature, the master timetable initiates synchronization as master data, while the teacher assignment table and the after-school service program table are submitted as associated materials along with the master record, each taking on the roles of field validation, date comparison, and signature receipt verification.
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 "version ledger and change records" are parsed from the response by subsequent nodes, or handled by the external system according to the agreement to complete the rest. The request URL, path parameters, request headers, and request body can all reference global variables, system variables, or outputs of preceding nodes via variables, and authentication information is placed in Authorization according to the external system's requirements.
| Object | Check | Verification action |
|---|---|---|
| Master timetable | Fields include class, course, week, and venue; the date and signature columns match the current version | Check the fully rendered URL in the request preview, and compare the fields returned in responseData against the sample |
| Teacher assignment table | Teacher, subject, class, and number of class hours match in name and quantity across the three materials | Check the source of each placeholder in the variables panel, and confirm where the variables values come from |
| After-school service program table | Program name, number of participants, date, and receipt signature are traceable against the old version | Use a sample request to compare the response, and check the Authorization request header name and the source of its value |
| Version ledger and change records | The current version is unique, old versions are traceable, and references are in sync | After changing one piece of content, resend the request and check whether the status code and returned fields are updated in sync |
Three common errors
- Symptom: the name or quantity of the same record does not match between the master timetable and the teacher assignment table. Cause: the two materials are maintained separately, without comparing fields against the same current version.
- Symptom: after the date or number of participants in the after-school service program table is changed, references still point to the old version. Cause: the version was not synchronized, the old version was not marked invalid, and references were not updated with the change.
- Symptom: the external system receives empty fields or returns 401. Cause: the request body fields are inconsistent with the interface agreement, or the
Authorizationauthentication information was not passed in according to the external system's requirements.
How to verify the setup
Acceptance for this feature: preview the rendered request, check the status code and returned fields, then compare the result against a sample; confirm that every placeholder in variables can be traced to its source, and that the responseData fields are consistent with the external interface agreement.
Business test: change one piece of content and see whether the version number and references are updated in sync
- Check the source of each placeholder item by item in the variables panel, and confirm that
variablescan be resolved into actual values - Use a sample request to compare the returned fields, and check the
Authorizationrequest header name and the source of its value