What this category's data looks like
District and county teaching research activity and lesson observation and evaluation materials mainly fall into three categories: teaching research activity notices, lesson observation records, and lesson evaluation minutes. Notices contain the activity theme, time, location, participating schools and teachers, and receipt requirements; lesson observation records contain the instructor, class, subject, observation time, observation points, and signature; lesson evaluation minutes contain evaluation points, improvement suggestions, and the signatures of the host and participants. These materials come from submissions by each school and compilation by teaching researchers, and the update rhythm is: notices are issued before the activity, lesson observations are recorded during the activity, and minutes are produced after the activity. When entering the HTTP interface and external system functions, notices serve as the basis for triggering and receipts, lesson observation records serve as process evidence, and lesson evaluation minutes serve as conclusions and citation sources; the fields, dates, and signatures of all three need to remain traceable in the version ledger.
Configuration and implementation checks
This step is executed by the HTTP node in the workflow, which outputs the response body, status code, and returned fields. The version ledger and change records are completed by subsequent nodes parsing the response, or by the external system handling them according to the agreement. The HTTP module sends requests to the target address, and variables can be used as placeholders in all three places: path parameters, request body, and request headers. 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, participating schools, and receipt requirements in the notice are consistent with the ledger | Check the request body fields against the original notice, and inspect the source of variables |
| Lesson observation record | Whether the instructor, class, subject, observation date, and signature in the lesson observation record correspond to the lesson evaluation minutes | Compare the fields of the same record in the two materials, and confirm that dates and signatures are not missing |
| Lesson evaluation minutes | Whether the evaluation points, improvement suggestions, and participant signatures in the lesson evaluation minutes are synchronized with the notice and lesson observation record | Check the version identifier and citation reference in the returned fields |
| Version ledger and change records | The current version is unique, old versions are traceable, and references are synchronized | View the fully rendered address in the request preview, and check the Authorization and responseData fields |
Three common errors
- Symptom: The activity name and date of the same record do not match between the notice and the lesson observation record. Cause: The two places were filled in manually and were not based on the same version ledger.
- Symptom: The lesson evaluation minutes have been updated, but the lesson observation record still references the old version. Cause: The version was not synchronized, and the reference was not refreshed with the change records.
- Symptom: The lesson observation record or lesson evaluation minutes lack a signature or receipt. Cause: The signature field was not validated during submission, and the external system received an empty field.
How to verify the setup
This function's acceptance: view the fully rendered address in the request preview, check the status code and returned fields, and then compare the returned result against a sample request.
Business test: change one piece of content and see whether the version number and references are updated synchronously.
- In the variables panel, check the source of each placeholder, and confirm that the
variablesin the path parameters, request headers, and request body can all be traced to global variables, system variables, or the output of preceding nodes. - Use a sample request to compare the response, and check whether the source of the
Authorizationvalue and theresponseDatafields are consistent with the external interface agreement.