What this category's data looks like
In the district and county teaching research activities and lesson observation and evaluation scenario, materials mainly come from three types: teaching research activity notices, lesson observation records, and lesson evaluation minutes. Notices are issued by the organizing party and include the activity name, date, location, and scope of participants; lesson observation records are filled in by observers and include the instructor, class, topic, time, and observation points; lesson evaluation minutes are compiled by the evaluation group and include evaluation opinions, conclusions, and signatures. When the three types of materials enter this function, the notice serves as the main activity record, while lesson observation records and lesson evaluation minutes are attached as sub-records, each playing the role of progress registration and statistical verification. The update rhythm is usually summarized weekly and verified at month-end. Field characteristics are concentrated on names, quantities, dates, signatures, and receipts, and the same record must remain consistent in definition across two materials.
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 "progress table and statistical definition description" is parsed from the response by subsequent nodes, or handled externally according to the agreement to complete the next step. The request URL, path parameters, request headers, and request body can all be placeholdered via variables, and the variables come from global variables, system variables, or the output of preceding nodes.
| Object | Check | Verification action |
|---|---|---|
| Teaching research activity notice | The name, date, and signature fields must be consistent with the lesson observation records and lesson evaluation minutes | View the complete rendered URL in the request preview, and check whether the notice fields are passed in as agreed |
| Lesson observation record | The record count matches the statistical count, and the definition is written in the header | Check the request header names and value sources, and compare the response using one sample request |
| Lesson evaluation minutes | Evaluation opinions, conclusions, and signature receipts are complete, and versions are synchronized | Check the source of each placeholder in the variables panel, and confirm the Authorization and responseData fields |
| Progress table and statistical definition description | Totals and exceptions are clearly stated, and weekly or monthly reports can cite them directly | Use one week of records to verify the totals, and check whether the definitions and exceptions are clearly stated |
Three common errors
- Symptom: The name and date of the same record do not match between the notice and the lesson observation record. Cause: The two places were entered separately and were not checked against a unified definition.
- Symptom: The lesson evaluation minutes lack a signature or receipt, making it impossible to confirm during statistics. Cause: The material circulation step was not synchronized, and the version was not updated.
- Symptom: The external system receives empty fields or the request returns 401. Cause: Placeholder variables were not resolved into actual values, and authentication information was not passed in as agreed.
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 one sample to confirm that variables and responseData are traceable.
Business test: use one week of records to verify the totals, and check whether the definitions and exceptions are clearly stated.
- In the request preview, check the complete rendered URL and path parameters, and confirm that placeholder variables can be resolved into actual values.
- In the variables panel, check the source of each placeholder, and compare whether the request header and request body fields are consistent with the external interface agreement.