What this category's data looks like
District and county teaching research activities and lesson observation and evaluation materials, including teaching research activity notices, lesson observation records, and lesson evaluation minutes. Notices come from the teaching research department, lesson observation records are filled in by observers, and lesson evaluation minutes are compiled by the lesson evaluation group. The update rhythm is: notices are issued before the activity, lesson observations are recorded during the activity, and minutes are produced after the activity. Fields include activity name, date, instructor, observer, lesson evaluation comments, and signature or receipt. When the materials enter the authorized access and external services function, the notice determines the visible scope, and the lesson observation records and lesson evaluation minutes determine whether the fields and signatures are complete.
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 externally available entry point and authorization scope are parsed from the response by subsequent nodes, or handled by an external system according to the agreement to complete the next step.
| Object | Check | Verification action |
|---|---|---|
| Teaching research activity notice | The activity name, date, and authorization scope in the notice must be consistent with the lesson observation records and lesson evaluation minutes | In the request preview, view the complete rendered address, and check the notice fields against the returned fields |
| Lesson observation record | The observer, instructor, date, and signature or receipt must correspond to the lesson evaluation minutes | Check the request header names and value sources, and compare the response using a sample request |
| Lesson evaluation minutes | The lesson evaluation comments, signature, and version must be synchronized with the notice and lesson observation records | In the variables panel, check the source of each placeholder and check whether variables is parsed |
| External service entry point | The visitor identity matches the visible scope, and unauthorized access must not be visible | Access once with a restricted identity and check whether Authorization and responseData match the settings |
Three common errors
- Symptom: The name, quantity, and date of the same record do not match across two materials. Cause: The notice and lesson observation record are maintained separately and were not checked against the same field definitions.
- Symptom: The lesson evaluation minutes version is not synchronized, and the old version is still read by the external service. Cause: The HTTP node request address or path parameter placeholder variables were not updated to the latest source.
- Symptom: The lesson observation record lacks a signature or receipt, but the external service still returns it as visible. Cause: The authentication information and visible scope were not passed in according to the external system's requirements.
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 the three placeholders Authorization, variables, and responseData are traceable.
Business test: access once with a restricted identity and check whether the visible scope matches the settings
- Check the request header names and value sources, and confirm that the authentication information is passed in according to the external system's requirements
- In the variables panel, check the source of each placeholder, and compare the returned fields using one sample request