What this category's data looks like
This page focuses on school moral education and homeroom teacher work. The materials include themed class meeting plans, student comprehensive quality records, and home visit records. Themed class meeting plans contain activity objectives, procedures, dates, and homeroom teacher signatures; student comprehensive quality records contain semester, evaluation dimensions, quantities, and parent receipts; home visit records contain visit dates, student names, home visit content, and signatures from both parties. These materials come from homeroom teachers' daily reporting, grade-level aggregation, and school archiving. The update cadence is weekly class meetings, comprehensive quality evaluations each semester, and home visits each semester. When entering the question acceptance and missing-item follow-up function, themed class meeting plans are used to check whether activities were carried out as planned; student comprehensive quality records are used to check whether evaluation dimensions and quantities are complete; home visit records are used to check whether student names, dates, and signature receipts are consistent. The three types of materials each serve as a basis in the acceptance records, and when following up on missing items, the specific materials and fields must be indicated.
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 "acceptance records and completed follow-up items" are parsed by subsequent nodes from the response, or handled by an external system according to the agreement to complete the process. The HTTP module sends requests 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 outputs from preceding nodes.
| Object | Check | Verification action |
|---|---|---|
| Themed class meeting plan | Whether activity objectives, procedures, dates, and homeroom teacher signatures are complete, and whether the name and date of the same activity match across two materials | In the request preview, view the complete rendered address and check the path parameters and request body fields; compare the response with a sample request to confirm that the signature and date fields are non-empty |
| Student comprehensive quality record | Whether the semester, evaluation dimensions, quantities, and parent receipts are complete, and whether the version is synchronized | Check the request header names and value sources, and confirm that Authorization is passed in according to the external system's requirements; trace the source of each placeholder in the variables panel and confirm that the receipt fields have values |
| Home visit record | Whether the visit date, student name, home visit content, and signatures from both parties are complete, and whether the receipt is missing | Check that the request body fields are consistent with the external interface agreement, and compare the response with a sample; check whether variables and responseData carry the name, date, and signature fields |
| Acceptance records and completed follow-up items | Whether missing items are identified and followed up, and whether the answers are based on materials | In the variables panel, check the source of each placeholder and confirm that the follow-up items correspond to the material fields; compare the response with a sample to confirm that the missing-item list is complete |
Three common errors
- Symptom: The name and date of the same activity do not match between the themed class meeting plan and the comprehensive quality record. Cause: The two materials are reported separately, versions are not synchronized, and no unified field comparison is performed during acceptance.
- Symptom: The home visit record lacks a signature or receipt, and the quantity in the comprehensive quality record is inconsistent with the plan. Cause: Signatures and quantities are not checked during material archiving, and missing items are not identified and followed up.
- Symptom: The request returns 401, or the external system receives empty fields or the request times out. Cause: The request header authentication information and request body fields are not passed in according to the external interface agreement, and variable placeholders are not resolved into actual values.
How to verify the setup
Acceptance for this function: preview the rendered request, check the status code and returned fields, then compare the result against a sample; confirm that the placeholders in Authorization, variables, and responseData can be traced to their sources.
Business test: submit a question missing key information and see whether it follows up before answering, and check whether the follow-up items point to specific fields in the themed class meeting plan, student comprehensive quality record, or home visit record.
- In the request preview, view the complete rendered address, check the path parameters, request headers, and request body fields, and confirm that each placeholder can be resolved into an actual value.
- In the variables panel, check the source of each placeholder, compare the response with a sample request, and after confirming that the missing-item list corresponds to the material fields, forward it to the responsible person for handling.