What this category's data looks like
District and county teaching research activities and lesson observation and evaluation involve three types of materials: teaching research activity notices, lesson observation records, and lesson evaluation minutes. Notices are issued by the teaching research department and contain the activity name, time, location, participating schools, and subject; lesson observation records are filled in on site by the observer and contain the instructor, class, topic, and observation points; lesson evaluation minutes are compiled by the moderator and contain key remarks, conclusions, and a signature field. The three types of materials are archived by activity batch, and the update rhythm is synchronized with the teaching research schedule, usually completed within one week after the activity ends. When the materials enter anomaly tracing and manual review, the notice serves as the baseline source for checking the activity name and date, the lesson observation record serves as process evidence for checking the instructor and class, and the lesson evaluation minutes serve as the basis for conclusions for checking signatures and receipts. Field characteristics are concentrated in four categories: name, quantity, date, and signature. The same record is prone to mismatches across the three materials and requires item-by-item tracing.
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 anomaly list and review conclusions are parsed from the response by subsequent nodes, or handled externally according to the agreement. The HTTP node sends a request to the target address. Path parameters, request body, and request headers can all use variable placeholders, and the variables come from global variables, system variables, or the output of preceding nodes.
| Object | Check | Verification action |
|---|---|---|
| Teaching research activity notice | Whether the activity name, date, and participating school fields are consistent with the lesson observation record and lesson evaluation minutes | Take the original notice, compare the name and date of the same activity across the three materials, and record the locations of discrepancies |
| Lesson observation record | Whether the instructor, class, and number of topics match the lesson evaluation minutes | Check the instructor, class, and number of sessions in the lesson observation record against the lesson evaluation minutes item by item, and mark missing items |
| Lesson evaluation minutes | Whether the signature field and receipt are complete, and whether the version is synchronized with the notice | Check the minutes signatures and receipt, and verify the minutes version number against the version issued with the notice |
| Request address and path parameters | Whether the placeholder variables can be resolved into actual values | View the fully rendered address in the request preview, and check the source of variables |
Three common errors
- Symptom: The name and date of the same activity do not match between the notice and the lesson observation record. Cause: The two materials were entered separately, and field comparison was not performed using the notice as the baseline source.
- Symptom: The version of the lesson evaluation minutes is not synchronized with the notice, and the conclusion cites an old version. Cause: After the version was updated, the minutes were not written back, and a version verification step was missing.
- Symptom: The lesson evaluation minutes lack a signature or receipt, and the review conclusion cannot be confirmed. Cause: The signature field was not filled in, the receipt was not collected, and no completeness check was performed when the materials were archived.
How to verify the setup
Acceptance of this feature: preview the rendered request, check the status code and returned fields, then compare the result against a sample, and confirm that the Authorization and responseData fields conform to the agreement.
Business test: create an anomaly record and see whether it can be traced back to the source material
- In the variables panel, check the source of each placeholder and confirm that the value source of the request header
Authorizationmeets the requirements of the external system - Use a sample request to compare the response and check that the
responseDatafield is consistent with the external interface agreement