What this category's data looks like
This page addresses district and county teaching research activities and lesson observation and evaluation scenarios. Material sources include teaching research activity notices, lesson observation records, and lesson evaluation minutes, with an update cadence that rolls with activity batches and semester schedules. When these materials enter the Q&A intake and missing-item follow-up feature, they play different roles: notices provide the activity theme, time, location, and participation scope; lesson observation records carry the segments, duration, and observation points of classroom observation; lesson evaluation minutes record review opinions, conclusions, and signature receipts. Field characteristics concentrate in three categories: dates (activity date, observation date, evaluation date), signatures (host, recorder, evaluator), and quantities (number of periods, number of observers, number of evaluation items). When the name, quantity, or date of the same record does not match across two materials, the intake step needs to first identify the missing item, then follow up with the submitting party, and only after it is completed can an intake record and question item list be formed and transferred to the handler.
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 record and the completed question items are parsed from the response by subsequent nodes, or handled by an external system according to the agreement. The request URL, path parameters, request headers, and placeholder variables in the request body come from global variables, system variables, or the output of preceding nodes, and the rendered result can be checked in the request preview.
| Object | Check | Verification action |
|---|---|---|
| Teaching research activity notice | Whether the date, signature, and quantity fields are consistent with the lesson observation records and lesson evaluation minutes | Check the fully rendered URL in the request preview, compare the notice date with the observation date and evaluation date; check whether the host's signature and receipt are complete; use one sample request to compare the returned fields |
| Lesson observation record | Whether the name, number of periods, and lesson evaluation minutes match | Check whether the request body fields are consistent with the external interface agreement, and check how the lesson observation periods and observation point names are written in the two materials; check each placeholder source in the variables panel, and confirm that the variables values come from the output of preceding nodes |
| Lesson evaluation minutes | Whether the version is synchronized, and whether signatures and receipts are missing | Check the request header names and value sources, and confirm that Authorization is passed in according to the external system's requirements; compare the minutes version number with the notice version; when signatures or receipts are missing, follow up first before answering |
| Intake record and completed question items | Whether missing items are identified and followed up, and whether answers are based on materials | Use one sample request to compare the return, and confirm that the missing-item fields in responseData correspond to the follow-up items; for one sample comparison result, check whether the question items cite the original text of the notice, lesson observation record, or lesson evaluation minutes |
Three common errors
- Symptom: the name, quantity, or date of the same record does not match between the notice and the lesson observation record. Cause: the two materials were entered separately, no field-level comparison was performed, and intake was passed directly.
- Symptom: the lesson evaluation minutes version is not synchronized, and old-version signatures and receipts are treated as valid materials. Cause: after the materials were updated, the intake record was not written back, and the follow-up step still judged by the old-version fields.
- Symptom: the request returns 401 or the external system receives empty fields. Cause: the value source of
Authorizationwas not checked, or thevariablesplaceholders were not resolved into actual values.
How to verify the setup
This feature's acceptance: preview the rendered request, check the status code and returned fields, then compare one sample result; check whether the missing items and follow-up items in responseData correspond, and whether the variables placeholders can be traced to specific sources.
Business test: submit a question that lacks key information, and see whether it follows up first before answering; after completion, check whether the intake record and question item list are transferred to the handler.
- Check the fully rendered URL, request header names, and value sources in the request preview, and confirm that the
Authorizationandvariablesplaceholders are resolved into actual values. - Use one sample request to compare the return, check that the request body fields are consistent with the external interface agreement, and check whether the missing-item fields in
responseDatacorrespond to the follow-up items.